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 1/9] rust: cpumask: Add a `Cpumask` iterator
Date: Fri, 7 Nov 2025 16:06:19 -0800 [thread overview]
Message-ID: <690e897d.170a0220.3b9532.0c02@mx.google.com> (raw)
In-Reply-To: <aQ08d2NUVsIf5ukH@yury>
On Thu, Nov 06, 2025 at 07:25:27PM -0500, Yury Norov wrote:
> On Wed, Nov 05, 2025 at 03:01:13PM -0800, Mitchell Levy wrote:
> > Add an iterator for `Cpumask` making use of C's `cpumask_next`.
> >
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> > Signed-off-by: Mitchell Levy <levymitchell0@gmail.com>
> > ---
> > rust/helpers/cpumask.c | 5 +++++
> > rust/kernel/cpumask.rs | 48 +++++++++++++++++++++++++++++++++++++++++++++++-
> > 2 files changed, 52 insertions(+), 1 deletion(-)
> >
> > diff --git a/rust/helpers/cpumask.c b/rust/helpers/cpumask.c
> > index eb10598a0242..d95bfa111191 100644
> > --- a/rust/helpers/cpumask.c
> > +++ b/rust/helpers/cpumask.c
> > @@ -42,6 +42,11 @@ bool rust_helper_cpumask_full(struct cpumask *srcp)
> > return cpumask_full(srcp);
> > }
> >
> > +unsigned int rust_helper_cpumask_next(int n, struct cpumask *srcp)
> > +{
> > + return cpumask_next(n, srcp);
> > +}
> > +
> > unsigned int rust_helper_cpumask_weight(struct cpumask *srcp)
> > {
> > return cpumask_weight(srcp);
> > diff --git a/rust/kernel/cpumask.rs b/rust/kernel/cpumask.rs
> > index 3fcbff438670..b7401848f59e 100644
> > --- a/rust/kernel/cpumask.rs
> > +++ b/rust/kernel/cpumask.rs
> > @@ -6,7 +6,7 @@
> >
> > use crate::{
> > alloc::{AllocError, Flags},
> > - cpu::CpuId,
> > + cpu::{self, CpuId},
> > prelude::*,
> > types::Opaque,
> > };
> > @@ -161,6 +161,52 @@ pub fn copy(&self, dstp: &mut Self) {
> > }
> > }
> >
> > +/// Iterator for a `Cpumask`.
> > +pub struct CpumaskIter<'a> {
> > + mask: &'a Cpumask,
> > + last: Option<u32>,
>
> This is not the last, it's a current CPU.
Ah, I meant it in the sense of "the last cpuid we've seen", though now
that you point it out I agree the naming here is poor. Will correct to
`current`.
> > +}
> > +
> > +impl<'a> CpumaskIter<'a> {
> > + /// Creates a new `CpumaskIter` for the given `Cpumask`.
> > + fn new(mask: &'a Cpumask) -> CpumaskIter<'a> {
> > + Self { mask, last: None }
> > + }
> > +}
> > +
> > +impl<'a> Iterator for CpumaskIter<'a> {
> > + type Item = CpuId;
> > +
> > + fn next(&mut self) -> Option<Self::Item> {
> > + // SAFETY: By the type invariant, `self.mask.as_raw` is a `struct cpumask *`.
> > + let next = unsafe {
> > + bindings::cpumask_next(
> > + if let Some(last) = self.last {
> > + last.try_into().unwrap()
> > + } else {
> > + -1
> > + },
> > + self.mask.as_raw(),
> > + )
> > + };
> > +
> > + if next == cpu::nr_cpu_ids() {
> > + None
>
> Please: if next >= cpu::nr_cpu_ids() {
>
> > + } else {
> > + self.last = Some(next);
> > + // SAFETY: `cpumask_next` returns either `nr_cpu_ids` or a valid CPU ID.
>
> Now that you've handled the no-found case in the previous block, the
> comment doesn't look correct. Can you either move it on top of the
> if-else, or just drop entirely?
Actually, now that I'm looking at this again, I think this whole if-else
thing should just be:
```
CpuId::from_u32(next)
```
which does exactly what we want here. I think this should address both
of your concerns, though please let me know if it doesn't.
Thanks,
Mitchell
> > + unsafe { Some(CpuId::from_u32_unchecked(next)) }
> > + }
> > + }
> > +}
> > +
> > +impl Cpumask {
> > + /// Returns an iterator over the set bits in the cpumask.
> > + pub fn iter(&self) -> CpumaskIter<'_> {
> > + CpumaskIter::new(self)
> > + }
> > +}
> > +
> > /// A CPU Mask pointer.
> > ///
> > /// Rust abstraction for the C `struct cpumask_var_t`.
> >
> > --
> > 2.34.1
next prev parent reply other threads:[~2025-11-08 0:06 UTC|newest]
Thread overview: 16+ 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 [this message]
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
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-05 23:01 ` [PATCH v4 5/9] rust: percpu: introduce a rust API for dynamic " Mitchell Levy
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-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=690e897d.170a0220.3b9532.0c02@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;
as well as URLs for NNTP newsgroup(s).