[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240829144003.GFZtCIQzK6SCrZsgyE@fat_crate.local>
Date: Thu, 29 Aug 2024 16:40:03 +0200
From: Borislav Petkov <bp@...en8.de>
To: "Kalra, Ashish" <ashish.kalra@....com>
Cc: seanjc@...gle.com, pbonzini@...hat.com, dave.hansen@...ux.intel.com,
tglx@...utronix.de, mingo@...hat.com, x86@...nel.org, hpa@...or.com,
peterz@...radead.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, thomas.lendacky@....com, michael.roth@....com,
kexec@...ts.infradead.org, linux-coco@...ts.linux.dev
Subject: Re: [PATCH] x86/sev: Fix host kdump support for SNP
On Thu, Aug 29, 2024 at 09:30:54AM -0500, Kalra, Ashish wrote:
> Hello Boris,
>
> On 8/29/2024 3:34 AM, Borislav Petkov wrote:
> > On August 27, 2024 10:38:04 PM GMT+02:00, Ashish Kalra <Ashish.Kalra@....com> wrote:
> >> From: Ashish Kalra <ashish.kalra@....com>
> >>
> >> With active SNP VMs, SNP_SHUTDOWN_EX invoked during panic notifiers causes
> >> crashkernel boot failure with the following signature:
> > Why would SNP_SHUTDOWN be allowed *at all* if there are active SNP guests and there's potential to lose guest data in the process?!
>
> If SNP_SHUTDOWN is not done,
Read my question again pls.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists