From: "zhenglifeng (A)" <zhenglifeng1@huawei.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Beata Michalska <beata.michalska@arm.com>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-renesas-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: topology: Do not warn on missing AMU in cpuhp_topology_online()
Date: Thu, 15 Jan 2026 20:52:11 +0800 [thread overview]
Message-ID: <7f156aa7-c723-4580-aa82-b2f0fe6d3845@huawei.com> (raw)
In-Reply-To: <a8dbf49bfa44a6809fa4f34b918516847dc14460.1768466986.git.geert+renesas@glider.be>
On 2026/1/15 16:51, Geert Uytterhoeven wrote:
> When CONFIG_CPUMASK_OFFSTACK is not enabled, and resuming from s2ram on
> Renesas R-Car H3 (big.LITTLE 4x Cortex-A57 + 4x Cortex-A53), during
> enabling of the first little core, a warning message is printed:
>
> AMU: CPU[4] doesn't support AMU counters
>
> This confuses users, as during boot amu_fie_setup() does not print such
> a message, unless debugging is enabled (freq_counters_valid() prints
> "CPU%d: counters are not supported.\n" at debug level in that case).
>
> Hence drop the warning, freq_counters_valid() has already printed a
> debug message anyway.
>
> Fixes: 6fd9be0b7b2e957d ("arm64: topology: Handle AMU FIE setup on CPU hotplug")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> arch/arm64/kernel/topology.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm64/kernel/topology.c b/arch/arm64/kernel/topology.c
> index 539b3893518281ec..3fe1faab03620e78 100644
> --- a/arch/arm64/kernel/topology.c
> +++ b/arch/arm64/kernel/topology.c
> @@ -332,7 +332,6 @@ static int cpuhp_topology_online(unsigned int cpu)
> * may use different source of the freq scale.
> */
> if (!freq_counters_valid(cpu)) {
> - pr_warn("CPU[%u] doesn't support AMU counters\n", cpu);
> topology_clear_scale_freq_source(SCALE_FREQ_SOURCE_ARCH,
> policy->related_cpus);
> cpumask_andnot(amu_fie_cpus, amu_fie_cpus, policy->related_cpus);
Thanks!
Reviewed-by: Lifeng Zheng <zhenglifeng1@huawei.com>
next prev parent reply other threads:[~2026-01-15 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 8:51 Geert Uytterhoeven
2026-01-15 12:52 ` zhenglifeng (A) [this message]
2026-01-22 16:59 ` Will Deacon
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=7f156aa7-c723-4580-aa82-b2f0fe6d3845@huawei.com \
--to=zhenglifeng1@huawei.com \
--cc=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®