[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E67ACDC.90303@redhat.com>
Date: Wed, 07 Sep 2011 20:41:48 +0300
From: Avi Kivity <avi@...hat.com>
To: Don Zickus <dzickus@...hat.com>
CC: 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>, Andi Kleen <andi@...stfloor.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 09/07/2011 08:21 PM, Don Zickus wrote:
> >
> > How about, during NMI, save %rip to a per-cpu variable. Handle just
> > one cause. If, on the next NMI, we hit the same %rip, assume
> > back-to-back NMI has occured and now handle all causes.
>
> I had a similar idea a couple of months ago while debugging a continuous
> flow of back-to-back NMIs from a stress-test perf application and I
> couldn't get it to work. But let me try it again, because it does make
> sense as an optimization.
>
>
Great, thanks.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
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