From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christoph Egger" Subject: Re: NMI delivery not correctly working Date: Wed, 25 Jul 2007 08:48:21 +0200 Message-ID: <200707250848.21972.Christoph.Egger@amd.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tuesday 24 July 2007 19:07:53 Keir Fraser wrote: > On 24/7/07 16:47, "Christoph Egger" wrote: > > I know, there is a line "current->nmi_masked =3D 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 handle= r. > This is giving a virtualised equivalent of the 'NMI-blocking' latch > implemented in x86 processors, which is reset by the IRET instruction. > Ah, I see. Tnx. It would be really nice to have some documentation about hypercalls, though. Christoph =2D-=20 AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Gesch=E4ftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht Dresden: HRA 4896 vertretungsberechtigter Komplement=E4r: AMD Saxony LLC (Sitz Wilmington, Delaware, USA) Gesch=E4ftsf=FChrer der AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy