KVM: vmx: hyper-v: don't pass EPT configuration info to vmx_hv_remote_flush_tlb()

I'm observing random crashes in multi-vCPU L2 guests running on KVM on
Hyper-V. I bisected the issue to the commit 877ad952be3d ("KVM: vmx: Add
tlb_remote_flush callback support"). Hyper-V TLFS states:

"AddressSpace specifies an address space ID (an EPT PML4 table pointer)"

So apparently, Hyper-V doesn't expect us to pass naked EPTP, only PML4
pointer should be used. Strip off EPT configuration information before
calling into vmx_hv_remote_flush_tlb().

Fixes: 877ad952be3d ("KVM: vmx: Add tlb_remote_flush callback support")
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

authored by Vitaly Kuznetsov and committed by Paolo Bonzini 5f8bb004 4cebf459

Changed files
+5 -1
arch
x86
kvm
+5 -1
arch/x86/kvm/vmx.c
··· 1572 1572 goto out; 1573 1573 } 1574 1574 1575 + /* 1576 + * FLUSH_GUEST_PHYSICAL_ADDRESS_SPACE hypercall needs the address of the 1577 + * base of EPT PML4 table, strip off EPT configuration information. 1578 + */ 1575 1579 ret = hyperv_flush_guest_mapping( 1576 - to_vmx(kvm_get_vcpu(kvm, 0))->ept_pointer); 1580 + to_vmx(kvm_get_vcpu(kvm, 0))->ept_pointer & PAGE_MASK); 1577 1581 1578 1582 out: 1579 1583 spin_unlock(&to_kvm_vmx(kvm)->ept_pointer_lock);