summaryrefslogtreecommitdiffstats
path: root/arch/x86/crypto/chacha20-avx2-x86_64.S
diff options
context:
space:
mode:
authorVitaly Kuznetsov <vkuznets@redhat.com>2018-10-11 12:03:12 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2018-10-13 11:38:54 +0200
commit5f8bb004bca43f7b5043c02b4aa5b9b43e15fe50 (patch)
tree9fa36531e4f2a6980e5a82a5370247966d3eeea3 /arch/x86/crypto/chacha20-avx2-x86_64.S
parentMerge tag 'kvmarm-fixes-for-4.19-2' of git://git.kernel.org/pub/scm/linux/ker... (diff)
downloadlinux-5f8bb004bca43f7b5043c02b4aa5b9b43e15fe50.tar.xz
linux-5f8bb004bca43f7b5043c02b4aa5b9b43e15fe50.zip
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>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions