From: Avi Kivity <avi@redhat.com>
To: "Nadav Har'El" <nyh@math.technion.ac.il>
Cc: Julian Stecklina <js@alien8.de>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Enable VMX-related bits in MSR_IA32_FEATURE_CONTROL.
Date: Wed, 07 Mar 2012 12:07:35 +0200 [thread overview]
Message-ID: <4F573367.5000707@redhat.com> (raw)
In-Reply-To: <20120306173308.GA20590@fermat.math.technion.ac.il>
On 03/06/2012 07:33 PM, Nadav Har'El wrote:
> On Tue, Mar 06, 2012, Nadav Har'El wrote about "Re: [PATCH] KVM: Enable VMX-related bits in MSR_IA32_FEATURE_CONTROL.":
> > 2. handle_vmon() does not check the previous setting of this MSR.
> > If the guest (or its BIOS) doesn't set both FEATURE_CONTROL_LOCKED
> > and FEATURE_CONTROL_VMXON_ENABLED_OUTSIDE_SMX, it should get a
>
> By the way, am I right in my understanding that KVM doesn't support
> SMX in the guest?
Isn't nested vmx crazy enough?
btw, any updates on nested EPT? Nested vmx is pointless without it.
> I didn't see mention of CR4.SMXE or a GETSEC exit
> handler, which is why I'm assuming that it doesn't...
> If this assumption isn't true, I'll also need to worry about the
> ..._INSIDE_SMX case.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-03-07 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 15:02 [PATCH] KVM: Enable VMX-related bits in MSR_IA32_FEATURE_CONTROL Julian Stecklina
2012-03-06 15:13 ` Avi Kivity
2012-03-06 15:25 ` Julian Stecklina
2012-03-06 15:47 ` Nadav Har'El
2012-03-06 16:45 ` Julian Stecklina
2012-03-06 17:33 ` Nadav Har'El
2012-03-07 10:07 ` Avi Kivity [this message]
2012-03-07 11:10 ` Nadav Har'El
2012-03-07 14:14 ` 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=4F573367.5000707@redhat.com \
--to=avi@redhat.com \
--cc=js@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=nyh@math.technion.ac.il \
/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