Re: [PATCH 6.12.y 2/3] KVM: SEV: Add an anonymous "psc" struct to track current PSC metadata

[Sean Christopherson <seanjc@google.com>]

On Mon, Aug 31, 2026, Sasha Levin wrote:
> From: Sean Christopherson <seanjc@google.com>
> 
> [ Upstream commit 00b9744a3688758c5c492756d08a1cd599a76965 ]
> 
> Add a "psc" struct to vcpu_sev_es_state to avoid having to prefix all of
> the fields with "psc_".
> 
> Take advantage of the code churn to opportunistically rename local
> variables to "guest_psc" to make it more obvious that the buffer is guest
> data, and more importantly, guest accessible!
> 
> Opportunistically rename inflight => batch_size as well, because there can
> really only be one operation in-flight (per-vCPU), i.e. "inflight" _looks_
> like a boolean, but in actuality is an integer tracking how many pages are
> being handled by the current operation.
> 
> No functional change intended.
> 
> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> Message-ID: <20260501202250.2115252-13-seanjc@google.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> Message-ID: <20260529183549.1104619-13-pbonzini@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> 
> For the 6.12 backport, retain the existing GHCB response write because the
> newer VMGEXIT response helper is not available.  Also fold in the VMSA GPA
> tracking and helper refactoring needed by the dependent AP_CREATE fix,
> adapting them to the 6.12 gmem and MP-state APIs and existing reset hook
> without adding a new function.

NAK.

As the first sentence says, grabbing 00b9744a3688 ("KVM: SEV: Add an anonymous
"psc" struct to track current PSC metadata") only requires handling a superficial
syntactic conflict.  This mixes in pieces of d1a3c2162334 ("KVM: SEV: Forcefully
invalidate SNP VMSA if its backing gmem page is zapped"), and *that* is the
commit that's by far the most interesting.  I.e. pretty much all of this is
leading up to that commit, not these intermediate commits.