All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christoph Egger" <Christoph.Egger@amd.com>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: NMI delivery not correctly working
Date: Wed, 25 Jul 2007 08:48:21 +0200	[thread overview]
Message-ID: <200707250848.21972.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C2CBF079.12F6E%keir@xensource.com>

On Tuesday 24 July 2007 19:07:53 Keir Fraser wrote:
> 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.
>

Ah, I see. Tnx. It would be really nice to have
some documentation about hypercalls, though.

Christoph




-- 
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy

  parent reply	other threads:[~2007-07-25  6:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 15:47 NMI delivery not correctly working Christoph Egger
2007-07-24 17:07 ` Keir Fraser
2007-07-24 18:26   ` Kaushik Barde
2007-07-25  6:22     ` Keir Fraser
2007-07-25  6:43       ` Kaushik Barde
2007-07-25  6:55         ` Keir Fraser
2007-07-25  6:48   ` Christoph Egger [this message]
2007-07-25  6:57     ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200707250848.21972.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=keir@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.