[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110914193437.GX7761@one.firstfloor.org>
Date: Wed, 14 Sep 2011 21:34:37 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Avi Kivity <avi@...hat.com>
Cc: Andi Kleen <andi@...stfloor.org>, Don Zickus <dzickus@...hat.com>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Peter Zijlstra <peterz@...radead.org>,
"H. Peter Anvin" <hpa@...or.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Nick Piggin <npiggin@...nel.dk>,
Marcelo Tosatti <mtosatti@...hat.com>,
KVM <kvm@...r.kernel.org>,
Xen Devel <xen-devel@...ts.xensource.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
Stefano Stabellini <stefano.stabellini@...citrix.com>
Subject: Re: [PATCH 08/13] xen/pvticketlock: disable interrupts while blocking
On Wed, Sep 14, 2011 at 10:26:21PM +0300, Avi Kivity wrote:
> On 09/14/2011 08:28 PM, Andi Kleen wrote:
> >> If an NMI hits in an interrupt handler, or in the "after hlt" section
> >> before the write-to-last-nmi-rip, then we'll see that %rip has changed.
> >> If it hits after the write-to-last-nmi-rip instruction (or in the hlt
> >> itself), then we'll also see that %rip has changed, due to the effect of
> >> that instruction.
> >
> >It won't handle multiple NMIs in halt. I assume that's reasonable common.
> >
>
> Why not?
They all have the same original RIPs and there is no way to distingush
them.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists