diff options
author | 2018-09-19 10:50:24 +0200 | |
---|---|---|
committer | 2018-09-27 20:39:42 +0200 | |
commit | 7904ba8a66f400182a204893c92098994e22a88d (patch) | |
tree | 5364759f89275e6b6ab95586301dc9b2bb265b16 /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | x86/mm/cpa: Factor common code between cpa_flush_*() (diff) | |
download | linux-dev-7904ba8a66f400182a204893c92098994e22a88d.tar.xz linux-dev-7904ba8a66f400182a204893c92098994e22a88d.zip |
x86/mm/cpa: Optimize __cpa_flush_range()
If we IPI for WBINDV, then we might as well kill the entire TLB too.
But if we don't have to invalidate cache, there is no reason not to
use a range TLB flush.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Dave Hansen <dave.hansen@intel.com>
Cc: Bin Yang <bin.yang@intel.com>
Cc: Mark Gross <mark.gross@intel.com>
Link: https://lkml.kernel.org/r/20180919085948.195633798@infradead.org
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions