From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: NMI delivery not correctly working
Date: Wed, 25 Jul 2007 07:22:39 +0100
Message-ID: <C2CCAABF.B61A%keir@xensource.com>
References: <0EF82802ABAA22479BC1CE8E2F60E8C3018F95BA@scl-exch2k3.phoenix.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <0EF82802ABAA22479BC1CE8E2F60E8C3018F95BA@scl-exch2k3.phoenix.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Kaushik Barde <Kaushik_Barde@Phoenix.com>, Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 24/7/07 19:26, "Kaushik Barde" <Kaushik_Barde@Phoenix.com> wrote:

> Processor disables calls to subsequent NMIs till it receives next IRET
> instruction

Yes.

> (via masking of maskable interrupts).

No, since NMIs are, of course, not maskable by conventional means.

> I guess, what I am not clear about is how a fully-virtualized guest
> whould issue a IRET hypercall?

It's used just like any other hypercall. Guest jumps at the correct offset
into its hypercall transfer page.

 -- Keir

> -Kaushik
> 
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser
> Sent: Tuesday, July 24, 2007 10:08 AM
> To: Christoph Egger; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] NMI delivery not correctly working
> 
> On 24/7/07 16:47, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> 
>> I know, there is a line "current->nmi_masked = 0;" in do_iret() in
>> xen/arch/x86/x86_(32|64)/traps.c, but this is actually never called
>> after NMI delivery.
> 
> Guests *must* use the iret hypercall when returning from their NMI
> handler.
> This is giving a virtualised equivalent of the 'NMI-blocking' latch
> implemented in x86 processors, which is reset by the IRET instruction.
> 
>  -- Keir
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel