[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250613033447.3531709-1-richard120310@gmail.com>
Date: Fri, 13 Jun 2025 11:34:45 +0800
From: I Hsin Cheng <richard120310@...il.com>
To: yury.norov@...il.com
Cc: linux@...musvillemoes.dk,
jstultz@...gle.com,
tglx@...utronix.de,
sboyd@...nel.org,
linux-kernel@...r.kernel.org,
eleanor15x@...il.com,
visitorckw@...il.com,
jserv@...s.ncku.edu.tw,
skhan@...uxfoundation.org,
linux-kernel-mentees@...ts.linux.dev,
I Hsin Cheng <richard120310@...il.com>
Subject: [RFC PATCH 0/2] Introduce cpumask_first_but() and use cases
This series introduce cpumask_first_but() and make cpumask_any_but()
a wrapper around it, just like other cpumask_any*() helpers, they're
some wrappers around cpumask_first*(), except some special cases.
The patches are scheduled as the following:
1. The implementation of cpumask_first_but() and some
positive results of making cpumask_any_but() a wrapper around
it are attached there, including performance and code size.
2. Use cpumask_first_but() in clocksource
I Hsin Cheng (2):
cpumask: Introduce cpumask_first_but()
clocksource: Use cpumask_first_but() in
clocksource_verify_choose_cpus()
include/linux/cpumask.h | 22 ++++++++++++++++------
kernel/time/clocksource.c | 4 +---
2 files changed, 17 insertions(+), 9 deletions(-)
--
2.43.0
Powered by blists - more mailing lists