All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "Yang, Sheng" <sheng.yang@intel.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: VMX: Host NMI triggering on NMI vmexit
Date: Mon, 22 Sep 2008 14:00:38 +0300	[thread overview]
Message-ID: <48D77AD6.8030008@redhat.com> (raw)
In-Reply-To: <48D7795E.5080002@siemens.com>

Jan Kiszka wrote:
>> Maybe the answer is to generate the local nmi via an IPI-to-self command
>> to the local apic.
>>     
>
> Going this way leaves me with a few questions: Will it be OK for the
> related mainainers to export the required service? 

If we can make a case for it (I think we can), then I don't see why not.

Sheng, can you confirm that 'int 2' is problematic, and that 
nmi-via-lapic is the best workaround?

> And is it safe to
> assume VMX == LAPIC available and usable?
>
>   

Yes.

> However, this is how it would look like. 

I'd define a send_nmi_self() instead, to allow the implementation to 
change (x2apic/etc).

> Yet untested, /me has to
> replace his host kernel first...
>   

You could test it in a VM, if someone implements nested vmx :)

btw, looks like svm is not affected by this.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-09-22 11:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 11:26 VMX: Host NMI triggering on NMI vmexit Jan Kiszka
2008-09-19 22:37 ` Avi Kivity
2008-09-20  6:55   ` Jan Kiszka
2008-09-22 10:54   ` Jan Kiszka
2008-09-22 11:00     ` Avi Kivity [this message]
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=48D77AD6.8030008@redhat.com \
    --to=avi@redhat.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.