diff options
| author | Sean Christopherson <[email protected]> | 2023-05-03 09:08:36 -0700 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2023-05-21 04:05:51 -0400 |
| commit | ad45413d22e6a224f8530b6fcc9ac01c8ced7fd6 (patch) | |
| tree | 000e181725c801bf46bc8f0a135b00c4c86235e3 /lib/crypto/utils.c | |
| parent | afb2acb2e3a32e4d56f7fbd819769b98ed1b7520 (diff) | |
KVM: VMX: Don't rely _only_ on CPUID to enforce XCR0 restrictions for ECREATE
Explicitly check the vCPU's supported XCR0 when determining whether or not
the XFRM for ECREATE is valid. Checking CPUID works because KVM updates
guest CPUID.0x12.1 to restrict the leaf to a subset of the guest's allowed
XCR0, but that is rather subtle and KVM should not modify guest CPUID
except for modeling true runtime behavior (allowed XFRM is most definitely
not "runtime" behavior).
Reviewed-by: Kai Huang <[email protected]>
Tested-by: Kai Huang <[email protected]>
Signed-off-by: Sean Christopherson <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'lib/crypto/utils.c')
0 files changed, 0 insertions, 0 deletions