From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: NMI delivery not correctly working Date: Wed, 25 Jul 2007 07:55:11 +0100 Message-ID: References: <0EF82802ABAA22479BC1CE8E2F60E8C3017E79E5@scl-exch2k3.phoenix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0EF82802ABAA22479BC1CE8E2F60E8C3017E79E5@scl-exch2k3.phoenix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Kaushik Barde , Christoph Egger , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 25/7/07 07:43, "Kaushik Barde" wrote: > Thanks. > >>> > via masking of maskable interrupts > << > What I'd meant there was all other interrupts are masked (by processor during > NMI handling) except for NMI. NMIs *are* masked by x86 CPU from when an NMI is delivered to the CPU until after that CPU next executes an IRET. The CPU has a special NMI mask for this purpose (not directly architecturally visible). It's unrelated to EFLAGS.IF. -- Keir