From: Sean Christopherson <seanjc@google.com>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: Ashish Kalra <Ashish.Kalra@amd.com>,
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,
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 v3 3/3] x86/sev: Fix broken SNP support with KVM module built-in
Date: Wed, 5 Feb 2025 07:17:08 -0800 [thread overview]
Message-ID: <Z6OA9OhxBgsTY2ni@google.com> (raw)
In-Reply-To: <62b643dd-36d9-4b8d-bed6-189d84eeab59@amd.com>
On Wed, Feb 05, 2025, Vasant Hegde wrote:
> Hi Ashish,
>
> [Sorry. I didn't see this series and responded to v2].
Heh, and then I saw your other email first and did the same. Copying my response
here, too (and fixing a few typos in the process).
> > diff --git a/drivers/iommu/amd/init.c b/drivers/iommu/amd/init.c
> > index c5cd92edada0..4bcb474e2252 100644
> > --- a/drivers/iommu/amd/init.c
> > +++ b/drivers/iommu/amd/init.c
> > @@ -3194,7 +3194,7 @@ static bool __init detect_ivrs(void)
> > return true;
> > }
> >
> > -static void iommu_snp_enable(void)
> > +static __init void iommu_snp_enable(void)
> > {
> > #ifdef CONFIG_KVM_AMD_SEV
> > if (!cc_platform_has(CC_ATTR_HOST_SEV_SNP))
> > @@ -3219,6 +3219,14 @@ static void iommu_snp_enable(void)
> > goto disable_snp;
> > }
> >
> > + /*
> > + * Enable host SNP support once SNP support is checked on IOMMU.
> > + */
> > + if (snp_rmptable_init()) {
> > + pr_warn("SNP: RMP initialization failed, SNP cannot be supported.\n");
> > + goto disable_snp;
> > + }
> > +
> > pr_info("IOMMU SNP support enabled.\n");
> > return;
> >
> > @@ -3318,6 +3326,9 @@ static int __init iommu_go_to_state(enum iommu_init_state state)
> > ret = state_next();
> > }
> >
> > + if (ret && !amd_iommu_snp_en && cc_platform_has(CC_ATTR_HOST_SEV_SNP))
>
>
> I think we should clear when `amd_iommu_snp_en` is true.
That doesn't address the case where amd_iommu_prepare() fails, because amd_iommu_snp_en
will be %false (its init value) and the RMP will be uninitialized, i.e.
CC_ATTR_HOST_SEV_SNP will be incorrectly left set.
And conversely, IMO clearing CC_ATTR_HOST_SEV_SNP after initializing the IOMMU
and RMP is wrong as well. Such a host is probably hosed regardless, but from
the CPU's perspective, SNP is supported and enabled.
> May be below check is enough?
>
> if (ret && amd_iommu_snp_en)
>
>
> -Vasant
>
>
next prev parent reply other threads:[~2025-02-05 15:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 21:56 [PATCH v3 0/3] Fix broken SNP support with KVM module built-in Ashish Kalra
2025-02-03 21:56 ` [PATCH v3 1/3] crypto: ccp: Add external API interface for PSP module initialization Ashish Kalra
2025-02-07 21:45 ` Tom Lendacky
2025-02-08 4:52 ` Kalra, Ashish
2025-02-03 21:56 ` [PATCH v3 2/3] KVM: SVM: Ensure PSP module is initialized if KVM module is built-in Ashish Kalra
2025-02-07 21:46 ` Tom Lendacky
2025-02-03 21:56 ` [PATCH v3 3/3] x86/sev: Fix broken SNP support with KVM module built-in Ashish Kalra
2025-02-05 9:51 ` Vasant Hegde
2025-02-05 15:17 ` Sean Christopherson [this message]
2025-02-05 16:55 ` Vasant Hegde
2025-02-05 19:31 ` Sean Christopherson
2025-02-05 22:54 ` Kalra, Ashish
2025-02-07 15:52 ` Sean Christopherson
2025-02-07 21:45 ` Kalra, Ashish
2025-02-06 5:41 ` Vasant Hegde
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=Z6OA9OhxBgsTY2ni@google.com \
--to=seanjc@google.com \
--cc=Ashish.Kalra@amd.com \
--cc=Neeraj.Upadhyay@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.