From: Bandan Das <bsd@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, david@redhat.com, rkrcmar@redhat.com,
jmattson@google.com, linux-kernel@vger.kernel.org
Subject: [PATCH v6 0/3] Expose VMFUNC to the nested hypervisor
Date: Tue, 1 Aug 2017 19:24:30 -0400 [thread overview]
Message-ID: <20170801232433.31749-1-bsd@redhat.com> (raw)
v6:
3/3:
Fix check for memory type in address
Change check function name as requested in the review
Move setting of mmu->ept_ad to after calling mmu_unload
and also reset base_role.ad_disabled appropriately
Replace IS_ALIGN with page_address_valid()
v5:
https://lkml.org/lkml/2017/7/28/621
1/3 and 2/3 are unchanged but some changes in 3/3. I left
the mmu_load failure path untouched because I am not sure what's
the right thing to do here.
3/3:
Move the eptp switching logic to a different function
Add check for EPTP_ADDRESS in check_vmentry_prereq
Add check for validity of ept pointer
Check if AD bit is set and set ept_ad
Add TODO item about mmu_unload failure
v4:
https://lkml.org/lkml/2017/7/10/705
2/3: Use WARN_ONCE to avoid logging dos
v3:
https://lkml.org/lkml/2017/7/10/684
3/3: Add missing nested_release_page_clean() and check the
eptp as mentioned in SDM 24.6.14
v2:
https://lkml.org/lkml/2017/7/6/813
1/3: Patch to enable vmfunc on the host but cause a #UD if
L1 tries to use it directly. (new)
2/3: Expose vmfunc to the nested hypervisor, but no vm functions
are exposed and L0 emulates a vmfunc vmexit to L1.
3/3: Force a vmfunc vmexit when L2 tries to use vmfunc and emulate
eptp switching. Unconditionally expose EPTP switching to the
L1 hypervisor since L0 fakes eptp switching via a mmu reload.
These patches expose eptp switching/vmfunc to the nested hypervisor.
vmfunc is enabled in the secondary controls for the host and is
exposed to the nested hypervisor. However, if the nested hypervisor
decides to use eptp switching, L0 emulates it.
v1:
https://lkml.org/lkml/2017/6/29/958
Bandan Das (3):
KVM: vmx: Enable VMFUNCs
KVM: nVMX: Enable VMFUNC for the L1 hypervisor
KVM: nVMX: Emulate EPTP switching for the L1 hypervisor
arch/x86/include/asm/vmx.h | 9 +++
arch/x86/kvm/vmx.c | 191 ++++++++++++++++++++++++++++++++++++++++++++-
2 files changed, 198 insertions(+), 2 deletions(-)
--
2.9.4
next reply other threads:[~2017-08-01 23:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 23:24 Bandan Das [this message]
2017-08-01 23:24 ` [PATCH v6 1/3] KVM: vmx: Enable VMFUNCs Bandan Das
2017-08-01 23:24 ` [PATCH v6 2/3] KVM: nVMX: Enable VMFUNC for the L1 hypervisor Bandan Das
2017-08-01 23:24 ` [PATCH 3/3] KVM: nVMX: Emulate EPTP switching " Bandan Das
2017-08-03 11:39 ` David Hildenbrand
2017-08-03 12:41 ` Paolo Bonzini
2017-08-03 12:47 ` David Hildenbrand
2017-08-03 19:55 ` Bandan Das
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=20170801232433.31749-1-bsd@redhat.com \
--to=bsd@redhat.com \
--cc=david@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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