From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH 08/13] xen/pvticketlock: disable interrupts while blocking Date: Tue, 13 Sep 2011 21:03:20 +0200 Message-ID: <20110913190320.GR7761@one.firstfloor.org> References: <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> <20110913184044.GN5795@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20110913184044.GN5795@redhat.com> Sender: linux-kernel-owner@vger.kernel.org To: Don Zickus Cc: Avi Kivity , 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 > So I got around to implementing this and it seems to work great. The back > to back NMIs are detected properly using the %rip and that info is passed to > the NMI notifier. That info is used to determine if only the first > handler to report 'handled' is executed or _all_ the handlers are > executed. > > I think all the 'unknown' NMIs I generated with various perf runs have > disappeared. I'll post a new version of my nmi notifier rewrite soon. This will fail when the system is idle. -Andi