From: Mitchell Levy <levymitchell0@gmail.com>
To: Yury Norov <yury.norov@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>,
"Allen Pais" <apais@linux.microsoft.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v4 2/9] rust: cpumask: Add getters for globally defined cpumasks
Date: Fri, 7 Nov 2025 16:27:23 -0800 [thread overview]
Message-ID: <690e8e6d.050a0220.b06fd.d2ec@mx.google.com> (raw)
In-Reply-To: <aQ1DAn7Djc19CgGF@yury>
On Thu, Nov 06, 2025 at 07:53:22PM -0500, Yury Norov wrote:
> On Wed, Nov 05, 2025 at 03:01:14PM -0800, 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
> >
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> > Suggested-by: Yury Norov <yury.norov@gmail.com>
> > 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..a6a130092fcb 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_cpus() -> &'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) }
> > + }
>
> Not sure about this '&raw const' syntax, but I want to make sure that
> all this getters provide non-modifiable references. To modify any of
> those masks, one has to call a dedicated helper like set_cpu_possible().
For `id: T`, the syntax `&raw const id` produces a `*const T` pointing
at `id` (the analogous syntax `&raw mut id` produces a `*mut T`).
All getters here provide const references (`&'static Self` as opposed to
`&'static mut Self`) which will cause the compiler to prevent usage of
any `Cpumask` methods with a `&mut self` reciever (i.e., methods that
change the `Cpumask`).
> Can you maybe explicitly mention it in the comments?
The compiler will prevent using these values to change the underlying
`__cpu_possible_mask` etc, so mentioning that these return values can't
be used for that purpose seems redundant to me.
It is possible someone could get the pointer out via `Cpumask::as_raw`,
and then do something bad with that pointer, but this isn't any
different than someone doing something bad with
`bindings::__cpu_possible_mask`.
Thanks,
Mitchell
> With that,
>
> Acked-by: Yury Norov (NVIDIA) <yury.norov@gmail.com>
>
> > + /// Get a CPU mask representing online CPUs; has bit `cpu` set iff cpu available to the
> > + /// scheduler
> > + #[inline]
> > + pub fn online_cpus() -> &'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_cpus() -> &'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_cpus() -> &'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_cpus() -> &'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-11-08 0:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 23:01 [PATCH v4 0/9] rust: Add Per-CPU Variable API Mitchell Levy
2025-11-05 23:01 ` [PATCH v4 1/9] rust: cpumask: Add a `Cpumask` iterator Mitchell Levy
2025-11-07 0:25 ` Yury Norov
2025-11-08 0:06 ` Mitchell Levy
2025-11-08 3:39 ` Yury Norov
2025-11-05 23:01 ` [PATCH v4 2/9] rust: cpumask: Add getters for globally defined cpumasks Mitchell Levy
2025-11-07 0:53 ` Yury Norov
2025-11-08 0:27 ` Mitchell Levy [this message]
2025-11-05 23:01 ` [PATCH v4 3/9] rust: percpu: Add C bindings for per-CPU variable API Mitchell Levy
2025-11-07 0:57 ` Yury Norov
2025-11-05 23:01 ` [PATCH v4 4/9] rust: percpu: introduce a rust API for static per-CPU variables Mitchell Levy
2025-11-14 14:48 ` Andreas Hindborg
2025-11-05 23:01 ` [PATCH v4 5/9] rust: percpu: introduce a rust API for dynamic " Mitchell Levy
2025-11-14 15:24 ` Andreas Hindborg
2025-11-05 23:01 ` [PATCH v4 6/9] rust: percpu: add a rust per-CPU variable sample Mitchell Levy
2025-11-05 23:01 ` [PATCH v4 7/9] rust: percpu: Support non-zeroable types for DynamicPerCpu Mitchell Levy
2025-11-14 15:18 ` Andreas Hindborg
2025-11-05 23:01 ` [PATCH v4 8/9] rust: percpu: Add pin-hole optimizations for numerics Mitchell Levy
2025-11-05 23:01 ` [PATCH v4 9/9] 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=690e8e6d.050a0220.b06fd.d2ec@mx.google.com \
--to=levymitchell0@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=apais@linux.microsoft.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=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 \
--cc=yury.norov@gmail.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