From: Bandan Das <bsd@redhat.com>
To: kvm@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Gleb Natapov <gleb@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] Emulate VMXON region correctly
Date: Tue, 6 May 2014 02:19:14 -0400 [thread overview]
Message-ID: <1399357158-8305-1-git-send-email-bsd@redhat.com> (raw)
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=54521
The vmxon region is unused by nvmx, but adding these checks
are probably harmless and may detect buggy L1 hypervisors in
the future!
v2:
1/4
- Commit message change to reflect addition of new function
2/4
- Use cpuid_maxphyaddr()
- Fix a leak with kunmap()
- Remove unnecessary braces around comparisions
- Move all checks into a common function, this will be later
used by handle_vmptrld and handle_vmclear in 4/4
4/4
- New patch - use common function to perform checks on
vmptr
Bandan Das (4):
KVM: nVMX: rearrange get_vmx_mem_address
KVM: nVMX: additional checks on vmxon region
KVM: nVMX: fail on invalid vmclear/vmptrld pointer
KVM: nVMX: move vmclear and vmptrld pre-checks to
nested_vmx_check_vmptr
arch/x86/kvm/cpuid.c | 1 +
arch/x86/kvm/vmx.c | 240 +++++++++++++++++++++++++++++++++------------------
2 files changed, 156 insertions(+), 85 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-05-06 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 6:19 Bandan Das [this message]
2014-05-06 6:19 ` [PATCH v2 1/4] KVM: nVMX: rearrange get_vmx_mem_address Bandan Das
2014-05-06 6:19 ` [PATCH v2 2/4] KVM: nVMX: additional checks on vmxon region Bandan Das
2014-05-06 6:19 ` [PATCH v2 3/4] KVM: nVMX: fail on invalid vmclear/vmptrld pointer Bandan Das
2014-05-06 6:19 ` [PATCH v2 4/4] KVM: nVMX: move vmclear and vmptrld pre-checks to nested_vmx_check_vmptr Bandan Das
2014-05-06 17:01 ` [PATCH v2 0/4] Emulate VMXON region correctly Paolo Bonzini
2014-06-03 20:11 ` Bandan Das
2014-06-04 7:18 ` 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=1399357158-8305-1-git-send-email-bsd@redhat.com \
--to=bsd@redhat.com \
--cc=gleb@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome