From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 53631] New: nVMX: Support exit/entry MSR load/store
Date: Mon, 11 Feb 2013 14:21:24 +0000 (UTC) [thread overview]
Message-ID: <bug-53631-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=53631
Summary: nVMX: Support exit/entry MSR load/store
Product: Virtualization
Version: unspecified
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
ReportedBy: nyh@math.technion.ac.il
Regression: No
Currently, nested VMX does not allow L1 to use the MSR load/store feature on
entry/exit. The code fails entry (from L1 to L2) if these VMCS features are
used:
if (vmcs12->vm_entry_msr_load_count > 0 ||
vmcs12->vm_exit_msr_load_count > 0 ||
vmcs12->vm_exit_msr_store_count > 0) {
pr_warn_ratelimited("%s: VMCS MSR_{LOAD,STORE} unsupported\n",
__func__);
nested_vmx_failValid(vcpu, VMXERR_ENTRY_INVALID_CONTROL_FIELD);
return 1;
}
This was not a big problem if L1 is also KVM, because KVM didn't use this
feature - it only uses it in case of EPT for switching the EFER (see
explanation in http://kerneltrap.org/mailarchive/linux-kvm/2010/5/2/6261577),
and in that case there is a simpler alternative: supporting
VM_ENTRY/EXIT_LOAD_IA32_EFER is enough. So this is what we did in the nested
EPT patches proposed in bug 53611.
However, it is likely that for different L1s (or even KVM in the future), we'll
need to support the generic MSR load/store feature.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2013-02-11 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 14:21 bugzilla-daemon [this message]
2013-02-11 14:21 ` [Bug 53631] nVMX: Support exit/entry MSR load/store bugzilla-daemon
2013-02-26 15:21 ` bugzilla-daemon
2015-03-17 3:53 ` bugzilla-daemon
2015-04-08 8:57 ` bugzilla-daemon
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=bug-53631-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/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