Re: [PATCH 4/4] kvm: svm: Support KVM_SEV_SNP_PAGE_TYPE_VMSA at SNP_LAUNCH_UPDATE
Sean Christopherson <[email protected]> Wed, 17 Jun 2026 06:37:52 -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:00:39AM -0700, Sean Christopherson wrote: > > On Wed, Jun 17, 2026, J=C3=B6rg R=C3=B6del wrote: > > > (which has happened a couple of times already). > >=20 > > Examples? The SEV features thing jumps to mind, but I don't recall any= others > > off the top of my head. >=20 > I was referring to KVM-induced changes to SEV features, but thought this > happened more than once? Ok, so it took us a few times to learn our lesson. I still don't see that = as a strong argument for new uAPI, especially not for VMSA pages. I am very fir= mly of the opinion that letting anything but the host kernel configure the VMSA= is beyond stupid, but unfortunately we're stuck with AP_CREATION. Expanding t= hat surface has a very, very, VERY high bar to get over.