|| ||Steven Rostedt <firstname.lastname@example.org> |
|| ||email@example.com |
|| ||[RFC][PATCH 0/3] x86: Find a way to allow breakpoints in NMIs |
|| ||Thu, 08 Dec 2011 14:30:03 -0500|
|| ||Ingo Molnar <firstname.lastname@example.org>,
Andrew Morton <email@example.com>,
Thomas Gleixner <firstname.lastname@example.org>,
Peter Zijlstra <email@example.com>,
Linus Torvalds <firstname.lastname@example.org>,
"H. Peter Anvin" <email@example.com>,
Frederic Weisbecker <firstname.lastname@example.org>,
Jason Baron <email@example.com>,
Mathieu Desnoyers <firstname.lastname@example.org>|
|| ||Article, Thread
As been previously discussed on LKML, x86 has an issue with NMIs and iret.
If an NMI takes an exception or breakpoint, iret that those handlers do
will take the CPU out of NMI context, which could allow another NMI to
come in and corrupt the stack.
Linus has discussed a way to solve this and I tried to implement it.
What I came up with was a bit different, but I'm posting it now to get
some feedback from it. See patch 3. I wrote a very detailed change log
there and wont repeat it here.
Let me know what everyone thinks.
Linus Torvalds (1):
x86: Do not schedule while still in NMI context
Steven Rostedt (2):
x86: Document the NMI handler about not using paranoid_exit
x86: Add workaround to NMI iret woes
arch/x86/kernel/entry_64.S | 209 +++++++++++++++++++++++++++++++++++++-------
1 files changed, 176 insertions(+), 33 deletions(-)