From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 08/13] xen/pvticketlock: disable interrupts while blocking Date: Wed, 07 Sep 2011 20:41:48 +0300 Message-ID: <4E67ACDC.90303@redhat.com> References: <20110906151408.GA7459@redhat.com> <4E66615E.8070806@goop.org> <20110906182758.GR5795@redhat.com> <4E66EF86.9070200@redhat.com> <20110907134411.GV5795@redhat.com> <4E678992.5050709@redhat.com> <20110907155657.GX5795@redhat.com> <4E679AF4.50209@redhat.com> <20110907165203.GQ6838@redhat.com> <4E67A551.4000502@redhat.com> <20110907172117.GY5795@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110907172117.GY5795@redhat.com> Sender: linux-kernel-owner@vger.kernel.org To: Don Zickus Cc: Jeremy Fitzhardinge , Peter Zijlstra , "H. Peter Anvin" , Linus Torvalds , Ingo Molnar , the arch/x86 maintainers , Linux Kernel Mailing List , Nick Piggin , Marcelo Tosatti , KVM , Andi Kleen , Xen Devel , Jeremy Fitzhardinge , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org 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.