aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2018-09-17 16:29:11 +0200
committerThomas Gleixner <tglx@linutronix.de>2018-09-27 20:39:38 +0200
commit4046460b867f8b041c81c26c09d3bcad6d6e814e (patch)
tree057fe915206b0f01b9db253b7871561d28be5824 /tools/perf/scripts/python/export-to-postgresql.py
parentx86/mm/cpa: Allow range check for static protections (diff)
downloadlinux-dev-4046460b867f8b041c81c26c09d3bcad6d6e814e.tar.xz
linux-dev-4046460b867f8b041c81c26c09d3bcad6d6e814e.zip
x86/mm/cpa: Add debug mechanism
The whole static protection magic is silently fixing up anything which is handed in. That's just wrong. The offending call sites need to be fixed. Add a debug mechanism which emits a warning if a requested mapping needs to be fixed up. The DETECT debug mechanism is really not meant to be enabled except for developers, so limit the output hard to the protection fixups. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Dave Hansen <dave.hansen@intel.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Bin Yang <bin.yang@intel.com> Cc: Mark Gross <mark.gross@intel.com> Link: https://lkml.kernel.org/r/20180917143546.078998733@linutronix.de
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions