[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250725220713.264711-12-seanjc@google.com>
Date: Fri, 25 Jul 2025 15:07:11 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Sean Christopherson <seanjc@...gle.com>
Subject: [GIT PULL] KVM: x86: SVM changes for 6.17
Two small SNP changes. I initially balked at completely dropping KVM's checks,
but I can't think of any way this will cause ABI problems, and I also don't see
how having KVM perform checks would add value in any way. So here they are :-)
The following changes since commit 28224ef02b56fceee2c161fe2a49a0bb197e44f5:
KVM: TDX: Report supported optional TDVMCALLs in TDX capabilities (2025-06-20 14:20:20 -0400)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-svm-6.17
for you to fetch changes up to 24be2b7956a545945fcb560d42e3ea86406dba09:
KVM: SVM: Allow SNP guest policy to specify SINGLE_SOCKET (2025-06-20 13:33:45 -0700)
----------------------------------------------------------------
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.
----------------------------------------------------------------
Tom Lendacky (2):
KVM: SVM: Allow SNP guest policy disallow running with SMT enabled
KVM: SVM: Allow SNP guest policy to specify SINGLE_SOCKET
arch/x86/kvm/svm/sev.c | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
Powered by blists - more mailing lists