From: Sean Christopherson <seanjc@google.com>
To: Ashish Kalra <Ashish.Kalra@amd.com>
Cc: pbonzini@redhat.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, thomas.lendacky@amd.com, john.allen@amd.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
joro@8bytes.org, suravee.suthikulpanit@amd.com, will@kernel.org,
robin.murphy@arm.com, michael.roth@amd.com,
dionnaglaze@google.com, nikunj@amd.com, ardb@kernel.org,
kevinloughlin@google.com, Neeraj.Upadhyay@amd.com,
vasant.hegde@amd.com, Stable@vger.kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-coco@lists.linux.dev,
iommu@lists.linux.dev
Subject: Re: [PATCH v4 0/3] Fix broken SNP support with KVM module built-in
Date: Tue, 11 Feb 2025 13:31:54 -0800 [thread overview]
Message-ID: <Z6vByjY9t8X901hQ@google.com> (raw)
In-Reply-To: <cover.1739226950.git.ashish.kalra@amd.com>
On Mon, Feb 10, 2025, Ashish Kalra wrote:
> Ashish Kalra (1):
> x86/sev: Fix broken SNP support with KVM module built-in
>
> Sean Christopherson (2):
> crypto: ccp: Add external API interface for PSP module initialization
> KVM: SVM: Ensure PSP module is initialized if KVM module is built-in
Unless I've overlooked a dependency, patch 3 (IOMMU vs. RMP) is entirely
independent of patches 1 and 2 (PSP vs. KVM). If no one objects, I'll take the
first two patches through the kvm-x86 tree, and let the tip/iommu maintainers
sort out the last patch.
> arch/x86/include/asm/sev.h | 2 ++
> arch/x86/kvm/svm/sev.c | 10 ++++++++++
> arch/x86/virt/svm/sev.c | 23 +++++++----------------
> drivers/crypto/ccp/sp-dev.c | 14 ++++++++++++++
> drivers/iommu/amd/init.c | 34 ++++++++++++++++++++++++++++++----
> include/linux/psp-sev.h | 9 +++++++++
> 6 files changed, 72 insertions(+), 20 deletions(-)
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-02-11 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 22:53 [PATCH v4 0/3] Fix broken SNP support with KVM module built-in Ashish Kalra
2025-02-10 22:53 ` [PATCH v4 1/3] crypto: ccp: Add external API interface for PSP module initialization Ashish Kalra
2025-02-10 22:54 ` [PATCH v4 2/3] KVM: SVM: Ensure PSP module is initialized if KVM module is built-in Ashish Kalra
2025-02-10 22:54 ` [PATCH v4 3/3] x86/sev: Fix broken SNP support with KVM module built-in Ashish Kalra
2025-02-13 7:42 ` Joerg Roedel
2025-02-11 21:31 ` Sean Christopherson [this message]
2025-02-14 23:38 ` [PATCH v4 0/3] " Paolo Bonzini
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=Z6vByjY9t8X901hQ@google.com \
--to=seanjc@google.com \
--cc=Ashish.Kalra@amd.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=Stable@vger.kernel.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dionnaglaze@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux.dev \
--cc=john.allen@amd.com \
--cc=joro@8bytes.org \
--cc=kevinloughlin@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).