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,
	Thomas Gleixner <tglx@linutronix.de>,
	Boqun Feng <boqun.feng@gmail.com>,
	linux-kernel@vger.kernel.org,
	Daniel Almeida <daniel.almeida@collabora.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
	"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
	"Waiman Long" <longman@redhat.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>
Subject: [PATCH v11 06/14] rust: helper: Add spin_{un,}lock_irq_{enable,disable}() helpers
Date: Thu, 17 Jul 2025 14:37:58 -0400	[thread overview]
Message-ID: <20250717184055.2071216-7-lyude@redhat.com> (raw)
In-Reply-To: <20250717184055.2071216-1-lyude@redhat.com>

From: Boqun Feng <boqun.feng@gmail.com>

spin_lock_irq_disable() and spin_unlock_irq_enable() are inline
functions, to use them in Rust, helpers are introduced. This is for
interrupt disabling lock abstraction in Rust.

Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
Signed-off-by: Lyude Paul <lyude@redhat.com>
---
 rust/helpers/spinlock.c | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/rust/helpers/spinlock.c b/rust/helpers/spinlock.c
index 42c4bf01a23e4..d4e61057c2a7a 100644
--- a/rust/helpers/spinlock.c
+++ b/rust/helpers/spinlock.c
@@ -35,3 +35,18 @@ void rust_helper_spin_assert_is_held(spinlock_t *lock)
 {
 	lockdep_assert_held(lock);
 }
+
+void rust_helper_spin_lock_irq_disable(spinlock_t *lock)
+{
+	spin_lock_irq_disable(lock);
+}
+
+void rust_helper_spin_unlock_irq_enable(spinlock_t *lock)
+{
+	spin_unlock_irq_enable(lock);
+}
+
+int rust_helper_spin_trylock_irq_disable(spinlock_t *lock)
+{
+	return spin_trylock_irq_disable(lock);
+}
-- 
2.50.0


  parent reply	other threads:[~2025-07-17 18:42 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 ` Lyude Paul [this message]
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 ` [PATCH v11 11/14] rust: sync: Expose lock::Backend Lyude Paul
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-7-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=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).