[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Re: [PATCH 08/13] xen/pvticketlock: disable interrupts while blocking
- To: Don Zickus <dzickus@xxxxxxxxxx>
- From: Avi Kivity <avi@xxxxxxxxxx>
- Date: Wed, 07 Sep 2011 20:41:48 +0300
- Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Marcelo Tosatti <mtosatti@xxxxxxxxxx>, Nick Piggin <npiggin@xxxxxxxxx>, KVM <kvm@xxxxxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Andi Kleen <andi@xxxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
- Delivery-date: Wed, 07 Sep 2011 10:44:48 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
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.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
