From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Prasanna Kumar T S M <ptsm@linux.microsoft.com>,
Beata Michalska <beata.michalska@arm.com>,
Sumit Gupta <sumitg@nvidia.com>, Oleg Keri <okerixx@gmail.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Ananthu C V <ananthu.cv@oss.qualcomm.com>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v6] arm64: topology: fix arch_freq_get_on_cpu() overflow above 4.19 GHz
Date: Thu, 24 Sep 2026 11:31:05 +0100 [thread overview]
Message-ID: <179024159739.2601842.17914856161102135517.b4-ty@kernel.org> (raw)
In-Reply-To: <20260923125604.2482-1-okerixx@gmail.com>
On Wed, 23 Sep 2026 14:56:04 +0200, Oleg Keri wrote:
> arch_freq_get_on_cpu() computes the product of the frequency scale and
> the reference frequency as a u64, but assigns it to an unsigned int
> before shifting it back down:
>
> freq = scale * arch_scale_freq_ref(cpu);
> freq >>= SCHED_CAPACITY_SHIFT;
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: topology: fix arch_freq_get_on_cpu() overflow above 4.19 GHz
https://git.kernel.org/arm64/c/3872cc6b9294
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-09-24 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 12:56 [PATCH v6] arm64: topology: fix arch_freq_get_on_cpu() overflow above 4.19 GHz Oleg Keri
2026-09-23 14:47 ` Catalin Marinas
2026-09-24 8:29 ` Oleg Keri
2026-09-24 10:31 ` Will Deacon [this message]
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=179024159739.2601842.17914856161102135517.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=ananthu.cv@oss.qualcomm.com \
--cc=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=okerixx@gmail.com \
--cc=peterz@infradead.org \
--cc=ptsm@linux.microsoft.com \
--cc=sumitg@nvidia.com \
--cc=vincent.guittot@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