From: Martin Schiller <ms@dev.tdt.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Florian Eckert <fe@dev.tdt.de>
Subject: Re: [PATCH] x86/reboot: Add call to do_kernel_restart()
Date: Wed, 25 Feb 2026 07:27:51 +0100 [thread overview]
Message-ID: <47d501dae62ff2b85ae225d597b33253@dev.tdt.de> (raw)
In-Reply-To: <20260225053254.GBaZ6Jhh-X8Mp5l9eS@renoirsky.local>
On 2026-02-25 06:32, Borislav Petkov wrote:
> On Fri, Feb 20, 2026 at 01:29:01PM +0100, Martin Schiller wrote:
>> SoC devices like the Intel / MaxLinear Lightning Mountain must be
>> reset
>> by the RCU instead of using "normal" x86 mechanisms like ACPI, BIOS,
>
> Read-Copy-Update?
Sorry, I forgot to explain the abbreviation.
RCU is short for Reset Control Unit. That's what it's called in the
Intel / MaxLinear world.
>
> I'm relatively sure you don't mean that.
>
>> KBD, etc.
>>
>> Therefore, the RCU driver (reset-intel-gw) registers a restart handler
>> which triggers the global reset signal.
>>
>> Unfortunately, this is of no use as long as the restart chain is not
>> processed during reboot on x86 systems.
>>
>> So we must call do_kernel_restart() when a reboot is performed. This
>> has
>
> Who's "we"?
I don't mean anyone in particular. I just wanted to express that the
function must be called.
>
>> long been common practice for other architectures.
>>
>> Signed-off-by: Martin Schiller <ms@dev.tdt.de>
>> ---
>> arch/x86/kernel/reboot.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c
>> index
>> 6032fa9ec753ce938b1b523a7eab76370ee802de..ddff25a1efbe71171ca22ec21f50541517c1a464
>> 100644
>> --- a/arch/x86/kernel/reboot.c
>> +++ b/arch/x86/kernel/reboot.c
>> @@ -773,12 +773,15 @@ static void __machine_emergency_restart(int
>> emergency)
>> machine_ops.emergency_restart();
>> }
>>
>> -static void native_machine_restart(char *__unused)
>> +static void native_machine_restart(char *command)
>> {
>> pr_notice("machine restart\n");
>>
>> if (!reboot_force)
>> machine_shutdown();
>> +
>> + do_kernel_restart(command);
>
> I guess we can do that - the other arches do it already...
next prev parent reply other threads:[~2026-02-25 6:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 12:29 [PATCH] x86/reboot: Add call to do_kernel_restart() Martin Schiller
2026-02-25 5:32 ` Borislav Petkov
2026-02-25 6:27 ` Martin Schiller [this message]
2026-02-25 7:25 ` Borislav Petkov
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=47d501dae62ff2b85ae225d597b33253@dev.tdt.de \
--to=ms@dev.tdt.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fe@dev.tdt.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.