From: Gary Guo <gary@garyguo.net>
To: Lyude Paul <lyude@redhat.com>
Cc: rust-for-linux@vger.kernel.org,
"Danilo Krummrich" <dakr@redhat.com>,
airlied@redhat.com, "Ingo Molnar" <mingo@redhat.com>,
"Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
"Valentin Obst" <kernel@valentinobst.de>
Subject: Re: [PATCH 1/1] rust: sync: Add Lock::from_raw() for ZST data types
Date: Mon, 16 Sep 2024 23:30:43 +0100 [thread overview]
Message-ID: <20240916233043.4c06abc7.gary@garyguo.net> (raw)
In-Reply-To: <20240916220818.567277-2-lyude@redhat.com>
On Mon, 16 Sep 2024 18:05:46 -0400
Lyude Paul <lyude@redhat.com> wrote:
> A few of the APIs I've been writing bindings for (KMS in particular) rely
> on the user manually acquiring specific locks before calling certain
> functions. At the moment though, the only way of acquiring these locks in
> bindings is to simply call the C locking functions directly - since said
> locks are not acquired on the rust side of things.
>
> However - if we add `#[repr(C)]` to `Lock<T, B>`, then given `T` is a ZST -
> `Lock<T, B>` becomes equivalent in data layout to its inner `B::State`
> type. Since locks in C don't have data explicitly associated with them
> anyway, we can take advantage of this to add a `Lock::from_raw()` function
> that can translate a raw pointer to `B::State` into its proper `Lock<T, B>`
> equivalent. This lets us simply acquire a reference to the lock in question
> and work with it like it was initialized on the rust side of things,
> allowing us to use less unsafe code to implement bindings with lock
> requirements.
>
> Signed-off-by: Lyude Paul <lyude@redhat.com>
> ---
> rust/kernel/sync/lock.rs | 32 ++++++++++++++++++++++++++++++--
> 1 file changed, 30 insertions(+), 2 deletions(-)
>
> diff --git a/rust/kernel/sync/lock.rs b/rust/kernel/sync/lock.rs
> index f6c34ca4d819f..f77cb178840b2 100644
> --- a/rust/kernel/sync/lock.rs
> +++ b/rust/kernel/sync/lock.rs
> @@ -6,8 +6,8 @@
> //! spinlocks, raw spinlocks) to be provided with minimal effort.
>
> use super::LockClassKey;
> -use crate::{init::PinInit, pin_init, str::CStr, types::Opaque, types::ScopeGuard};
> -use core::{cell::UnsafeCell, marker::PhantomData, marker::PhantomPinned};
> +use crate::{init::PinInit, pin_init, prelude::*, str::CStr, types::Opaque, types::ScopeGuard};
> +use core::{cell::UnsafeCell, marker::PhantomData, marker::PhantomPinned, mem};
> use macros::pin_data;
>
> pub mod mutex;
> @@ -81,6 +81,7 @@ unsafe fn relock(ptr: *mut Self::State, guard_state: &mut Self::GuardState) {
> ///
> /// Exposes one of the kernel locking primitives. Which one is exposed depends on the lock
> /// [`Backend`] specified as the generic parameter `B`.
> +#[repr(C)]
> #[pin_data]
> pub struct Lock<T: ?Sized, B: Backend> {
> /// The kernel lock object.
> @@ -117,6 +118,33 @@ pub fn new(t: T, name: &'static CStr, key: &'static LockClassKey) -> impl PinIni
> }),
> })
> }
> +
> + /// Constructs a [`Lock`] from a raw pointer.
> + ///
> + /// This can be useful for interacting with a lock which was initialised outside of rust. This
> + /// can only be used when `T` is a ZST type.
> + ///
> + /// # Safety
> + ///
> + /// - The caller promises that `ptr` points to a valid initialised instance of [`State`].
> + /// - The caller promises that `T` is a type that it is allowed to create (e.g. `!` would not be
> + /// allowed)
I think "allowed to create" is quite vague. Is `IrqDisabled<'static>`
something that is classified as allowed to create? It is not an
uninhabited type, but it does have invariants associated with that.
Do you have a need for `T` to be arbitrary type, not just `()`? I would
prefer to see this being an impl on `Lock<(), B>` if you do not have a
specific need for arbitrary ZST types.
Best,
Gary
> + ///
> + /// [`State`]: Backend::State
> + pub unsafe fn from_raw<'a>(ptr: *mut B::State) -> &'a Self {
> + build_assert!(
> + mem::size_of::<T>() == 0,
> + "Lock::<T, B>::from_raw() can only be used if T is a ZST"
> + );
> +
> + // SAFETY:
> + // * By the safety contract `ptr` must point to a valid initialised instance of `B::State`
> + // * We just asserted that `T` is a ZST, making `state` the only non-ZST member of the
> + // struct
> + // * Combined with `#[repr(C)]`, this guarantees `Self` has an equivalent data layout to
> + // `B::State`.
> + unsafe { &*ptr.cast() }
> + }
> }
>
> impl<T: ?Sized, B: Backend> Lock<T, B> {
next prev parent reply other threads:[~2024-09-16 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 22:05 [PATCH 0/1] rust: sync: Add Lock::from_raw for ZST data types Lyude Paul
2024-09-16 22:05 ` [PATCH 1/1] rust: sync: Add Lock::from_raw() " Lyude Paul
2024-09-16 22:30 ` Gary Guo [this message]
2024-09-16 23:05 ` Lyude Paul
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=20240916233043.4c06abc7.gary@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@samsung.com \
--cc=airlied@redhat.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@redhat.com \
--cc=kernel@valentinobst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lyude@redhat.com \
--cc=mingo@redhat.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
--cc=wedsonaf@gmail.com \
--cc=will@kernel.org \
--cc=yakoyoku@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).