diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2025-07-28 11:37:05 -0400 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2025-07-29 08:36:45 -0400 |
| commit | 0097f9df996fe9c4a66a9f96a492391a8432affd (patch) | |
| tree | 0805e366df034da24fdadb7817de4d106cf98134 | |
| parent | b4733cd5be1a284cd92840f3126e4165ab34460c (diff) | |
| parent | 24be2b7956a545945fcb560d42e3ea86406dba09 (diff) | |
Merge tag 'kvm-x86-svm-6.17' of https://github.com/kvm-x86/linux into HEAD
KVM SVM changes for 6.17
Drop KVM's rejection of SNP's SMT and single-socket policy restrictions, and
instead rely on firmware to verify that the policy can actually be supported.
Don't bother checking that requested policy(s) can actually be satisfied, as
an incompatible policy doesn't put the kernel at risk in any way, and providing
guarantees with respect to the physical topology is outside of KVM's purview.
| -rw-r--r-- | arch/x86/kvm/svm/sev.c | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c index d061ebb430ce..fde328ed3f78 100644 --- a/arch/x86/kvm/svm/sev.c +++ b/arch/x86/kvm/svm/sev.c @@ -2135,11 +2135,7 @@ static int snp_launch_start(struct kvm *kvm, struct kvm_sev_cmd *argp) return -EINVAL; /* Check for policy bits that must be set */ - if (!(params.policy & SNP_POLICY_MASK_RSVD_MBO) || - !(params.policy & SNP_POLICY_MASK_SMT)) - return -EINVAL; - - if (params.policy & SNP_POLICY_MASK_SINGLE_SOCKET) + if (!(params.policy & SNP_POLICY_MASK_RSVD_MBO)) return -EINVAL; sev->policy = params.policy; |
