From: Ladi Prosek <lprosek@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, rkrcmar@redhat.com, bsd@redhat.com
Subject: [PATCH v3 0/4] KVM: nVMX: fix CR3 load if L2 uses PAE paging and EPT
Date: Wed, 30 Nov 2016 16:03:07 +0100 [thread overview]
Message-ID: <1480518191-4572-1-git-send-email-lprosek@redhat.com> (raw)
The series addresses a specific issue with guest CR3 load on nested vmentry
as well as a few additional changes related to handling guest and host CR3.
v2->v3:
* split to 4 patches
* fixed the error code used on host PDPTE load failure
* added a vmentry host CR3 validity check + new nested_cr3_valid helper
v1->v2:
* introduced nested_vmx_load_cr3 (more error handling, less MMU work)
* also handles nested exit in addition to nested entry
* amended commit description
Ladi Prosek (4):
KVM: nVMX: fix CR3 load if L2 uses PAE paging and EPT
KVM: nVMX: propagate errors from prepare_vmcs02
KVM: nVMX: introduce nested_vmx_load_cr3 and call it on vmentry
KVM: nVMX: check host CR3 on vmexit
next reply other threads:[~2016-11-30 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 15:03 Ladi Prosek [this message]
2016-11-30 15:03 ` [PATCH v3 1/4] KVM: nVMX: fix CR3 load if L2 uses PAE paging and EPT Ladi Prosek
2016-12-21 7:31 ` Wanpeng Li
2016-12-21 8:09 ` Ladi Prosek
2016-12-21 12:20 ` Wanpeng Li
2016-11-30 15:03 ` [PATCH v3 2/4] KVM: nVMX: propagate errors from prepare_vmcs02 Ladi Prosek
2016-11-30 15:03 ` [PATCH v3 3/4] KVM: nVMX: introduce nested_vmx_load_cr3 and call it on vmentry Ladi Prosek
2016-11-30 15:03 ` [PATCH v3 4/4] KVM: nVMX: check host CR3 on vmentry and vmexit Ladi Prosek
2016-12-01 14:18 ` [PATCH v3 0/4] KVM: nVMX: fix CR3 load if L2 uses PAE paging and EPT Radim Krčmář
2016-12-01 15:00 ` Ladi Prosek
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=1480518191-4572-1-git-send-email-lprosek@redhat.com \
--to=lprosek@redhat.com \
--cc=bsd@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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