From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, sudeep.holla@arm.com,
will@kernel.org, sfr@canb.auug.org.au,
Beata Michalska <beata.michalska@arm.com>
Cc: ionela.voinescu@arm.com, yury.norov@gmail.com,
linux-next@vger.kernel.org, sumitg@nvidia.com,
yang@os.amperecomputing.com, vanshikonda@os.amperecomputing.com,
lihuisong@huawei.com, zhanjie9@hisilicon.com,
ptsm@linux.microsoft.com
Subject: Re: [PATCH v2] arm64: Utilize for_each_cpu_wrap for reference lookup
Date: Fri, 21 Feb 2025 09:40:24 +0000 [thread overview]
Message-ID: <174013080894.2262863.4824734189364820879.b4-ty@arm.com> (raw)
In-Reply-To: <20250220091015.2319901-1-beata.michalska@arm.com>
On Thu, 20 Feb 2025 09:10:15 +0000, Beata Michalska wrote:
> While searching for a reference CPU within a given policy,
> arch_freq_get_on_cpu relies on cpumask_next_wrap to iterate over
> all available CPUs and to ensure each is verified only once.
> Recent changes to cpumask_next_wrap will handle the latter no more,
> so switching to for_each_cpu_wrap, which preserves expected behavior
> while ensuring compatibility with the updates.
> Not to mention that when iterating over each CPU, using a dedicated
> iterator is preferable to an open-coded loop.
>
> [...]
Applied to arm64 (for-next/amuv1-avg-freq), thanks!
[1/1] arm64: Utilize for_each_cpu_wrap for reference lookup
https://git.kernel.org/arm64/c/20711efa91e8
--
Catalin
next prev parent reply other threads:[~2025-02-21 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 9:10 Beata Michalska
2025-02-21 9:40 ` Catalin Marinas [this message]
2025-02-21 19:03 ` Yury Norov
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=174013080894.2262863.4824734189364820879.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=beata.michalska@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=lihuisong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ptsm@linux.microsoft.com \
--cc=sfr@canb.auug.org.au \
--cc=sudeep.holla@arm.com \
--cc=sumitg@nvidia.com \
--cc=vanshikonda@os.amperecomputing.com \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.com \
--cc=yury.norov@gmail.com \
--cc=zhanjie9@hisilicon.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 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®