diff options
| author | Sean Christopherson <[email protected]> | 2022-05-27 17:06:57 +0000 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2022-06-08 13:06:18 -0400 |
| commit | f5a81d0eb01e0dfebd175edffa7d0a1bdb74d026 (patch) | |
| tree | 89384f4b5b8065e7408760635ba07277d9dec797 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 8e6a58e28b34e8d247e772159b8fa8f6bae39192 (diff) | |
KVM: VMX: Sanitize VM-Entry/VM-Exit control pairs at kvm_intel load time
Sanitize the VM-Entry/VM-Exit control pairs (load+load or load+clear)
during setup instead of checking both controls in a pair at runtime. If
only one control is supported, KVM will report the associated feature as
not available, but will leave the supported control bit set in the VMCS
config, which could lead to corruption of host state. E.g. if only the
VM-Entry control is supported and the feature is not dynamically toggled,
KVM will set the control in all VMCSes and load zeros without restoring
host state.
Note, while this is technically a bug fix, practically speaking no sane
CPU or VMM would support only one control. KVM's behavior of checking
both controls is mostly pedantry.
Cc: Chenyi Qiang <[email protected]>
Cc: Lei Wang <[email protected]>
Signed-off-by: Sean Christopherson <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions