rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lyude Paul <lyude@redhat.com>
To: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"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>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
	"Waiman Long" <longman@redhat.com>
Subject: [PATCH v15 13/16] rust: sync: Expose lock::Backend
Date: Tue,  2 Dec 2025 13:24:21 -0500	[thread overview]
Message-ID: <20251202182720.125884-14-lyude@redhat.com> (raw)
In-Reply-To: <20251202182720.125884-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 847edd943c457..e4604d21c884a 100644
--- a/rust/kernel/sync.rs
+++ b/rust/kernel/sync.rs
@@ -29,6 +29,7 @@
 pub use lock::spinlock::{
     new_spinlock, new_spinlock_irq, SpinLock, SpinLockGuard, SpinLockIrq, SpinLockIrqGuard,
 };
+pub use lock::Backend;
 pub use locked_by::LockedBy;
 pub use refcount::Refcount;
 
-- 
2.52.0


  parent reply	other threads:[~2025-12-02 18:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 18:24 [PATCH v15 00/16] Refcounted interrupts, SpinLockIrq for rust Lyude Paul
2025-12-02 18:24 ` [PATCH v15 01/16] preempt: Introduce HARDIRQ_DISABLE_BITS Lyude Paul
2025-12-02 18:24 ` [PATCH v15 02/16] preempt: Track NMI nesting to separate per-CPU counter Lyude Paul
2025-12-02 18:24 ` [PATCH v15 03/16] preempt: Introduce __preempt_count_{sub, add}_return() Lyude Paul
2025-12-02 18:24 ` [PATCH v15 04/16] irq & spin_lock: Add counted interrupt disabling/enabling Lyude Paul
2025-12-02 18:24 ` [PATCH v15 05/16] irq: Add KUnit test for refcounted interrupt enable/disable Lyude Paul
2025-12-02 18:24 ` [PATCH v15 06/16] rust: Introduce interrupt module Lyude Paul
2025-12-02 18:24 ` [PATCH v15 07/16] rust: helper: Add spin_{un,}lock_irq_{enable,disable}() helpers Lyude Paul
2025-12-02 18:24 ` [PATCH v15 08/16] rust: sync: Add SpinLockIrq Lyude Paul
2025-12-02 18:24 ` [PATCH v15 09/16] rust: sync: Introduce lock::Backend::Context Lyude Paul
2025-12-02 18:24 ` [PATCH v15 10/16] rust: sync: lock: Add `Backend::BackendInContext` Lyude Paul
2025-12-02 18:24 ` [PATCH v15 11/16] rust: sync: lock/global: Rename B to G in trait bounds Lyude Paul
2025-12-02 18:24 ` [PATCH v15 12/16] rust: sync: Add a lifetime parameter to lock::global::GlobalGuard Lyude Paul
2025-12-02 18:24 ` Lyude Paul [this message]
2025-12-02 18:24 ` [PATCH v15 14/16] rust: sync: lock/global: Add Backend parameter to GlobalGuard Lyude Paul
2025-12-02 18:24 ` [PATCH v15 15/16] rust: sync: lock/global: Add BackendInContext support to GlobalLock Lyude Paul
2025-12-02 18:24 ` [PATCH v15 16/16] locking: Switch to _irq_{disable,enable}() variants in cleanup guards 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=20251202182720.125884-14-lyude@redhat.com \
    --to=lyude@redhat.com \
    --cc=a.hindborg@kernel.org \
    --cc=akpm@linux-foundation.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=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=lossin@kernel.org \
    --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=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 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).