From: Jonas Jelonek <jelonek.jonas@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@kernel.org>,
Jiayuan Chen <jiayuan.chen@linux.dev>,
linux-rt-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: smp: report dying CPU to RCU in stop_this_cpu()
Date: Fri, 5 Jun 2026 13:12:38 +0200 [thread overview]
Message-ID: <153b976e-ce36-44fe-899a-01fc5877e573@gmail.com> (raw)
In-Reply-To: <20260605103418.tH3rlwmO@linutronix.de>
Hi,
On 05.06.26 12:34, Sebastian Andrzej Siewior wrote:
> Does
> echo 0 > /sys/devices/system/cpu/cpu1/online
>
> lead to the same problem?
Funny, my device doesn't have this 'online' file, neither for the
other CPUs. So it seems this CPU hotplug isn't supported/used here?
Or am I missing a Kconfig option for that?
I'm working on a Realtek RTL931x SoC here, it has MIPS interAptiv
cores. I can provide more information if needed.
> I missed that arm64 has also this but only if the online path fails kind
> of early, see
> 04e613ded8c26 ("arm64: smp: Tell RCU about CPUs that fail to come online")
>
> so this not the "normal" case but an exception. Mips seems to be doing
> something different here. I am not sure if this is the only thing that
> is missing.
>
>> Best,
>> Jonas
> Sebastian
Best,
Jonas
next prev parent reply other threads:[~2026-06-05 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 18:24 [PATCH] MIPS: smp: report dying CPU to RCU in stop_this_cpu() Jonas Jelonek
2026-06-05 3:01 ` Huacai Chen
2026-06-05 6:56 ` Jonas Jelonek
2026-06-05 6:42 ` Sebastian Andrzej Siewior
2026-06-05 7:12 ` Jonas Jelonek
2026-06-05 10:34 ` Sebastian Andrzej Siewior
2026-06-05 11:12 ` Jonas Jelonek [this message]
2026-06-08 8:25 ` Sebastian Andrzej Siewior
2026-06-05 14:00 ` Huacai Chen
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=153b976e-ce36-44fe-899a-01fc5877e573@gmail.com \
--to=jelonek.jonas@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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