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 12:14:11 -0500 |
| |
On Fri, 2011-12-09 at 11:49 -0500, Jason Baron wrote: > > > > Then, I'm wondering if the same technique can be used for the original > nmi->int3->nmi case. That is, switch the IDT when the int3 comes in, so > that the subsequent nmi will be handled on the debug stack. As you pointed out, > these nesting and thus the IDT switching would be rare in > practice. (I know you don't want to touch any code outside of nmi :))
Right, I NMIs are ugly and we shouldn't uglify other code because of it.
Anyway, when could we do the switch in the int3 handler? As I said, the NMI could come in at that moment the int3 is being processed, before it does anything. If the NMI hits an int3, it just stomped over the previous int3's interrupt frame.
The more I look at this, the more I like the original idea.
-- Steve
| |