diff options
author | Sean Christopherson <[email protected]> | 2022-08-30 23:15:49 +0000 |
---|---|---|
committer | Paolo Bonzini <[email protected]> | 2022-09-26 12:03:04 -0400 |
commit | eba9799b5a6efe2993cf92529608e4aa8163d73b (patch) | |
tree | e04f9eb4c15250ee78325ec124e03ec80c3d74c4 /tools/perf/scripts/python/flamegraph.py | |
parent | d953540430c5af57f5de97ea9e36253908204027 (diff) |
KVM: VMX: Drop bits 31:16 when shoving exception error code into VMCS
Deliberately truncate the exception error code when shoving it into the
VMCS (VM-Entry field for vmcs01 and vmcs02, VM-Exit field for vmcs12).
Intel CPUs are incapable of handling 32-bit error codes and will never
generate an error code with bits 31:16, but userspace can provide an
arbitrary error code via KVM_SET_VCPU_EVENTS. Failure to drop the bits
on exception injection results in failed VM-Entry, as VMX disallows
setting bits 31:16. Setting the bits on VM-Exit would at best confuse
L1, and at worse induce a nested VM-Entry failure, e.g. if L1 decided to
reinject the exception back into L2.
Cc: [email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Reviewed-by: Jim Mattson <[email protected]>
Reviewed-by: Maxim Levitsky <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions