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>
Subject: [RFC v10 00/14] Refcounted interrupts, SpinLockIrq for rust
Date: Tue, 27 May 2025 16:26:45 -0400 [thread overview]
Message-ID: <20250527203355.551287-1-lyude@redhat.com> (raw)
Hi! While this patch series still needs some changes on the C side, I
wanted to update things and send out the latest version of it that's
been sitting on my machine for a while now. This adds back the
mistakenly missing commit messages along with a number of other changes
that were requested.
Please keep in mind, there are still some issues with this patch series
that I do need help with solving before it can move forward:
* https://lore.kernel.org/rust-for-linux/ZxrCrlg1XvaTtJ1I@boqun-archlinux/
* Concerns around double checking the HARDIRQ bits against all
architectures that have interrupt priority support. I know what IPL is
but I really don't have a clear understanding of how this actually
fits together in the kernel's codebase or even how to find the
documentation for many of the architectures involved here.
Please help :C! If you want these rust bindings, figuring out these
two issues will let this patch seires move forward.
The previous version of this patch series can be found here:
https://lore.kernel.org/rust-for-linux/20250227221924.265259-4-lyude@redhat.com/T/
Boqun Feng (6):
preempt: Introduce HARDIRQ_DISABLE_BITS
preempt: Introduce __preempt_count_{sub, add}_return()
irq & spin_lock: Add counted interrupt disabling/enabling
rust: helper: Add spin_{un,}lock_irq_{enable,disable}() helpers
rust: sync: lock: Add `Backend::BackendInContext`
locking: Switch to _irq_{disable,enable}() variants in cleanup guards
Lyude Paul (8):
rust: Introduce interrupt module
rust: sync: Add SpinLockIrq
rust: sync: Introduce lock::Backend::Context
rust: sync: Add a lifetime parameter to lock::global::GlobalGuard
rust: sync: lock/global: Rename B to G in trait bounds
rust: sync: Expose lock::Backend
rust: sync: lock/global: Add Backend parameter to GlobalGuard
rust: sync: lock/global: Add BackendInContext support to GlobalLock
arch/arm64/include/asm/preempt.h | 18 +++
arch/s390/include/asm/preempt.h | 19 +++
arch/x86/include/asm/preempt.h | 10 ++
include/asm-generic/preempt.h | 14 +++
include/linux/irqflags.h | 1 -
include/linux/irqflags_types.h | 6 +
include/linux/preempt.h | 20 +++-
include/linux/spinlock.h | 88 +++++++++++---
include/linux/spinlock_api_smp.h | 27 +++++
include/linux/spinlock_api_up.h | 8 ++
include/linux/spinlock_rt.h | 16 +++
kernel/locking/spinlock.c | 31 +++++
kernel/softirq.c | 3 +
rust/helpers/helpers.c | 1 +
rust/helpers/interrupt.c | 18 +++
rust/helpers/spinlock.c | 15 +++
rust/kernel/interrupt.rs | 83 +++++++++++++
rust/kernel/lib.rs | 1 +
rust/kernel/sync.rs | 5 +-
rust/kernel/sync/lock.rs | 69 ++++++++++-
rust/kernel/sync/lock/global.rs | 91 ++++++++++-----
rust/kernel/sync/lock/mutex.rs | 2 +
rust/kernel/sync/lock/spinlock.rs | 186 ++++++++++++++++++++++++++++++
23 files changed, 680 insertions(+), 52 deletions(-)
create mode 100644 rust/helpers/interrupt.c
create mode 100644 rust/kernel/interrupt.rs
base-commit: a3b2347343e077e81d3c169f32c9b2cb1364f4cc
--
2.49.0
next reply other threads:[~2025-05-27 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 20:26 Lyude Paul [this message]
2025-05-27 20:36 ` 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=20250527203355.551287-1-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=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
/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
all inboxes | Powered by JetHome®