From: Alice Ryhl <aliceryhl@google.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: a.hindborg@kernel.org, alex.gaynor@gmail.com,
benno.lossin@proton.me, bjorn3_gh@protonmail.com,
boqun.feng@gmail.com, dakr@redhat.com, gary@garyguo.net,
linux-kernel@vger.kernel.org, linux@rasmusvillemoes.dk,
ojeda@kernel.org, rust-for-linux@vger.kernel.org,
tmgross@umich.edu, vincent.guittot@linaro.org,
yury.norov@gmail.com
Subject: Re: [PATCH 1/2] rust: Add initial cpumask abstractions
Date: Thu, 27 Feb 2025 13:19:43 +0100 [thread overview]
Message-ID: <CAH5fLgg8PvCEEks81Dy_3eRBkVG4P0a7usB2cfP2pbcSw495FA@mail.gmail.com> (raw)
In-Reply-To: <20250227104640.sa6vqdz7j5hwjigs@vireshk-i7>
On Thu, Feb 27, 2025 at 11:46 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 25-02-25, 18:02, Alice Ryhl wrote:
> > diff --git a/rust/kernel/cpumask.rs b/rust/kernel/cpumask.rs
> > +/// This corresponds to the C type alias `cpumask_var_t`.
> > +pub struct CpumaskBox {
> > + #[cfg(CONFIG_CPUMASK_OFFSTACK)]
> > + ptr: NonNull<Cpumask>,
> > + #[cfg(not(CONFIG_CPUMASK_OFFSTACK))]
> > + mask: Cpumask,
> > +}
> >
> > +impl CpumaskBox {
> > + pub fn new(_flags: Flags) -> Result<Self, AllocError> {
> > + Ok(Self {
> > + #[cfg(CONFIG_CPUMASK_OFFSTACK)]
> > + ptr: {
> > + let mut ptr: *mut bindings::cpumask = ptr::null_mut();
> > + unsafe { bindings::zalloc_cpumask_var(&mut ptr, _flags.as_raw()) };
> > + NonNull::new(ptr.cast()).ok_or(AllocError)?
> > + },
> > #[cfg(not(CONFIG_CPUMASK_OFFSTACK))]
> > - // SAFETY: The pointer was earlier initialized from the result of `KBox::into_raw()`.
> > - unsafe {
> > - drop(KBox::from_raw(self.ptr))
> > - };
> > - }
> > + mask: unsafe { core::mem::zeroed() },
>
> This will work correctly, yes, but I wasn't sure if the Rust code
> should do this or depend on the C API and call zalloc_cpumask_var().
> The implementation of struct cpumask allows this to work right now,
> but any change where some internal state management is done, for
> example, within the structure may break the Rust side.
>
> I am okay with this way of doing it if that looks okay to you.
>
> I have made following changes over your diff.
>
> Thanks for your help in simplifying the code.
>
> --
> viresh
>
> -------------------------8<-------------------------
>
> diff --git a/rust/kernel/cpumask.rs b/rust/kernel/cpumask.rs
> index f82dafbc4e61..d56f7dc9d762 100644
> --- a/rust/kernel/cpumask.rs
> +++ b/rust/kernel/cpumask.rs
> @@ -13,20 +13,28 @@
> #[cfg(CONFIG_CPUMASK_OFFSTACK)]
> use core::ptr::{self, NonNull};
>
> +#[cfg(not(CONFIG_CPUMASK_OFFSTACK))]
> +use core::mem::MaybeUninit;
> +
> +use core::ops::{Deref, DerefMut};
> +
> /// This corresponds to the C type `struct cpumask`.
> #[repr(transparent)]
> -pub struct Cpumask {
> - mask: Opaque<bindings::cpumask>,
> -}
> +pub struct Cpumask(Opaque<bindings::cpumask>);
>
> impl Cpumask {
> - /// Creates a reference to an existing `struct cpumask` pointer.
> + /// Creates a mutable reference to an existing `struct cpumask` pointer.
> ///
> /// # Safety
> ///
> /// The caller must ensure that `ptr` is valid for writing and remains valid for the lifetime
> /// of the returned reference.
> - pub unsafe fn from_raw_mut<'a>(ptr: *mut bindings::cpumask) -> &'a mut Self {
> + pub unsafe fn from_raw_mut<'a>(ptr: *mut bindings::cpumask_var_t) -> &'a mut Self {
Why?
Perhaps put this on the CpumaskBox and keep the `struct cpumask` one here?
Alice
next prev parent reply other threads:[~2025-02-27 12:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 9:47 [PATCH 0/2] Rust: Add " Viresh Kumar
2025-02-25 9:47 ` [PATCH 1/2] rust: Add initial " Viresh Kumar
2025-02-25 9:55 ` Alice Ryhl
2025-02-25 10:54 ` Viresh Kumar
2025-02-25 11:34 ` Alice Ryhl
2025-02-25 11:36 ` Viresh Kumar
2025-02-25 11:39 ` Alice Ryhl
2025-02-25 11:52 ` Viresh Kumar
2025-02-25 11:48 ` Viresh Kumar
2025-02-25 11:53 ` Alice Ryhl
2025-02-25 17:02 ` Viresh Kumar
2025-02-25 17:12 ` Alice Ryhl
2025-02-25 18:02 ` Alice Ryhl
2025-02-27 10:46 ` Viresh Kumar
2025-02-27 12:19 ` Alice Ryhl [this message]
2025-02-28 7:09 ` Viresh Kumar
2025-02-25 9:47 ` [PATCH 2/2] MAINTAINERS: Add entry for Rust bitmap API Viresh Kumar
2025-02-26 15: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=CAH5fLgg8PvCEEks81Dy_3eRBkVG4P0a7usB2cfP2pbcSw495FA@mail.gmail.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@redhat.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=vincent.guittot@linaro.org \
--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
all inboxes | Powered by JetHome®