summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorDave Hansen <dave.hansen@linux.intel.com>2016-02-13 00:02:25 +0300
committerIngo Molnar <mingo@kernel.org>2016-02-18 21:46:29 +0300
commitc0b17b5bd4b7b98e7c6b67c9f69343b64711271b (patch)
treeeb3bc0ea1461fd43622db5a2a1045894ed1dd045 /tools/perf/scripts/python/call-graph-from-postgresql.py
parentd61172b4b695b821388cdb6088a41d431bcbb93b (diff)
downloadlinux-c0b17b5bd4b7b98e7c6b67c9f69343b64711271b.tar.xz
x86/mm/pkeys: Dump PKRU with other kernel registers
Protection Keys never affect kernel mappings. But, they can affect whether the kernel will fault when it touches a user mapping. The kernel doesn't touch user mappings without some careful choreography and these accesses don't generally result in oopses. But, if one does, we definitely want to have PKRU available so we can figure out if protection keys played a role. Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com> Reviewed-by: Thomas Gleixner <tglx@linutronix.de> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Andy Lutomirski <luto@amacapital.net> Cc: Borislav Petkov <bp@alien8.de> Cc: Brian Gerst <brgerst@gmail.com> Cc: Dave Hansen <dave@sr71.net> Cc: Denys Vlasenko <dvlasenk@redhat.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Rik van Riel <riel@redhat.com> Cc: linux-mm@kvack.org Link: http://lkml.kernel.org/r/20160212210225.BF0D4482@viggo.jf.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions