From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Ashish Kalra <Ashish.Kalra@amd.com>,
pbonzini@redhat.com, dave.hansen@linux.intel.com,
tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
hpa@zytor.com, peterz@infradead.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
thomas.lendacky@amd.com, michael.roth@amd.com,
kexec@lists.infradead.org, linux-coco@lists.linux.dev
Subject: Re: [PATCH] x86/sev: Fix host kdump support for SNP
Date: Thu, 29 Aug 2024 07:50:16 -0700 [thread overview]
Message-ID: <ZtCKqD_gc6wnqu-P@google.com> (raw)
In-Reply-To: <87475131-856C-44DC-A27A-84648294F094@alien8.de>
On Thu, Aug 29, 2024, Borislav Petkov wrote:
> On August 27, 2024 10:38:04 PM GMT+02:00, Ashish Kalra <Ashish.Kalra@amd.com> wrote:
> >From: Ashish Kalra <ashish.kalra@amd.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?!
Because if the host is panicking, guests are hosed regardless. Unless I'm
misreading things, the goal here is to ensure the crashkernel can actually capture
a kdump.
next prev parent reply other threads:[~2024-08-29 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 20:38 [PATCH] x86/sev: Fix host kdump support for SNP Ashish Kalra
2024-08-29 8:34 ` Borislav Petkov
2024-08-29 14:30 ` Kalra, Ashish
2024-08-29 14:40 ` Borislav Petkov
2024-08-29 14:50 ` Sean Christopherson [this message]
2024-08-29 15:04 ` Borislav Petkov
2024-08-29 15:16 ` Kalra, Ashish
2024-08-30 21:08 ` Kalra, Ashish
2024-09-03 16:54 ` Borislav Petkov
2024-08-29 15:50 ` kernel test robot
2024-08-31 7:35 ` kernel test robot
2024-09-02 15:05 ` Paolo Bonzini
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=ZtCKqD_gc6wnqu-P@google.com \
--to=seanjc@google.com \
--cc=Ashish.Kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--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