[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z6vByjY9t8X901hQ@google.com>
Date: Tue, 11 Feb 2025 13:31:54 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Ashish Kalra <Ashish.Kalra@....com>
Cc: pbonzini@...hat.com, tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
thomas.lendacky@....com, john.allen@....com, herbert@...dor.apana.org.au,
davem@...emloft.net, joro@...tes.org, suravee.suthikulpanit@....com,
will@...nel.org, robin.murphy@....com, michael.roth@....com,
dionnaglaze@...gle.com, nikunj@....com, ardb@...nel.org,
kevinloughlin@...gle.com, Neeraj.Upadhyay@....com, vasant.hegde@....com,
Stable@...r.kernel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-coco@...ts.linux.dev,
iommu@...ts.linux.dev
Subject: Re: [PATCH v4 0/3] Fix broken SNP support with KVM module built-in
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
>
Powered by blists - more mailing lists