From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Yang, Sheng" <sheng.yang@intel.com>
Cc: Avi Kivity <avi@qumranet.com>, kvm-devel <kvm@vger.kernel.org>
Subject: VMX: Host NMI triggering on NMI vmexit
Date: Tue, 16 Sep 2008 13:26:41 +0200 [thread overview]
Message-ID: <48CF97F1.9090004@siemens.com> (raw)
Sheng,
out of curiosity: vmx_vcpu_run invokes 'int $2' to trigger a host NMI if
the VM exited due to an external NMI event. According to Intel specs I
have, software-triggered NMIs do not block hardware NMIs. So are we
facing the risk to receive another NMI while running the first handler?
Or will the VM be left with the hardware blocking logic armed? Or does
Linux not care about NMI handler re-entrance?
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next reply other threads:[~2008-09-16 11:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 11:26 Jan Kiszka [this message]
2008-09-19 22:37 ` VMX: Host NMI triggering on NMI vmexit Avi Kivity
2008-09-20 6:55 ` Jan Kiszka
2008-09-22 10:54 ` Jan Kiszka
2008-09-22 11:00 ` Avi Kivity
2008-09-23 5:34 ` Yang, Sheng
2008-09-23 8:47 ` Jan Kiszka
2008-09-23 8:57 ` Yang, Sheng
2008-09-23 8:59 ` Jan Kiszka
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=48CF97F1.9090004@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=sheng.yang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox