Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 8 Nov 2002 10:04:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 8 Nov 2002 10:04:31 -0500 Received: from pc1-cwma1-5-cust42.swa.cable.ntl.com ([80.5.120.42]:55707 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Fri, 8 Nov 2002 10:04:31 -0500 Subject: Re: NMI handling rework From: Alan Cox To: Corey Minyard Cc: Zwane Mwaikambo , Ingo Molnar , Linux Kernel Mailing List , John Levon In-Reply-To: <3DCA99F4.4090703@mvista.com> References: <3DCA99F4.4090703@mvista.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 08 Nov 2002 15:34:28 +0000 Message-Id: <1036769668.16651.0.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 516 Lines: 13 On Thu, 2002-11-07 at 16:51, Corey Minyard wrote: > NMIs cannot be masked, they are by definition non-maskable :-). You can > get an NMI while executing an NMI. The intel docs certainly imply NMI is never interrupted by an NMI, so you have one per CPU to worry about - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/