From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 54521] New: nVMX: accurately emulate VMXON region
Date: Tue, 26 Feb 2013 15:07:20 +0000 (UTC) [thread overview]
Message-ID: <bug-54521-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=54521
Summary: nVMX: accurately emulate VMXON region
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
According to the VMX spec, the VMXON instruction takes a "VMXON region", a 4096
byte memory region which the VMX implementation (in this case, our emulation in
nested VMX) may use for its needs.
We currently have no need to for this memory area, because when our
implementation needs to store extra data, it stores it in the vmx_vcpu
structure (in L0 memory). However, we may want to store data in guest memory in
the future - e.g. for making it easier to do live migration (see bug 53851).
In any case, according to the VMX spec, the VMXON instruction is supposed to
verify that the memory pointed by the VMXON operand is 4K aligned and has the
right physical address width, and its content has the right VMCS revision field
(copied from VMX_BASIC). We don't do this currently.
Moreover, according to the spec, VMXON needs to save this pointer, and on
VMPTRLD/VMCLEAR we need to verify that the given VMCS pointer is not the VMXON
region.
--
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-26 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 15:07 bugzilla-daemon [this message]
2013-02-26 15:08 ` [Bug 54521] nVMX: accurately emulate VMXON region bugzilla-daemon
2014-06-12 16:52 ` bugzilla-daemon
2014-06-13 13:01 ` 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-54521-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