Re: [PATCH 4/4] kvm: svm: Support KVM_SEV_SNP_PAGE_TYPE_VMSA at SNP_LAUNCH_UPDATE

Sean Christopherson <[email protected]> Tue, 23 Jun 2026 06:40:13 -0700
Newsgroups dev.linux.lists.coconut-svsm,org.kernel.vger.kvm,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
On Wed, Jun 17, 2026, J=C3=B6rg R=C3=B6del wrote:
> On Wed, Jun 17, 2026 at 06:37:52AM -0700, Sean Christopherson wrote:
> > Ok, so it took us a few times to learn our lesson.  I still don't see t=
hat as a
> > strong argument for new uAPI, especially not for VMSA pages.  I am very=
 firmly
> > of the opinion that letting anything but the host kernel configure the =
VMSA is
> > beyond stupid, but unfortunately we're stuck with AP_CREATION.  Expandi=
ng that
> > surface has a very, very, VERY high bar to get over.
>=20
> The strongest argument in my view (and the main reason we are doing this)=
 is
> actually the predictable launch measurement. On SEV-SNP this is a require=
ment
> to use platform VM-identity features like the ID Block.

And I'm saying that unless KVM *can't* provide a predictable launch measure=
ment,
which AIUI isn't the case, then the launch measurement *must* be stable acr=
oss
kernels because it's part of KVM's ABI.  So as I see it, the issue isn't th=
at
KVM is inherently unpredictable, it's that we lack tests to validate a thor=
ny,
subtle piece of KVM's ABI.

In other words, I want tests, not more complexity in KVM.