[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f9252d0-17f2-4466-bffa-9da02d48f989@amd.com>
Date: Fri, 25 Jul 2025 16:00:16 +0530
From: Sairaj Kodilkar <sarunkod@....com>
To: Ashish Kalra <Ashish.Kalra@....com>, <joro@...tes.org>,
<suravee.suthikulpanit@....com>, <thomas.lendacky@....com>,
<Sairaj.ArunKodilkar@....com>, <Vasant.Hegde@....com>,
<herbert@...dor.apana.org.au>
CC: <seanjc@...gle.com>, <pbonzini@...hat.com>, <will@...nel.org>,
<robin.murphy@....com>, <john.allen@....com>, <davem@...emloft.net>,
<michael.roth@....com>, <iommu@...ts.linux.dev>,
<linux-kernel@...r.kernel.org>, <linux-crypto@...r.kernel.org>,
<kvm@...r.kernel.org>
Subject: Re: [PATCH v4 3/4] crypto: ccp: Skip SEV and SNP INIT for kdump boot
On 7/22/2025 3:23 AM, Ashish Kalra wrote:
> From: Ashish Kalra <ashish.kalra@....com>
>
> If SNP is enabled and initialized in the previous kernel then SNP is
> already initialized for kdump boot and attempting SNP INIT again
> during kdump boot causes SNP INIT failure and eventually leads to
> IOMMU failures.
>
> For SEV avoid SEV INIT failure warnings during kdump boot if SEV
> is enabled and initialized in the previous kernel.
>
> Skip SNP and SEV INIT if doing kdump boot.
>
> Signed-off-by: Ashish Kalra <ashish.kalra@....com>
Tested-by: Sairaj Kodilkar <sarunkod@....com>
Powered by blists - more mailing lists