From: Sudeep Holla <sudeep.holla@arm.com>
To: Jacky Bai <ping.bai@nxp.com>
Cc: <rafael@kernel.org>, <daniel.lezcano@linaro.org>,
<lpieralisi@kernel.org>, <ulf.hansson@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>, <james.morse@arm.com>,
<d-gole@ti.com>, <anup@brainfault.org>,
<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <linux-pm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<imx@lists.linux.dev>, <khilman@baylibre.com>,
<quic_tingweiz@quicinc.com>, <quic_yuanjiey@quicinc.com>
Subject: Re: [PATCH v4] cpuidle: Init cpuidle only for present CPUs
Date: Fri, 7 Mar 2025 09:50:26 +0000 [thread overview]
Message-ID: <Z8rBYuDiIyo8y6HT@bogus> (raw)
In-Reply-To: <20250307080303.2660506-1-ping.bai@nxp.com>
On Fri, Mar 07, 2025 at 04:03:03PM +0800, Jacky Bai wrote:
> for_each_possible_cpu() is currently used to initialize cpuidle
> in below cpuidle drivers:
> drivers/cpuidle/cpuidle-arm.c
> drivers/cpuidle/cpuidle-big_little.c
> drivers/cpuidle/cpuidle-psci.c
> drivers/cpuidle/cpuidle-riscv-sbi.c
>
> However, in cpu_dev_register_generic(), for_each_present_cpu()
> is used to register CPU devices which means the CPU devices are
> only registered for present CPUs and not all possible CPUs.
>
> With nosmp or maxcpus=0, only the boot CPU is present, lead
> to the failure:
>
> | Failed to register cpuidle device for cpu1
>
> Then rollback to cancel all CPUs' cpuidle registration.
>
> Change for_each_possible_cpu() to for_each_present_cpu() in the
> above cpuidle drivers to ensure it only registers cpuidle devices
> for CPUs that are actually present.
>
> Fixes: b0c69e1214bc ("drivers: base: Use present CPUs in GENERIC_CPU_DEVICES")
> Reviewed-by: Dhruva Gole <d-gole@ti.com>
> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
> Tested-by: Yuanjie Yang <quic_yuanjiey@quicinc.com>
> Signed-off-by: Jacky Bai <ping.bai@nxp.com>
> ---
> - v4 changes:
> - add changes for other cpuidle driver that has the similar issue
> as cpuidle-pcsi driver.
>
> - v3 changes:
> - improve the changelog as suggested by Sudeep
> ---
> drivers/cpuidle/cpuidle-arm.c | 8 ++++----
> drivers/cpuidle/cpuidle-big_little.c | 2 +-
> drivers/cpuidle/cpuidle-psci.c | 4 ++--
> drivers/cpuidle/cpuidle-riscv-sbi.c | 4 ++--
Why have you spared drivers/cpuidle/cpuidle-qcom-spm.c ? IIUC the issue
exists there as well.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-03-07 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 8:03 [PATCH v4] cpuidle: Init cpuidle only for present CPUs Jacky Bai
2025-03-07 9:50 ` Sudeep Holla [this message]
2025-03-07 10:02 ` Jacky Bai
2025-03-07 10:04 ` Sudeep Holla
2025-03-07 10:10 ` Jacky Bai
2025-03-07 10:19 ` Sudeep Holla
2025-03-07 10:26 ` Jacky Bai
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=Z8rBYuDiIyo8y6HT@bogus \
--to=sudeep.holla@arm.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=d-gole@ti.com \
--cc=daniel.lezcano@linaro.org \
--cc=imx@lists.linux.dev \
--cc=james.morse@arm.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ping.bai@nxp.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_yuanjiey@quicinc.com \
--cc=rafael@kernel.org \
--cc=ulf.hansson@linaro.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