OSDN Git Service

x86/KVM/nVMX: don't use clean fields data on enlightened VMLAUNCH
authorVitaly Kuznetsov <vkuznets@redhat.com>
Fri, 28 Jun 2019 11:23:32 +0000 (13:23 +0200)
committerPaolo Bonzini <pbonzini@redhat.com>
Tue, 2 Jul 2019 16:56:00 +0000 (18:56 +0200)
commita21a39c206f8a541ce9670666c0025d73383aa1a
treeb61f9a71f1617fce96c3a7dde210c577595e776b
parent95c5c7c77c06c7037385b3d8d4d7592ab032c3cb
x86/KVM/nVMX: don't use clean fields data on enlightened VMLAUNCH

Apparently, Windows doesn't maintain clean fields data after it does
VMCLEAR for an enlightened VMCS so we can only use it on VMRESUME.
The issue went unnoticed because currently we do nested_release_evmcs()
in handle_vmclear() and the consecutive enlightened VMPTRLD invalidates
clean fields when a new eVMCS is mapped but we're going to change the
logic.

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
arch/x86/kvm/vmx/nested.c