From: Sumit Gupta <sumitg@nvidia.com>
To: <catalin.marinas@arm.com>, <will@kernel.org>,
<zhanjie9@hisilicon.com>, <zhenglifeng1@huawei.com>,
<viresh.kumar@linaro.org>, <rafael@kernel.org>,
<beata.michalska@arm.com>, <pierre.gondois@arm.com>,
<ionela.voinescu@arm.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>
Cc: <treding@nvidia.com>, <jonathanh@nvidia.com>, <bbasu@nvidia.com>,
<sumitg@nvidia.com>
Subject: [PATCH v2] arm64: topology: Fix false warning in counters_read_on_cpu() for same-CPU reads
Date: Tue, 24 Feb 2026 14:57:14 +0530 [thread overview]
Message-ID: <20260224092714.1242141-1-sumitg@nvidia.com> (raw)
The counters_read_on_cpu() function warns when called with IRQs
disabled to prevent deadlock in smp_call_function_single(). However,
this warning is spurious when reading counters on the current CPU,
since no IPI is needed for same CPU reads.
Commit 12eb8f4fff24 ("cpufreq: CPPC: Update FIE arch_freq_scale in
ticks for non-PCC regs") changed the CPPC Frequency Invariance Engine
to read AMU counters directly from the scheduler tick for non-PCC
register spaces (like FFH), instead of deferring to a kthread. This
means counters_read_on_cpu() is now called with IRQs disabled from
the tick handler, triggering the warning:
| WARNING: arch/arm64/kernel/topology.c:410 at counters_read_on_cpu
| ...
| Call trace:
| counters_read_on_cpu+0x88/0xa8 (P)
| cpc_read_ffh+0xdc/0x148
| cpc_read+0x260/0x518
| cppc_get_perf_ctrs+0xf0/0x398
| __cppc_scale_freq_tick+0x4c/0x148 [cppc_cpufreq]
| cppc_scale_freq_tick+0x44/0x88 [cppc_cpufreq]
| topology_scale_freq_tick+0x34/0x58
| sched_tick+0x58/0x300
| update_process_times+0xcc/0x120
| tick_nohz_handler+0xa8/0x260
| __hrtimer_run_queues+0x154/0x360
| hrtimer_interrupt+0xf4/0x2b0
| arch_timer_handler_phys+0x4c/0x78
| ....
| CPPC Cpufreq:__cppc_scale_freq_tick: failed to read perf counters
| ....
Fix this by calling the counter read function directly for same CPU
case, bypassing smp_call_function_single(). Use get_cpu() to disable
preemption, as the counter read functions call this_cpu_has_cap()
which requires a non-preemptible context.
Fixes: 997c021abc6e ("cpufreq: CPPC: Update FIE arch_freq_scale in ticks for non-PCC regs")
Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
Reviewed-by: Jie Zhan <zhanjie9@hisilicon.com>
---
v1 -> v2:
- Rebased on v7.0-rc1
- Updated Fixes tag to match upstream commit SHA
---
arch/arm64/kernel/topology.c | 21 +++++++++++++++++++--
1 file changed, 19 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/kernel/topology.c b/arch/arm64/kernel/topology.c
index 3fe1faab0362..c3e883e99aa0 100644
--- a/arch/arm64/kernel/topology.c
+++ b/arch/arm64/kernel/topology.c
@@ -400,12 +400,29 @@ static inline
int counters_read_on_cpu(int cpu, smp_call_func_t func, u64 *val)
{
/*
- * Abort call on counterless CPU or when interrupts are
- * disabled - can lead to deadlock in smp sync call.
+ * Abort call on counterless CPU.
*/
if (!cpu_has_amu_feat(cpu))
return -EOPNOTSUPP;
+ /*
+ * For same-CPU reads, call the function directly since no IPI
+ * is needed and this is safe even with IRQs disabled.
+ * Use get_cpu() to disable preemption as the counter read
+ * functions call this_cpu_has_cap() which requires a
+ * non-preemptible context.
+ */
+ if (cpu == get_cpu()) {
+ func(val);
+ put_cpu();
+ return 0;
+ }
+ put_cpu();
+
+ /*
+ * Reading from a remote CPU requires IRQs enabled to avoid
+ * deadlock in smp_call_function_single().
+ */
if (WARN_ON_ONCE(irqs_disabled()))
return -EPERM;
--
2.34.1
next reply other threads:[~2026-02-24 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 9:27 Sumit Gupta [this message]
2026-02-24 17:55 ` [PATCH v2] arm64: topology: Fix false warning in counters_read_on_cpu() for same-CPU reads Marc Zyngier
2026-02-25 11:38 ` Sumit Gupta
2026-02-25 22:16 ` Will Deacon
2026-02-26 11:17 ` Sumit Gupta
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=20260224092714.1242141-1-sumitg@nvidia.com \
--to=sumitg@nvidia.com \
--cc=bbasu@nvidia.com \
--cc=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pierre.gondois@arm.com \
--cc=rafael@kernel.org \
--cc=treding@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.org \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.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 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.