From: "Kalra, Ashish" <ashish.kalra@amd.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Vasant Hegde <vasant.hegde@amd.com>,
Tom Lendacky <thomas.lendacky@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, 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, 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 1/4] iommu/amd: Check SNP support before enabling IOMMU
Date: Mon, 27 Jan 2025 14:43:16 -0600 [thread overview]
Message-ID: <e23a94f0-c35f-4d50-b348-4cd64b5ebb67@amd.com> (raw)
In-Reply-To: <Z5QyybbSk4NeroyZ@google.com>
Hello Sean,
On 1/24/2025 6:39 PM, Sean Christopherson wrote:
> On Fri, Jan 24, 2025, Ashish Kalra wrote:
>> With discussions with the AMD IOMMU team, here is the AMD IOMMU
>> initialization flow:
>
> ..
>
>> IOMMU SNP check
>> Core IOMMU subsystem init is done during iommu_subsys_init() via
>> subsys_initcall. This function does change the DMA mode depending on
>> kernel config. Hence, SNP check should be done after subsys_initcall.
>> That's why its done currently during IOMMU PCI init (IOMMU_PCI_INIT stage).
>> And for that reason snp_rmptable_init() is currently invoked via
>> device_initcall().
>>
>> The summary is that we cannot move snp_rmptable_init() to subsys_initcall as
>> core IOMMU subsystem gets initialized via subsys_initcall.
>
> Just explicitly invoke RMP initialization during IOMMU SNP setup. Pretending
> there's no connection when snp_rmptable_init() checks amd_iommu_snp_en and has
> a comment saying it needs to come after IOMMU SNP setup is ridiculous.
>
Thanks for the suggestion and the patch, i have tested it works for all cases
and scenarios. I will post the next version of the patch-set based on this
patch.
Ashish
> Compile tested only.
>
> ---
> From: Sean Christopherson <seanjc@google.com>
> Date: Fri, 24 Jan 2025 16:25:58 -0800
> Subject: [PATCH] x86/sev: iommu/amd: Explicitly init SNP's RMP table during
> IOMMU SNP setup
>
> Explicitly initialize the RMP table during IOMMU SNP setup, as there is a
> hard dependency on the IOMMU being configured first, and dancing around
> the dependency with initcall shenanigans and a comment is all kinds of
> stupid.
>
> The RMP is blatantly not a device; initializing it via a device_initcall()
> is confusing and "works" only because of dumb luck: due to kernel build
> order, when the the PSP driver is built-in, its effective device_initcall()
> just so happens to be invoked after snp_rmptable_init().
>
> That all falls apart if the order is changed in any way. E.g. if KVM
> is built-in and attempts to access the RMP during its device_initcall(),
> chaos ensues.
>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> arch/x86/include/asm/sev.h | 1 +
> arch/x86/virt/svm/sev.c | 25 ++++++++-----------------
> drivers/iommu/amd/init.c | 7 ++++++-
> 3 files changed, 15 insertions(+), 18 deletions(-)
>
> diff --git a/arch/x86/include/asm/sev.h b/arch/x86/include/asm/sev.h
> index 91f08af31078..30da0fc15923 100644
> --- a/arch/x86/include/asm/sev.h
> +++ b/arch/x86/include/asm/sev.h
> @@ -503,6 +503,7 @@ static inline void snp_kexec_begin(void) { }
>
> #ifdef CONFIG_KVM_AMD_SEV
> bool snp_probe_rmptable_info(void);
> +int __init snp_rmptable_init(void);
> int snp_lookup_rmpentry(u64 pfn, bool *assigned, int *level);
> void snp_dump_hva_rmpentry(unsigned long address);
> int psmash(u64 pfn);
> diff --git a/arch/x86/virt/svm/sev.c b/arch/x86/virt/svm/sev.c
> index 9a6a943d8e41..d932aa21340b 100644
> --- a/arch/x86/virt/svm/sev.c
> +++ b/arch/x86/virt/svm/sev.c
> @@ -189,19 +189,19 @@ void __init snp_fixup_e820_tables(void)
> * described in the SNP_INIT_EX firmware command description in the SNP
> * firmware ABI spec.
> */
> -static int __init snp_rmptable_init(void)
> +int __init snp_rmptable_init(void)
> {
> u64 max_rmp_pfn, calc_rmp_sz, rmptable_size, rmp_end, val;
> void *rmptable_start;
>
> - if (!cc_platform_has(CC_ATTR_HOST_SEV_SNP))
> - return 0;
> + if (WARN_ON_ONCE(!cc_platform_has(CC_ATTR_HOST_SEV_SNP)))
> + return -ENOSYS;
>
> - if (!amd_iommu_snp_en)
> - goto nosnp;
> + if (WARN_ON_ONCE(!amd_iommu_snp_en))
> + return -ENOSYS;
>
> if (!probed_rmp_size)
> - goto nosnp;
> + return -ENOSYS;
>
> rmp_end = probed_rmp_base + probed_rmp_size - 1;
>
> @@ -218,13 +218,13 @@ static int __init snp_rmptable_init(void)
> if (calc_rmp_sz > probed_rmp_size) {
> pr_err("Memory reserved for the RMP table does not cover full system RAM (expected 0x%llx got 0x%llx)\n",
> calc_rmp_sz, probed_rmp_size);
> - goto nosnp;
> + return -ENOSYS;
> }
>
> rmptable_start = memremap(probed_rmp_base, probed_rmp_size, MEMREMAP_WB);
> if (!rmptable_start) {
> pr_err("Failed to map RMP table\n");
> - goto nosnp;
> + return -ENOMEM;
> }
>
> /*
> @@ -261,17 +261,8 @@ static int __init snp_rmptable_init(void)
> crash_kexec_post_notifiers = true;
>
> return 0;
> -
> -nosnp:
> - cc_platform_clear(CC_ATTR_HOST_SEV_SNP);
> - return -ENOSYS;
> }
>
> -/*
> - * This must be called after the IOMMU has been initialized.
> - */
> -device_initcall(snp_rmptable_init);
> -
> static struct rmpentry *get_rmpentry(u64 pfn)
> {
> if (WARN_ON_ONCE(pfn > rmptable_max_pfn))
> diff --git a/drivers/iommu/amd/init.c b/drivers/iommu/amd/init.c
> index 0e0a531042ac..d00530156a72 100644
> --- a/drivers/iommu/amd/init.c
> +++ b/drivers/iommu/amd/init.c
> @@ -3171,7 +3171,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))
> @@ -3196,6 +3196,11 @@ static void iommu_snp_enable(void)
> goto disable_snp;
> }
>
> + 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;
>
>
> base-commit: ac80076177131f6e3291737c851a6fe32cc03fd3
next prev parent reply other threads:[~2025-01-27 20:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 0:59 [PATCH 0/4] Fix broken SNP support with KVM module built-in Ashish Kalra
2025-01-22 1:00 ` [PATCH 1/4] iommu/amd: Check SNP support before enabling IOMMU Ashish Kalra
2025-01-22 15:22 ` Tom Lendacky
2025-01-22 17:07 ` Vasant Hegde
2025-01-24 21:46 ` Kalra, Ashish
2025-01-25 0:39 ` Sean Christopherson
2025-01-27 20:43 ` Kalra, Ashish [this message]
2025-01-27 21:12 ` Sean Christopherson
2025-01-29 9:24 ` Vasant Hegde
2025-01-22 1:00 ` [PATCH 2/4] crypto: ccp: Add external API interface for PSP module initialization Ashish Kalra
2025-01-22 15:53 ` Tom Lendacky
2025-01-22 1:00 ` [PATCH 3/4] KVM: SVM: Ensure PSP module initialized before built-in KVM module Ashish Kalra
2025-01-22 15:58 ` Tom Lendacky
2025-01-22 1:00 ` [PATCH 4/4] x86/sev: Fix broken SNP support with KVM module built-in Ashish Kalra
2025-01-22 16:07 ` Tom Lendacky
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=e23a94f0-c35f-4d50-b348-4cd64b5ebb67@amd.com \
--to=ashish.kalra@amd.com \
--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=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=pbonzini@redhat.com \
--cc=robin.murphy@arm.com \
--cc=seanjc@google.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