Re: [PATCH 1/2] KVM: nVMX: Implement EPTP switching for the L1 hypervisor

2017-06-30 Thread Paolo Bonzini
> > What happens if the root_hpa is dropped by the L0 MMU? I'm not sure > > what removes it from the shadow EPT list. > > That would result in a vmfunc vmexit, which will jump to handle_vmfunc > and then a call to mmu_alloc_shadow_roots() that will overwrite the shadow > eptp entry with the new

Re: [PATCH 1/2] KVM: nVMX: Implement EPTP switching for the L1 hypervisor

2017-06-30 Thread Bandan Das
Hi Paolo, Paolo Bonzini writes: > - Original Message - >> From: "Bandan Das" >> To: k...@vger.kernel.org >> Cc: pbonz...@redhat.com, linux-kernel@vger.kernel.org >> Sent: Friday, June 30, 2017 1:29:55 AM >> Subject: [PATCH 1/2] KVM

Re: [PATCH 1/2] KVM: nVMX: Implement EPTP switching for the L1 hypervisor

2017-06-30 Thread Paolo Bonzini
- Original Message - > From: "Bandan Das" > To: k...@vger.kernel.org > Cc: pbonz...@redhat.com, linux-kernel@vger.kernel.org > Sent: Friday, June 30, 2017 1:29:55 AM > Subject: [PATCH 1/2] KVM: nVMX: Implement EPTP switching for the L1 hypervisor >

[PATCH 1/2] KVM: nVMX: Implement EPTP switching for the L1 hypervisor

2017-06-29 Thread Bandan Das
This is a mix of emulation/passthrough to implement EPTP switching for the nested hypervisor. If the shadow EPT are absent, a vmexit occurs with reason 59. L0 can then create shadow structures based on the entry that the guest calls with to obtain a new root_hpa that can be written to the shadow l