From: Boqun Feng <boqun.feng@gmail.com>
To: phasta@kernel.org
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Asahi Lina" <lina+kernel@asahilina.net>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Krishna Ketan Rai" <prafulrai522@gmail.com>,
"Lyude Paul" <lyude@redhat.com>,
"Mitchell Levy" <levymitchell0@gmail.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
llvm@lists.linux.dev, dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH] rust: sync: Add dma_fence abstractions
Date: Fri, 26 Sep 2025 08:44:43 -0700 [thread overview]
Message-ID: <aNa069wZv1cn8VGh@tardis.local> (raw)
In-Reply-To: <12c09de235023c99a8a864b17b2f797c7339bb7b.camel@mailbox.org>
On Fri, Sep 26, 2025 at 10:48:06AM +0200, Philipp Stanner wrote:
[..]
> > >
> > > Regarding the manually created spinlock of mine: I so far never need
> > > that spinlock anywhere in Rust and wasn't sure what's then the best way
> > > to pass a "raw" spinlock to C.
> > >
> >
> > You can use `SpinLock<()>` for this purpose, no need to add new
> > bindings.
>
> The dma_fence C backend needs a spinlock pointer, given to it by the
> driver (so Rust code).
>
> How do I pass a SpinLock<()> to a C function? AFAICS SpinLock doesn't
> implement as_raw(), so I'd have to implement it, wouldn't I?
>
Technically you can use a `&raw` to get the address of the spinlock and
just use it, since `SpinLock<()>` is `repr(C)`, so it's transparent to a
spinlock_t. So you don't have to ;-)
However, while we are at it, it makes sense that we do it right.
> Or rather, as it looks, I'd have to implement it for SpinLockBackend?
>
I think the below should work, we already have a special from_raw() for
Lock<()>, it makes sense to have a special as_raw() as well.
Let me know if you want me to send a proper patch, or feel free to add
one in your patchset ;-)
diff --git a/rust/kernel/sync/lock.rs b/rust/kernel/sync/lock.rs
index 27202beef90c..78f3287a1372 100644
--- a/rust/kernel/sync/lock.rs
+++ b/rust/kernel/sync/lock.rs
@@ -160,6 +160,13 @@ pub unsafe fn from_raw<'a>(ptr: *mut B::State) -> &'a Self {
// `B::State`.
unsafe { &*ptr.cast() }
}
+
+ /// Obtains the raw pointer from a [`Lock`].
+ ///
+ /// This can be useful for working with a lock user outside Rust.
+ pub fn as_raw(&self) -> *mut B::State {
+ self.state.get()
+ }
}
impl<T: ?Sized, B: Backend> Lock<T, B> {
Regards,
Boqun
>
> P.
>
> >
> > [1]: https://lore.kernel.org/rust-for-linux/20250905044141.77868-1-boqun.feng@gmail.com/
> >
> > Regards,
> > Boqun
> >
> > >
> > > So much from my side. Hope to hear from you.
> > >
> > > (I've compiled and tested this with the unit test on the current -rc3)
> > >
> > > Philipp
> > > ---
> > [...]
>
next prev parent reply other threads:[~2025-09-26 15:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 12:30 [RFC PATCH] rust: sync: Add dma_fence abstractions Philipp Stanner
2025-09-18 13:11 ` Christian König
2025-09-18 13:53 ` Philipp Stanner
2025-09-18 13:52 ` Boqun Feng
2025-09-26 8:48 ` Philipp Stanner
2025-09-26 15:44 ` Boqun Feng [this message]
2025-09-26 16:10 ` Boqun Feng
2025-09-27 9:01 ` Philipp Stanner
2025-09-27 13:33 ` Boqun Feng
2025-09-28 14:34 ` Christian König
2025-09-28 15:26 ` Philipp Stanner
2025-09-28 15:57 ` Christian König
2025-09-27 12:14 ` Miguel Ojeda
2025-09-27 14:03 ` Boqun Feng
2025-09-28 15:20 ` Danilo Krummrich
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=aNa069wZv1cn8VGh@tardis.local \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=justinstitt@google.com \
--cc=levymitchell0@gmail.com \
--cc=lina+kernel@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=longman@redhat.com \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=phasta@kernel.org \
--cc=prafulrai522@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@linaro.org \
--cc=wedsonaf@gmail.com \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.