From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 54461] New: nVMX: Downgrading nested VMX features from user-space
Date: Mon, 25 Feb 2013 13:50:21 +0000 (UTC) [thread overview]
Message-ID: <bug-54461-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=54461
Summary: nVMX: Downgrading nested VMX features from user-space
Product: Virtualization
Version: unspecified
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: enhancement
Priority: P1
Component: kvm
AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
ReportedBy: nyh@math.technion.ac.il
Regression: No
In nested SVM, the sub-features of SVM are all part of CPUID, so we already
have a user-space interface (KVM_GET_SUPPORTED_CPUID/KVM_SET_CPUID2) to set a
guest's features - which is, for example, useful for dictating a fixed set of
features across different hosts.
However, in nested VMX, the VMX sub-features offered or not to the guest are
not in CPUID, but rather in MSRs, and currently the
nested_vmx_setup_ctls_msrs() function determines their value - without any
option for user space to control this. We need some sort of new
KVM_SET_READONLY_MSRS ioctl for overriding (downgrading)
nested_vmx_setup_ctls_msrs()'s decisions for a particular guest.
--
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-25 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 13:50 bugzilla-daemon [this message]
2013-02-25 13:51 ` [Bug 54461] nVMX: Downgrading nested VMX features from user-space bugzilla-daemon
2015-03-17 3:53 ` 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-54461-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 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.