lkml.org 
[lkml]   [2017]   [Jul]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Subject[PATCH v3 0/3] Expose VMFUNC to the nested hypervisor
    Date

    v3:
    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 | 125 ++++++++++++++++++++++++++++++++++++++++++++-
    2 files changed, 132 insertions(+), 2 deletions(-)

    --
    2.9.4

    \
     
     \ /
      Last update: 2017-07-10 21:55    [W:3.602 / U:0.060 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site