From: Alexander Sverdlin <alexander.sverdlin@nokia.com>
To: Mark Rutland <mark.rutland@arm.com>, Ard Biesheuvel <ardb@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Peter Collingbourne <pcc@google.com>,
Guenter Roeck <linux@roeck-us.net>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Matija Glavinic-Pecotic <matija.glavinic-pecotic.ext@nokia.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Krzysztof Adamski <krzysztof.adamski@nokia.com>,
linux-efi@vger.kernel.org
Subject: Re: [PATCH v2] arm64: move efi_reboot to restart handler
Date: Tue, 15 Feb 2022 09:44:27 +0100 [thread overview]
Message-ID: <79bcce92-abb2-4c3e-7193-d18e144da8a0@nokia.com> (raw)
In-Reply-To: <Yfk8hQB1eon7oeYU@FVFF77S0Q05N>
Hello Mark, Ard,
On 01/02/2022 14:58, Mark Rutland wrote:
>> You could argue that restart handlers were not created for that but they
>> suit this purpose ideally and it wouldn't make much sense (in my
>> opinion) to add yet another notifier chain that would run before reset
>> notifiers, for code that is not supposed to reset the whole system and
>> this is exacly what I would have to do if efi_reboot() is forced to be
>> called before all handlers.
>
> As above, I think that's just using the wrong interface, and the reboot
> notifier mechanism *already* exists, so I'm really confused here.
>
> Have I misunderstood what you're trying to achieve?
>
> Is there some problem with the reboot notifier mechanism that I am unaware of?
> e.g. do we bypass them in some case where you think they're needed?
>
> Are you simply unaware of reboot notifiers?
Could you please check the simple case of pwrseq_emmc.c?
While that's currently the only example of this kind upstream I can imagine
further use-cases, especially in storage area like above.
Would you suggest it's illegal usage of register_restart_handler()?
Do we need to fix pwrseq_emmc.c by introducing new atomic notifier chain
which will be called before restart handlers, so that it works on
emergency_restart()?
--
Best regards,
Alexander Sverdlin.
next prev parent reply other threads:[~2022-02-15 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YfP0osb45uJldtM9@localhost.localdomain>
[not found] ` <YfQTZTUNaeGi+8tG@FVFF77S0Q05N>
[not found] ` <YfRorCpk0seVGI+5@localhost.localdomain>
[not found] ` <Yfk8hQB1eon7oeYU@FVFF77S0Q05N>
[not found] ` <Yfp7wZXLKPIYBxmp@localhost.localdomain>
[not found] ` <CAMj1kXEP+0ErwmLebw5mswz+jD+Yd_U_U7jmhPR2bKgnMRTWNw@mail.gmail.com>
2022-02-15 8:44 ` [PATCH v2] arm64: move efi_reboot to restart handler Alexander Sverdlin
2022-02-15 8:44 ` Alexander Sverdlin [this message]
2022-02-15 14:30 ` Guenter Roeck
2022-02-15 15:01 ` Krzysztof Adamski
2022-02-15 16:57 ` Guenter Roeck
2022-02-15 17:03 ` Ard Biesheuvel
2022-02-16 9:11 ` Krzysztof Adamski
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=79bcce92-abb2-4c3e-7193-d18e144da8a0@nokia.com \
--to=alexander.sverdlin@nokia.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=krzysztof.adamski@nokia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=matija.glavinic-pecotic.ext@nokia.com \
--cc=pcc@google.com \
--cc=will@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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