From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>
Cc: Marc Zyngier <maz@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
will Deacon <will@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Ard Biesheuvel <ardb@kernel.org>,
broonie@kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Subject: Re: Should arm64 have a custom crash shutdown handler?
Date: Thu, 5 May 2022 11:07:47 -0300 [thread overview]
Message-ID: <53d516d2-a991-05c2-981d-640b05fc5e29@igalia.com> (raw)
In-Reply-To: <878rrg13zb.fsf@redhat.com>
On 05/05/2022 10:52, Vitaly Kuznetsov wrote:
> [...]
> For Hyper-V, the situation is similar: hv_crash_handler() intitiates
> VMbus unload on the crashing CPU only, there's no mechanism to do
> 'global' unload so other CPUs will likely not be able to connect Vmbus
> devices in kdump kernel but this should not be necessary.
>
> There's a crash_kexec_post_notifiers mechanism which can be used instead
> but it's disabled by default so using machine_ops.crash_shutdown is
> better.
>
Thanks a bunch Vitaly, for the clarification!
Just as a heads-up: there's been a panic notifiers refactor proposed [0]
in which some notifiers will run before kdump by default, not requiring
"crash_kexec_post_notifiers" (which BTW is *unfortunately* hardcoded as
'Y' for hyper-v, since a11589563e96).
Cheers,
Guilherme
[0]
https://lore.kernel.org/lkml/20220427224924.592546-1-gpiccoli@igalia.com/
next prev parent reply other threads:[~2022-05-05 14:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 20:00 Should arm64 have a custom crash shutdown handler? Guilherme G. Piccoli
2022-05-05 7:29 ` Marc Zyngier
2022-05-05 12:44 ` Guilherme G. Piccoli
2022-05-05 12:53 ` Mark Rutland
2022-05-05 13:05 ` Guilherme G. Piccoli
2022-05-05 13:15 ` Mark Rutland
2022-05-05 13:19 ` Guilherme G. Piccoli
2022-05-05 13:52 ` Vitaly Kuznetsov
2022-05-05 14:07 ` Guilherme G. Piccoli [this message]
2022-05-05 14:31 ` Mark Rutland
2022-05-05 14:51 ` Vitaly Kuznetsov
2022-05-06 11:01 ` Mark Rutland
2022-05-30 1:51 ` Michael Kelley (LINUX)
2022-05-05 11:10 ` Mark Rutland
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=53d516d2-a991-05c2-981d-640b05fc5e29@igalia.com \
--to=gpiccoli@igalia.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mikelley@microsoft.com \
--cc=vkuznets@redhat.com \
--cc=will@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