[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86: don't deliver NMI to PVH Dom0

To: Jan Beulich <JBeulich@xxxxxxxx>
From: Tim Deegan <tim@xxxxxxx>
Date: Thu, 11 Dec 2014 14:00:26 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>
Delivery-date: Thu, 11 Dec 2014 13:00:46 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

At 10:47 +0000 on 11 Dec (1418291241), Jan Beulich wrote:
> ... for the time being: The mechanism used depends on the domain's use
> of the IRET hypercall.

Can you elaborate?  Looking at the existing code it seems like what it
does is set v->nmi_pending and make sure the vcpu gets scheduled
appropriately.

The HVM code will deliver an NMI if it sees v->nmi_pending (which is
what vlapic_accept_irq does, for example).  Is there some other piece
I'm missing?

Cheers,

Tim.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH] x86: don't deliver NMI to PVH Dom0
  - From: Jan Beulich

References:
- [Xen-devel] [PATCH] x86: don't deliver NMI to PVH Dom0
  - From: Jan Beulich

Prev by Date: Re: [Xen-devel] [PATCH 08/27] ts-unixbench-reslts: for retrieving the results
Next by Date: Re: [Xen-devel] [PATCH 03/27] Guest setup: allow the amount of RAM to be a runvar
Previous by thread: Re: [Xen-devel] [PATCH] x86: don't deliver NMI to PVH Dom0
Next by thread: Re: [Xen-devel] [PATCH] x86: don't deliver NMI to PVH Dom0
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.