diff options
author | Andy Lutomirski <luto@kernel.org> | 2015-07-15 19:29:41 +0200 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2015-07-17 12:50:14 +0200 |
commit | a97439aa1aec10387797b4abae3cf117de1c90d7 (patch) | |
tree | 6350d830fed0e1a6908bc53eaa9aefff2425902b /Documentation/PCI/pci-iov-howto.txt | |
parent | x86/nmi/64: Make the "NMI executing" variable more consistent (diff) | |
download | linux-a97439aa1aec10387797b4abae3cf117de1c90d7.tar.xz linux-a97439aa1aec10387797b4abae3cf117de1c90d7.zip |
x86/entry/64, x86/nmi/64: Add CONFIG_DEBUG_ENTRY NMI testing code
It turns out to be rather tedious to test the NMI nesting code.
Make it easier: add a new CONFIG_DEBUG_ENTRY option that causes
the NMI handler to pre-emptively unmask NMIs.
With this option set, errors in the repeat_nmi logic or failures
to detect that we're in a nested NMI will result in quick panics
under perf (especially if multiple counters are running at high
frequency) instead of requiring an unusual workload that
generates page faults or breakpoints inside NMIs.
I called it CONFIG_DEBUG_ENTRY instead of CONFIG_DEBUG_NMI_ENTRY
because I want to add new non-NMI checks elsewhere in the entry
code in the future, and I'd rather not add too many new config
options or add this option and then immediately rename it.
Signed-off-by: Andy Lutomirski <luto@kernel.org>
Reviewed-by: Steven Rostedt <rostedt@goodmis.org>
Cc: Borislav Petkov <bp@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'Documentation/PCI/pci-iov-howto.txt')
0 files changed, 0 insertions, 0 deletions