diff options
| author | Sean Christopherson <[email protected]> | 2022-08-30 15:37:18 +0200 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2022-09-26 12:02:47 -0400 |
| commit | 3ff8a13d41b283932ec6ac692c6def22a157269b (patch) | |
| tree | 1cdba85ae6b602dcfff5cd7e666d2bec889980a4 /arch/x86/kvm/hyperv.c | |
| parent | 8174193163095238e70e0decd121feb4b9ef8cc0 (diff) | |
KVM: nVMX: WARN once and fail VM-Enter if eVMCS sees VMFUNC[63:32] != 0
WARN and reject nested VM-Enter if KVM is using eVMCS and manages to
allow a non-zero value in the upper 32 bits of VM-function controls. The
eVMCS code assumes all inputs are 32-bit values and subtly drops the
upper bits. WARN instead of adding proper "support", it's unlikely the
upper bits will be defined/used in the next decade.
Signed-off-by: Sean Christopherson <[email protected]>
Signed-off-by: Vitaly Kuznetsov <[email protected]>
Signed-off-by: Sean Christopherson <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'arch/x86/kvm/hyperv.c')
0 files changed, 0 insertions, 0 deletions