From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933188Ab1INUQu (ORCPT ); Wed, 14 Sep 2011 16:16:50 -0400 Received: from ch1ehsobe004.messaging.microsoft.com ([216.32.181.184]:47089 "EHLO ch1outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933151Ab1INUQt (ORCPT ); Wed, 14 Sep 2011 16:16:49 -0400 X-SpamScore: -8 X-BigFish: VPS-8(zz1432N98dKzz1202hzzz32i668h839h944h) X-Forefront-Antispam-Report: CIP:163.181.249.109;KIP:(null);UIP:(null);IPVD:NLI;H:ausb3twp02.amd.com;RD:none;EFVD:NLI X-FB-SS: 0,13, X-WSS-ID: 0LRJ4B6-02-4UU-02 X-M-MSG: Date: Wed, 14 Sep 2011 22:16:12 +0200 From: Robert Richter To: Don Zickus CC: "x86@kernel.org" , Andi Kleen , Peter Zijlstra , "ying.huang@intel.com" , LKML , "paulmck@linux.vnet.ibm.com" , "avi@redhat.com" , "jeremy@goop.org" Subject: Re: [V4][PATCH 4/6] x86, nmi: add in logic to handle multiple events and unknown NMIs Message-ID: <20110914201612.GK6063@erda.amd.com> References: <1315947509-6429-1-git-send-email-dzickus@redhat.com> <1315947509-6429-5-git-send-email-dzickus@redhat.com> <20110914162653.GI6063@erda.amd.com> <20110914175809.GY5795@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20110914175809.GY5795@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginatorOrg: amd.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14.09.11 13:58:09, Don Zickus wrote: > On Wed, Sep 14, 2011 at 06:26:53PM +0200, Robert Richter wrote: > > On 13.09.11 16:58:27, Don Zickus wrote: > > > @@ -87,6 +87,16 @@ static int notrace __kprobes nmi_handle(unsigned int type, struct pt_regs *regs) > > > > > > handled += a->handler(type, regs); > > > > > > + /* > > > + * Optimization: only loop once if this is not a > > > + * back-to-back NMI. The idea is nothing is dropped > > > + * on the first NMI, only on the second of a back-to-back > > > + * NMI. No need to waste cycles going through all the > > > + * handlers. > > > + */ > > > + if (!b2b && handled) > > > + break; > > > > Don, if I am not missing something, this actually does not work > > because perfctr NMIs do not re-trigger. Suppose a handler running > > before perfctr. It sets 'handled' and the chain is stopped here. To > > run through the perfctr handler the NMI must retrigger which it > > doesn't. > > Your patch is incorrect. Your dummy handler does not handle a _real_ NMI. > Which means no _real_ NMI was ever generated. Of course perf won't work. > You just swallowed its NMI. > > The change I made is for nmi handlers that actually have an NMI associated > with them. The idea is if somebody generated an NMI, it will get handled > by a handler. If perf comes along and generates another NMI, it should > get latched. Upon handling the first NMI, the perf NMI should be sitting > queued up and cause the back-to-back NMI. In this case all the handlers > will be executed (to handle dropped NMIs). Yes, your thought about the latched NMI could work. Though I better test this with some real nmis from different sources. Unfortunately this is much harder to trigger. Will give it a try. It would be a pretty nice optimization then. > My only question to you is the IBS stuff you were working on. Does that > generate a _real_ NMI or does it just piggy back off of the perf NMI? Yes, IBS generates real NMIs, there is an own interrupt vector for it. -Robert -- Advanced Micro Devices, Inc. Operating System Research Center