All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "Yang, Sheng" <sheng.yang@intel.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: VMX: NMI injection without virtual NMI support
Date: Sat, 13 Sep 2008 08:14:18 +0300	[thread overview]
Message-ID: <48CB4C2A.5030804@qumranet.com> (raw)
In-Reply-To: <48CA298A.8080404@siemens.com>

Jan Kiszka wrote:
> Well, I thought in this direction already as well. But I wasn't sure if,
> while the guest is in NMI context, hard IRQs will also be blocked and
> won't cause guest exists anymore. Can you comment on this?
>
> However, even if that is no issue, I do not really like this workaround.
> Specifically the need to fiddle with the guest's IDT and, of course,
> that we may delays host NMIs.
>
> I'm now playing with this idea, basically a "light" version of yours:
> After we injected an NMI, consider the guest being in NMI context until
> the next IRQ window opens. That may cause lost NMIs if the guest blocks
> IRQ delivery infinitely, but I would say this is rather untypical and
> still much better than the current situation (no NMIs at all!). And it
> is easier to implement. Comments?
>
>
>   


In some cases misbehaving NMIs are worse than no NMIs.  For example, a
software watchdog may use NMIs to monitor a system.  But if the guest
spins with interrupts disabled, the irq window will never open, and NMIs
will never be delivered, so the watchdog will deliver a false negative.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2008-09-13  5:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 15:11 VMX: NMI injection without virtual NMI support Jan Kiszka
2008-09-12  6:29 ` Yang, Sheng
2008-09-12  8:34   ` Jan Kiszka
2008-09-13  5:14     ` Avi Kivity [this message]
2008-09-13  6:27       ` Jan Kiszka
2008-09-13  8:58         ` Avi Kivity

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=48CB4C2A.5030804@qumranet.com \
    --to=avi@qumranet.com \
    --cc=jan.kiszka@siemens.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 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.