WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] NMI delivery not correctly working

To: "Keir Fraser" <keir@xxxxxxxxxxxxx>, "Christoph Egger" <Christoph.Egger@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] NMI delivery not correctly working
From: "Kaushik Barde" <Kaushik_Barde@xxxxxxxxxxx>
Date: Tue, 24 Jul 2007 11:26:08 -0700
Delivery-date: Tue, 24 Jul 2007 11:23:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2CBF079.12F6E%keir@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200707241747.23720.Christoph.Egger@xxxxxxx> <C2CBF079.12F6E%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfOFSvtajGyxzoIEdy8MAAX8io7RQACLO6w
Thread-topic: [Xen-devel] NMI delivery not correctly working
Keir:

Processor disables calls to subsequent NMIs till it receives next IRET
instruction (via masking of maskable interrupts).
I guess, what I am not clear about is how a fully-virtualized guest
whould issue a IRET hypercall?

-Kaushik

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
Sent: Tuesday, July 24, 2007 10:08 AM
To: Christoph Egger; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] NMI delivery not correctly working

On 24/7/07 16:47, "Christoph Egger" <Christoph.Egger@xxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel