diff options
| author | Vitaly Kuznetsov <vkuznets@redhat.com> | 2019-06-28 13:23:32 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2019-07-02 18:56:00 +0200 |
| commit | a21a39c206f8a541ce9670666c0025d73383aa1a (patch) | |
| tree | b61f9a71f1617fce96c3a7dde210c577595e776b /tools/thermal | |
| parent | 95c5c7c77c06c7037385b3d8d4d7592ab032c3cb (diff) | |
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>
Diffstat (limited to 'tools/thermal')
0 files changed, 0 insertions, 0 deletions