From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755291Ab0JKQOI (ORCPT ); Mon, 11 Oct 2010 12:14:08 -0400 Received: from casper.infradead.org ([85.118.1.10]:40325 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754641Ab0JKQOH convert rfc822-to-8bit (ORCPT ); Mon, 11 Oct 2010 12:14:07 -0400 Subject: Re: [PATCH -v3 3/6] x86, NMI, Rewrite NMI handler From: Peter Zijlstra To: Huang Ying Cc: Don Zickus , Ingo Molnar , "H. Peter Anvin" , linux-kernel@vger.kernel.org, Andi Kleen , Robert Richter In-Reply-To: <1286606987-19879-3-git-send-email-ying.huang@intel.com> References: <1286606987-19879-1-git-send-email-ying.huang@intel.com> <1286606987-19879-3-git-send-email-ying.huang@intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Mon, 11 Oct 2010 18:13:55 +0200 Message-ID: <1286813635.2336.617.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2010-10-09 at 14:49 +0800, Huang Ying wrote: > notify_die(DIE_NMI_IPI); > notify_die(DIE_NMI); > /* process io port 0x61 */ > nmi_watchdog_touch(); > unknown_nmi(); Why keep NMI_IPI? What the heck is it for? I'd like to see: DIE_NMI DIE_NMI_UNKNOWN In DIE_NMI we walk the chain and deal with NMIs, in DIE_NMI_UNKNOWN we try to consume extra NMIs where possible (like the much discussed extra PMU interrupts).