From: Sean Christopherson <seanjc@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Tom Lendacky <thomas.lendacky@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 6.12.y 2/3] KVM: SEV: Add an anonymous "psc" struct to track current PSC metadata
Date: Thu, 3 Sep 2026 17:23:14 -0700 [thread overview]
Message-ID: <apoPcpTa7Qy2isaR@google.com> (raw)
In-Reply-To: <20260902-daily-reply-0017-kvm-sev-psc-nak-6-12@kernel.org>
On Wed, Sep 02, 2026, Sasha Levin wrote:
> > 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.
>
> Yes, this is a complex one :(
>
> How do you see this series then? it's a lot to backport, but if you're okay
> with it...
Ya, backport the whole thing up through d1a3c2162334. It's a lot of patches, but
IMO the risk of breaking something by trying to trim down the backport is
significantly higher than the risk of those backports.
next prev parent reply other threads:[~2026-09-04 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 12:25 FAILED: patch "[PATCH] KVM: SEV: Mark vCPU RUNNABLE after AP_CREATE, even if VMSA is" failed to apply to 6.12-stable tree gregkh
2026-08-31 21:10 ` [PATCH 6.12.y 1/3] KVM: SEV: Make it more obvious when KVM is writing back the current PSC index Sasha Levin
2026-08-31 21:10 ` [PATCH 6.12.y 2/3] KVM: SEV: Add an anonymous "psc" struct to track current PSC metadata Sasha Levin
2026-09-01 19:01 ` Sean Christopherson
2026-09-02 22:14 ` Sasha Levin
2026-09-04 0:23 ` Sean Christopherson [this message]
2026-09-06 13:32 ` Sasha Levin
2026-08-31 21:10 ` [PATCH 6.12.y 3/3] KVM: SEV: Mark vCPU RUNNABLE after AP_CREATE, even if VMSA is unusable Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=apoPcpTa7Qy2isaR@google.com \
--to=seanjc@google.com \
--cc=pbonzini@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox