From: Lyude Paul <lyude@redhat.com>
To: rust-for-linux@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Boqun Feng <boqun.feng@gmail.com>,
linux-kernel@vger.kernel.org,
Daniel Almeida <daniel.almeida@collabora.com>
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>,
"Mitchell Levy" <levymitchell0@gmail.com>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>
Subject: [PATCH v11 11/14] rust: sync: Expose lock::Backend
Date: Thu, 17 Jul 2025 14:38:03 -0400 [thread overview]
Message-ID: <20250717184055.2071216-12-lyude@redhat.com> (raw)
In-Reply-To: <20250717184055.2071216-1-lyude@redhat.com>
Due to the addition of sync::lock::Backend::Context, lock guards can be
returned with a different Backend than their respective lock. Since we'll
be adding a trait bound for Backend to GlobalGuard in order to support
this, users will need to be able to directly refer to Backend so that they
can use it in trait bounds.
So, let's make this easier for users and expose Backend in sync.
Signed-off-by: Lyude Paul <lyude@redhat.com>
---
rust/kernel/sync.rs | 1 +
1 file changed, 1 insertion(+)
diff --git a/rust/kernel/sync.rs b/rust/kernel/sync.rs
index f1e448e096ea9..ebf004193bca5 100644
--- a/rust/kernel/sync.rs
+++ b/rust/kernel/sync.rs
@@ -25,6 +25,7 @@
pub use lock::spinlock::{
new_spinlock, new_spinlock_irq, SpinLock, SpinLockGuard, SpinLockIrq, SpinLockIrqGuard,
};
+pub use lock::Backend;
pub use locked_by::LockedBy;
/// Represents a lockdep class. It's a wrapper around C's `lock_class_key`.
--
2.50.0
next prev parent reply other threads:[~2025-07-17 18:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 18:37 [PATCH v11 00/14] Refcounted interrupts, SpinLockIrq for rust Lyude Paul
2025-07-17 18:37 ` [PATCH v11 01/14] preempt: Introduce HARDIRQ_DISABLE_BITS Lyude Paul
2025-07-17 18:37 ` [PATCH v11 02/14] preempt: Introduce __preempt_count_{sub, add}_return() Lyude Paul
2025-07-17 18:37 ` [PATCH v11 03/14] irq & spin_lock: Add counted interrupt disabling/enabling Lyude Paul
2025-07-17 18:37 ` [PATCH v11 04/14] irq: Add KUnit test for refcounted interrupt enable/disable Lyude Paul
2025-07-17 18:37 ` [PATCH v11 05/14] rust: Introduce interrupt module Lyude Paul
2025-07-17 18:37 ` [PATCH v11 06/14] rust: helper: Add spin_{un,}lock_irq_{enable,disable}() helpers Lyude Paul
2025-07-17 18:37 ` [PATCH v11 07/14] rust: sync: Add SpinLockIrq Lyude Paul
2025-07-17 18:38 ` [PATCH v11 08/14] rust: sync: Introduce lock::Backend::Context Lyude Paul
2025-07-17 18:38 ` [PATCH v11 09/14] rust: sync: lock: Add `Backend::BackendInContext` Lyude Paul
2025-07-17 18:38 ` [PATCH v11 10/14] rust: sync: Add a lifetime parameter to lock::global::GlobalGuard Lyude Paul
2025-07-17 18:38 ` Lyude Paul [this message]
2025-07-17 18:38 ` [PATCH v11 12/14] rust: sync: lock/global: Add Backend parameter to GlobalGuard Lyude Paul
2025-07-17 18:38 ` [PATCH v11 13/14] rust: sync: lock/global: Add BackendInContext support to GlobalLock Lyude Paul
2025-07-17 18:38 ` [PATCH v11 14/14] locking: Switch to _irq_{disable,enable}() variants in cleanup guards Lyude Paul
2025-07-17 19:07 ` [PATCH v11 00/14] Refcounted interrupts, SpinLockIrq for rust 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=20250717184055.2071216-12-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=levymitchell0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@linaro.org \
--cc=wedsonaf@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).