From: Yury Norov <yury.norov@gmail.com>
To: Mitchell Levy <levymitchell0@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Dennis Zhou" <dennis@kernel.org>, "Tejun Heo" <tj@kernel.org>,
"Christoph Lameter" <cl@linux.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Benno Lossin" <lossin@kernel.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Tyler Hicks" <code@tyhicks.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 4/7] rust: cpumask: Add getters for globally defined cpumasks
Date: Wed, 3 Sep 2025 18:03:51 -0400 [thread overview]
Message-ID: <aLi7Ptya5xp22P-B@yury> (raw)
In-Reply-To: <20250828-rust-percpu-v3-4-4dd92e1e7904@gmail.com>
On Thu, Aug 28, 2025 at 12:00:11PM -0700, Mitchell Levy wrote:
> Add getters for the global cpumasks documented in
> `include/linux/cpumask.h`, specifically:
> - cpu_possible_mask
> - cpu_online_mask
> - cpu_enabled_mask
> - cpu_present_mask
> - cpu_active_mask
>
> Signed-off-by: Mitchell Levy <levymitchell0@gmail.com>
> ---
> rust/kernel/cpumask.rs | 46 ++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 46 insertions(+)
>
> diff --git a/rust/kernel/cpumask.rs b/rust/kernel/cpumask.rs
> index b7401848f59e..ca9aa6875b4a 100644
> --- a/rust/kernel/cpumask.rs
> +++ b/rust/kernel/cpumask.rs
> @@ -77,6 +77,52 @@ pub unsafe fn as_ref<'a>(ptr: *const bindings::cpumask) -> &'a Self {
> unsafe { &*ptr.cast() }
> }
>
> + /// Get a CPU mask representing possible CPUs; has bit `cpu` set iff cpu is populatable
> + #[inline]
> + pub fn possible() -> &'static Self {
> + // SAFETY: `__cpu_possible_mask` is a valid global provided by the kernel that lives
> + // forever.
> + unsafe { Cpumask::as_ref(&raw const bindings::__cpu_possible_mask) }
> + }
This function and the following look like returning a boolean.
Maybe possible_cpus()?
The general rule is to keep the rust naming as close to C as
possible, but in this case Cpumask::cpu_possible_mask is, OK,
somewhat excessive.
Thanks,
Yury
> +
> + /// Get a CPU mask representing online CPUs; has bit `cpu` set iff cpu available to the
> + /// scheduler
> + #[inline]
> + pub fn online() -> &'static Self {
> + // SAFETY: `__cpu_online_mask` is a valid global provided by the kernel that lives forever.
> + // Since we wrap the returned pointer in an `Opaque`, it's ok that `__cpu_online_mask`
> + // may change its value.
> + unsafe { Cpumask::as_ref(&raw const bindings::__cpu_online_mask) }
> + }
> +
> + /// Get a CPU mask representing enabled CPUs; has bit `cpu` set iff cpu can be brought online
> + #[inline]
> + pub fn enabled() -> &'static Self {
> + // SAFETY: `__cpu_enabled_mask` is a valid global provided by the kernel that lives forever.
> + // Since we wrap the returned pointer in an `Opaque`, it's ok that `__cpu_enabled_mask`
> + // may change its value.
> + unsafe { Cpumask::as_ref(&raw const bindings::__cpu_enabled_mask) }
> + }
> +
> + /// Get a CPU mask representing present CPUs; has bit `cpu` set iff cpu is populated
> + #[inline]
> + pub fn present() -> &'static Self {
> + // SAFETY: `__cpu_present_mask` is a valid global provided by the kernel that lives
> + // forever. Since we wrap the returned pointer in an `Opaque`, it's ok that
> + // `__cpu_present_mask` may change its value.
> + unsafe { Cpumask::as_ref(&raw const bindings::__cpu_present_mask) }
> + }
> +
> + /// Get a CPU mask representing active CPUs; has bit `cpu` set iff cpu is available to
> + /// migration.
> + #[inline]
> + pub fn active() -> &'static Self {
> + // SAFETY: `__cpu_active_mask` is a valid global provided by the kernel that lives forever.
> + // Since we wrap the returned pointer in an `Opaque`, it's ok that `__cpu_active_mask`
> + // may change its value.
> + unsafe { Cpumask::as_ref(&raw const bindings::__cpu_active_mask) }
> + }
> +
> /// Obtain the raw `struct cpumask` pointer.
> pub fn as_raw(&self) -> *mut bindings::cpumask {
> let this: *const Self = self;
>
> --
> 2.34.1
next prev parent reply other threads:[~2025-09-03 22:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 19:00 [PATCH v3 0/7] rust: Add Per-CPU Variable API Mitchell Levy
2025-08-28 19:00 ` [PATCH v3 1/7] rust: percpu: introduce a rust API for per-CPU variables Mitchell Levy
2025-09-03 21:42 ` Yury Norov
2025-09-04 19:53 ` Mitchell Levy
2025-09-04 20:27 ` Yury Norov
2025-09-04 21:17 ` Mitchell Levy
2025-08-28 19:00 ` [PATCH v3 2/7] rust: percpu: add a rust per-CPU variable sample Mitchell Levy
2025-08-28 19:00 ` [PATCH v3 3/7] rust: cpumask: Add a `Cpumask` iterator Mitchell Levy
2025-08-29 5:19 ` Viresh Kumar
2025-08-28 19:00 ` [PATCH v3 4/7] rust: cpumask: Add getters for globally defined cpumasks Mitchell Levy
2025-08-29 5:20 ` Viresh Kumar
2025-09-03 22:03 ` Yury Norov [this message]
2025-09-04 19:55 ` Mitchell Levy
2025-08-28 19:00 ` [PATCH v3 5/7] rust: percpu: Support non-zeroable types for DynamicPerCpu Mitchell Levy
2025-09-03 22:19 ` Yury Norov
2025-09-04 20:26 ` Mitchell Levy
2025-09-04 20:37 ` Yury Norov
2025-09-04 21:05 ` Mitchell Levy
2025-09-04 21:46 ` Yury Norov
2025-09-04 21:57 ` Miguel Ojeda
2025-09-03 23:05 ` Miguel Ojeda
2025-09-04 20:17 ` Mitchell Levy
2025-09-04 20:37 ` Miguel Ojeda
2025-09-04 21:50 ` Mitchell Levy
2025-08-28 19:00 ` [PATCH v3 6/7] rust: percpu: Add pin-hole optimizations for numerics Mitchell Levy
2025-08-28 19:00 ` [PATCH v3 7/7] rust: percpu: cache per-CPU pointers in the dynamic case Mitchell Levy
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=aLi7Ptya5xp22P-B@yury \
--to=yury.norov@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=cl@linux.com \
--cc=code@tyhicks.com \
--cc=dakr@kernel.org \
--cc=dennis@kernel.org \
--cc=gary@garyguo.net \
--cc=levymitchell0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tj@kernel.org \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@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;
as well as URLs for NNTP newsgroup(s).