diff options
| author | Sean Christopherson <seanjc@google.com> | 2023-08-15 23:36:42 +0300 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2023-08-17 21:38:28 +0300 |
| commit | 0497d2ac9b26d015cfafc4655ad9308c30a61810 (patch) | |
| tree | a1072b6599779adc736fb93a9ff591bfbee87e40 /arch/x86/kvm/vmx/nested.c | |
| parent | 1143c0b85c07fc45daf1c33b26ba9320becd6748 (diff) | |
| download | linux-0497d2ac9b26d015cfafc4655ad9308c30a61810.tar.xz | |
KVM: VMX: Check KVM CPU caps, not just VMX MSR support, for XSAVE enabling
Check KVM CPU capabilities instead of raw VMX support for XSAVES when
determining whether or not XSAVER can/should be exposed to the guest.
Practically speaking, it's nonsensical/impossible for a CPU to support
"enable XSAVES" without XSAVES being supported natively. The real
motivation for checking kvm_cpu_cap_has() is to allow using the governed
feature's standard check-and-set logic.
Reviewed-by: Yuan Yao <yuan.yao@intel.com>
Link: https://lore.kernel.org/r/20230815203653.519297-5-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'arch/x86/kvm/vmx/nested.c')
0 files changed, 0 insertions, 0 deletions