Messages in this thread | | | Subject | Re: [RFC][PATCH 3/3] x86: Add workaround to NMI iret woes | From | Steven Rostedt <> | Date | Fri, 09 Dec 2011 11:34:38 -0500 |
| |
On Thu, 2011-12-08 at 21:43 -0500, Steven Rostedt wrote:
> diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c > index a8e3eb8..906a02a 100644 > --- a/arch/x86/kernel/traps.c > +++ b/arch/x86/kernel/traps.c > @@ -723,4 +723,9 @@ void __init trap_init(void) > cpu_init(); > > x86_init.irqs.trap_init(); > + > +#ifdef CONFIG_X86_64 > + memcpy(&nmi_idt_table, &idt_table, IDT_ENTRIES * 16); > + set_nmi_gate(1, &debug);
Frederic Weisbecker told me on IRC that int3 is 3 #bp, not 1 #db. I need to also add that:
set_nmi_gate(3, &int3)
Mathieu says we need to worry about MCEs, so maybe we can add that stack as well.
set_nmi_gate(18, &machine_check);
If we make NMIs not modify any stack, then we can remove the "NMI executing variable" on the stack. As any nested NMIs will see that it preempted an NMI by just checking the stack. We have to check it anyway, and by removing another check, this may be good to do.
-- Steve
> +#endif > } >
| |