From: Borislav Petkov <[email protected]> Hi Ingo,
here's a pile which addresses issues which arise when using an NMI button on certain platforms which provide it, to cause an external NMI and thus cause a concurrent kdump to fail. For that, we're getting a new cmdline option called "apic_extnmi" which can control which CPUs (or none) to receive the external NMI. The default behavior is what the kernel does currently - only the BSP receives it. I've made sure that each commit message explains in great detail what the problem is as this whole area is not trivial. Please apply, thanks. Borislav Petkov (1): x86/mm: Align macro defines Hidehiro Kawai (6): panic, x86: Fix re-entrance problem due to panic on NMI panic, x86: Allow CPUs to save registers even if looping in NMI context kexec: Fix race between panic() and crash_kexec() x86/apic: Introduce apic_extnmi command line parameter x86/nmi: Save regs in crash dump on external NMI Documentation: Document kernel.panic_on_io_nmi sysctl -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
