rust: Add irq abstraction, SpinLockIrq
Subsystems (4)
Lyude Paul
reviewerv5 cover rust: Add irq abstraction, SpinLockIrq
This adds a simple interface for disabling and enabling CPUs, along with the ability to mark a function as expecting interrupts be disabled - along with adding bindings for spin_lock_irqsave/spin_lock_irqrestore().
Current example usecase (very much WIP driver) in rvkms:
https://gitlab.freedesktop.org/lyudess/linux/-/commits/rvkms-example-08012024
specifically drivers/gpu/drm/rvkms/crtc.rs
Lyude Paul (3):
rust: Introduce irq module
rust: sync: Introduce lock::Backend::Context
rust: sync: Add SpinLockIrq
rust/helpers/helpers.c | 1 + rust/helpers/irq.c | 22 +++++++ rust/kernel/irq.rs | 90 +++++++++++++++++++++++++ rust/kernel/lib.rs | 1 + rust/kernel/sync.rs | 2 +- rust/kernel/sync/lock.rs | 17 ++++- rust/kernel/sync/lock/mutex.rs | 1 + rust/kernel/sync/lock/spinlock.rs | 105 ++++++++++++++++++++++++++++++ 8 files changed, 236 insertions(+), 3 deletions(-) create mode 100644 rust/helpers/irq.c create mode 100644 rust/kernel/irq.rs
base-commit: 93dc3be19450447a3a7090bd1dfb9f3daac3e8d2
Signature · 1 line
2.46.0
Lyude Paul
reviewerPATCH v5 1/3 rust: Introduce irq module
This introduces a module for dealing with interrupt-disabled contexts, including the ability to enable and disable interrupts (with_irqs_disabled()) - along with the ability to annotate functions as expecting that IRQs are already disabled on the local CPU.
---
V2:
* Actually make it so that we check whether or not we have interrupts disabled with debug assertions
* Fix issues in the documentation (added suggestions, missing periods, made sure that all rustdoc examples compile properly)
* Pass IrqDisabled by value, not reference
* Ensure that IrqDisabled is !Send and !Sync using PhantomData<(&'a (), *mut ())>
* Add all of the suggested derives from Benno Lossin
V3:
* Use impl for FnOnce bounds in with_irqs_disabled()
* Use higher-ranked trait bounds for the lifetime of with_irqs_disabled()
* Wording changes in the documentation for the module itself
V4:
* Use the actual unsafe constructor for IrqDisabled in with_irqs_disabled()
* Fix comment style in with_irqs_disabled example
* Check before calling local_irq_restore() in with_irqs_disabled that interrupts are still disabled. It would have been nice to do this from a Drop implementation like I hoped, but I realized rust doesn't allow that for types that implement Copy.
* Document that interrupts can't be re-enabled within the cb provided to with_irqs_disabled, and link to the github issue I just filed about this that describes the solution for this.
V5:
* Rebase against rust-next for the helpers split
* Fix typo (enabled -> disabled) - Dirk
--- rust/helpers/helpers.c | 1 + rust/helpers/irq.c | 22 +++++++++++ rust/kernel/irq.rs | 90 ++++++++++++++++++++++++++++++++++++++++++ rust/kernel/lib.rs | 1 + 4 files changed, 114 insertions(+) create mode 100644 rust/helpers/irq.c create mode 100644 rust/kernel/irq.rs
rust/helpers/helpers.c +1 -0
@@ -12,6 +12,7 @@#include "build_assert.c" #include "build_bug.c" #include "err.c" +#include "irq.c" #include "kunit.c" #include "mutex.c" #include "page.c"
rust/helpers/irq.c new file +22 -0
@@ -0,0 +1,22 @@ +// SPDX-License-Identifier: GPL-2.0 + +#include <linux/irqflags.h> + +unsigned long rust_helper_local_irq_save (void ) +{ +unsigned long flags; + +local_irq_save (flags); + +return flags; +} + +void rust_helper_local_irq_restore (unsigned long flags) +{ +local_irq_restore (flags); +} + +bool rust_helper_irqs_disabled (void ) +{ +return irqs_disabled (); +}
rust/kernel/irq.rs new file +90 -0
90 lines not on this page · raw message
rust/kernel/lib.rs +1 -0
@@ -36,6 +36,7 @@pub mod firmware;pub mod init;pub mod ioctl; +pub mod irq;#[cfg( CONFIG_KUNIT )] pub mod kunit;pub mod list;
Signature · 1 line
2.46.0
Re: [PATCH v5 1/3] rust: Introduce irq module
Quoted 41 lines · Lyude Paul
This introduces a module for dealing with interrupt-disabled contexts, including the ability to enable and disable interrupts (
with_irqs_disabled()) - along with the ability to annotate functions as expecting that IRQs are already disabled on the local CPU.Signed-off-by Lyude Paul <[email protected]>---
V2:
* Actually make it so that we check whether or not we have interrupts disabled with debug assertions
* Fix issues in the documentation (added suggestions, missing periods, made sure that all rustdoc examples compile properly)
* Pass IrqDisabled by value, not reference
* Ensure that IrqDisabled is !Send and !Sync using PhantomData<(&'a (), *mut ())>
* Add all of the suggested derives from Benno LossinV3:
* Useimplfor FnOnce bounds inwith_irqs_disabled()
* Use higher-ranked trait bounds for the lifetime ofwith_irqs_disabled()
* Wording changes in the documentation for the module itselfV4:
* Use the actual unsafe constructor for IrqDisabled inwith_irqs_disabled()
* Fix comment style inwith_irqs_disabledexample
* Check before callinglocal_irq_restore()inwith_irqs_disabledthat interrupts are still disabled. It would have been nice to do this from a Drop implementation like I hoped, but I realized rust doesn't allow that for types that implement Copy.
* Document that interrupts can't be re-enabled within thecbprovided towith_irqs_disabled, and link to the github issue I just filed about this that describes the solution for this.V5:
* Rebase against rust-next for the helpers split
* Fix typo (enabled -> disabled) - DirkSigned-off-by Lyude Paul <[email protected]>
Quoted 8 lines
--- rust/helpers/helpers.c | 1 + rust/helpers/irq.c | 22 +++++++++++ rust/kernel/irq.rs | 90 ++++++++++++++++++++++++++++++++++++++++++ rust/kernel/lib.rs | 1 + 4 files changed, 114 insertions(+) create mode 100644 rust/helpers/irq.c create mode 100644 rust/kernel/irq.rs
This looks pretty good, I have two documentation improvements below, with those fixed:
Quoted 11 lines
rust/kernel/irq.rs new file +5
-0@@ -0,0 +1,90 @@ +// SPDX-License-Identifier: GPL-2.0 + +//! Interrupt controls +//! +//! This module allows Rust code to control processor interrupts. [`with_irqs_disabled()`] may be
rust/kernel/irq.rs line 15
Quoted 10 lines
rust/kernel/irq.rs new file +10
-0+//! used for nested disables of interrupts, whereas [`IrqDisabled`] can be used for annotating code +//! that requires interrupts to be disabled. + +use bindings; +use core::marker::*; + +/// A token that is only available in contexts where IRQs are disabled. +/// +/// [`IrqDisabled`] is marker made available when interrupts are not active. Certain functions take +/// an [`IrqDisabled`] in order to indicate that they may only be run in IRQ-free contexts.
I feel like "indicate" is not strong enough, how about using "require"?
Quoted 23 lines
rust/kernel/irq.rs new file +20
-0+/// +/// This is a marker type; it has no size, and is simply used as a compile-time guarantee that +/// interrupts are disabled where required. +/// +/// This token can be created by [`with_irqs_disabled`]. See [`with_irqs_disabled`] for examples and +/// further information. +#[derive( Copy , Clone , Debug , Ord , Eq , PartialOrd , PartialEq , Hash )] +pub struct IrqDisabled <'a>(PhantomData <(&'a (), *mut ())>); +/// Run the closure `cb` with interrupts disabled on the local CPU. +/// +/// This creates an [`IrqDisabled`] token, which can be passed to functions that must be run +/// without interrupts. Note that interrupts must be disabled for the entire duration of `cb`, they +/// cannot be re-enabled. In the future, this may be expanded on +/// [as documented here](https://github.com/Rust-for-Linux/linux/issues/1115). +/// +/// # Examples +/// +/// Using [`with_irqs_disabled`] to call a function that can only be called with interrupts +/// disabled: +///
rust/kernel/irq.rs line 71
Quoted 10 lines
rust/kernel/irq.rs new file +10
-0+/// ``` +/// use kernel::irq::{IrqDisabled, with_irqs_disabled}; +/// +/// // Requiring interrupts be disabled to call a function +/// fn dont_interrupt_me(_irq: IrqDisabled<'_>) { +/// // When this token is available, IRQs are known to be disabled. Actions that rely on this +/// // can be safely performed +/// } +/// +/// // Disabling interrupts. They'll be re-enabled once this closure completes.
Please change this to be "Disables interrupts, their previous state will be restored once the closure completes.".
ie it is important to stress that this can be nested. Please also add this in a paragraph above the examples.
---
Cheers,
Benno
Quoted 34 lines
rust/kernel/irq.rs new file +19
-0+/// with_irqs_disabled(|irq| dont_interrupt_me(irq)); +/// ``` +#[inline] +pub fn with_irqs_disabled <T >(cb:impl for <'a>FnOnce (IrqDisabled <'a>) ->T ) ->T { +// SAFETY: FFI call with no special requirements +let flags =unsafe { bindings::local_irq_save () }; + +// SAFETY: We just disabled IRQs using `local_irq_save()` +let ret =cb (unsafe {IrqDisabled ::new () }); + +// Confirm that IRQs are still disabled now that the callback has finished +// SAFETY: FFI call with no special requirements +debug_assert! (unsafe { bindings::irqs_disabled () }); + +// SAFETY: `flags` comes from our previous call to local_irq_save +unsafe { bindings::local_irq_restore (flags) }; + + ret +}rust/kernel/lib.rs +1
-1@@ -36,6 +36,7 @@pub mod firmware;pub mod init;pub mod ioctl; +pub mod irq;#[cfg( CONFIG_KUNIT )] pub mod kunit;pub mod list; --2.46.0
Re: [PATCH v5 1/3] rust: Introduce irq module
In reply to Lyude PaulGary Guo
maintainerRe: [PATCH v5 1/3] rust: Introduce irq module
In reply to Lyude PaulQuoted 101 lines · On Thu, 12 Sep 2024 15:04:16 -0400 Lyude Paul <[email protected]> wrote:
This introduces a module for dealing with interrupt-disabled contexts, including the ability to enable and disable interrupts (
with_irqs_disabled()) - along with the ability to annotate functions as expecting that IRQs are already disabled on the local CPU.Signed-off-by Lyude Paul <[email protected]>---
V2:
* Actually make it so that we check whether or not we have interrupts disabled with debug assertions
* Fix issues in the documentation (added suggestions, missing periods, made sure that all rustdoc examples compile properly)
* Pass IrqDisabled by value, not reference
* Ensure that IrqDisabled is !Send and !Sync using PhantomData<(&'a (), *mut ())>
* Add all of the suggested derives from Benno LossinV3:
* Useimplfor FnOnce bounds inwith_irqs_disabled()
* Use higher-ranked trait bounds for the lifetime ofwith_irqs_disabled()
* Wording changes in the documentation for the module itselfV4:
* Use the actual unsafe constructor for IrqDisabled inwith_irqs_disabled()
* Fix comment style inwith_irqs_disabledexample
* Check before callinglocal_irq_restore()inwith_irqs_disabledthat interrupts are still disabled. It would have been nice to do this from a Drop implementation like I hoped, but I realized rust doesn't allow that for types that implement Copy.
* Document that interrupts can't be re-enabled within thecbprovided towith_irqs_disabled, and link to the github issue I just filed about this that describes the solution for this.V5:
* Rebase against rust-next for the helpers split
* Fix typo (enabled -> disabled) - DirkSigned-off-by Lyude Paul <[email protected]>--- rust/helpers/helpers.c | 1 + rust/helpers/irq.c | 22 +++++++++++ rust/kernel/irq.rs | 90 ++++++++++++++++++++++++++++++++++++++++++ rust/kernel/lib.rs | 1 + 4 files changed, 114 insertions(+) create mode 100644 rust/helpers/irq.c create mode 100644 rust/kernel/irq.rsrust/helpers/helpers.c +1
-0@@ -12,6 +12,7 @@#include "build_assert.c" #include "build_bug.c" #include "err.c" +#include "irq.c" #include "kunit.c" #include "mutex.c" #include "page.c" rust/helpers/irq.c new file +22
-0@@ -0,0 +1,22 @@ +// SPDX-License-Identifier: GPL-2.0 + +#include <linux/irqflags.h> + +unsigned long rust_helper_local_irq_save (void ) +{ +unsigned long flags; + +local_irq_save (flags); + +return flags; +} + +void rust_helper_local_irq_restore (unsigned long flags) +{ +local_irq_restore (flags); +} + +bool rust_helper_irqs_disabled (void ) +{ +return irqs_disabled (); +}rust/kernel/irq.rs new file +5
-0@@ -0,0 +1,90 @@ +// SPDX-License-Identifier: GPL-2.0 + +//! Interrupt controls +//! +//! This module allows Rust code to control processor interrupts. [`with_irqs_disabled()`] may be
rust/kernel/irq.rs line 15
Quoted 10 lines
rust/kernel/irq.rs new file +10
-0+//! used for nested disables of interrupts, whereas [`IrqDisabled`] can be used for annotating code +//! that requires interrupts to be disabled. + +use bindings; +use core::marker::*; + +/// A token that is only available in contexts where IRQs are disabled. +/// +/// [`IrqDisabled`] is marker made available when interrupts are not active. Certain functions take +/// an [`IrqDisabled`] in order to indicate that they may only be run in IRQ-free contexts.
I think this should be encoded as a type invariant?
Quoted 21 lines
rust/kernel/irq.rs new file +21
-0+/// +/// This is a marker type; it has no size, and is simply used as a compile-time guarantee that +/// interrupts are disabled where required. +/// +/// This token can be created by [`with_irqs_disabled`]. See [`with_irqs_disabled`] for examples and +/// further information. +#[derive( Copy , Clone , Debug , Ord , Eq , PartialOrd , PartialEq , Hash )] +pub struct IrqDisabled <'a>(PhantomData <(&'a (), *mut ())>); + +impl IrqDisabled <'_> { +/// Create a new [`IrqDisabled`] without disabling interrupts. +/// +/// This creates an [`IrqDisabled`] token, which can be passed to functions that must be run +/// without interrupts. If debug assertions are enabled, this function will assert that +/// interrupts are disabled upon creation. Otherwise, it has no size or cost at runtime. +/// +/// # Panics +/// +/// If debug assertions are enabled, this function will panic if interrupts are not disabled +/// upon creation. +///
rust/kernel/irq.rs line 46
Quoted 10 lines
rust/kernel/irq.rs new file +10
-0+/// # Safety +/// +/// This function must only be called in contexts where it is already known that interrupts have +/// been disabled for the current CPU, as the user is making a promise that they will remain +/// disabled at least until this [`IrqDisabled`] is dropped. +pub unsafe fn new () ->Self { +// SAFETY: FFI call with no special requirements +debug_assert! (unsafe { bindings::irqs_disabled () }); + +Self (PhantomData )
This needs to assert INVARIANT.
Quoted 56 lines
rust/kernel/irq.rs new file +44
-0+ } +} + +/// Run the closure `cb` with interrupts disabled on the local CPU. +/// +/// This creates an [`IrqDisabled`] token, which can be passed to functions that must be run +/// without interrupts. Note that interrupts must be disabled for the entire duration of `cb`, they +/// cannot be re-enabled. In the future, this may be expanded on +/// [as documented here](https://github.com/Rust-for-Linux/linux/issues/1115). +/// +/// # Examples +/// +/// Using [`with_irqs_disabled`] to call a function that can only be called with interrupts +/// disabled: +/// +/// ``` +/// use kernel::irq::{IrqDisabled, with_irqs_disabled}; +/// +/// // Requiring interrupts be disabled to call a function +/// fn dont_interrupt_me(_irq: IrqDisabled<'_>) { +/// // When this token is available, IRQs are known to be disabled. Actions that rely on this +/// // can be safely performed +/// } +/// +/// // Disabling interrupts. They'll be re-enabled once this closure completes. +/// with_irqs_disabled(|irq| dont_interrupt_me(irq)); +/// ``` +#[inline] +pub fn with_irqs_disabled <T >(cb:impl for <'a>FnOnce (IrqDisabled <'a>) ->T ) ->T { +// SAFETY: FFI call with no special requirements +let flags =unsafe { bindings::local_irq_save () }; + +// SAFETY: We just disabled IRQs using `local_irq_save()` +let ret =cb (unsafe {IrqDisabled ::new () }); + +// Confirm that IRQs are still disabled now that the callback has finished +// SAFETY: FFI call with no special requirements +debug_assert! (unsafe { bindings::irqs_disabled () }); + +// SAFETY: `flags` comes from our previous call to local_irq_save +unsafe { bindings::local_irq_restore (flags) }; + + ret +}rust/kernel/lib.rs +1
-0@@ -36,6 +36,7 @@pub mod firmware;pub mod init;pub mod ioctl; +pub mod irq;#[cfg( CONFIG_KUNIT )] pub mod kunit;pub mod list;
Lyude Paul
reviewerPATCH v5 2/3 rust: sync: Introduce lock::Backend::Context
In reply to Lyude PaulNow that we've introduced an IrqDisabled token for marking contexts in which IRQs are disabled, we need a way to be able to pass it to locks that require that IRQs are disabled. In order to continue using the lock::Backend type instead of inventing our own thing, we accomplish this by adding the associated Context type, along with a lock_with() function that can accept a Context when acquiring a lock. To allow current users of context-less locks to keep using the normal lock() method, we take an example from Wedson Almeida Filho's work and add a where T<'a>: Default bound to lock() so that it can only be called on lock types where the context is simply a placeholder value, then re-implement it through the new lock_with() function.
---
V3:
* Use explicit lifetimes in lock_with() to ensure self and _context have the same lifetime (Benno)
* Use () for locks that don't need a Context instead of PhantomData (Benno) V4:
* Fix typo (Dirk)
--- rust/kernel/sync/lock.rs | 17 +++++++++++++++-- rust/kernel/sync/lock/mutex.rs | 1 + rust/kernel/sync/lock/spinlock.rs | 1 + 3 files changed, 17 insertions(+), 2 deletions(-)
rust/kernel/sync/lock.rs +15 -2
@@ -38,6 +38,9 @@ pub unsafe trait Backend {/// [`unlock`]: Backend::unlock type GuardState ; +/// The context which must be provided to acquire the lock. +type Context <'a>; +/// Initialises the lock. /// /// # Safety
@@ -120,14 +123,24 @@ pub fn new(t: T, name: &'static CStr, key: &'static LockClassKey) -> impl PinIni }impl <T : ?Sized ,B :Backend >Lock <T ,B > { -/// Acquires the lock and gives the caller access to the data protected by it. -pub fn lock (&self) ->Guard <'_,T ,B > { +/// Acquires the lock with the given context and gives the caller access to the data protected +/// by it. +pub fn lock_with <'a>(&'a self, _context:B ::Context <'a>) ->Guard <'a,T ,B > {// SAFETY: The constructor of the type calls `init`, so the existence of the object proves // that `init` was called. let state =unsafe {B ::lock (self.state.get ()) };// SAFETY: The lock was just acquired. unsafe {Guard ::new (self, state) } } + +/// Acquires the lock and gives the caller access to the data protected by it. +#[inline] +pub fn lock <'a>(&'a self) ->Guard <'a,T ,B > +where +B ::Context <'a>:Default , + { + self.lock_with (B ::Context ::default ()) + } }/// A lock guard.
rust/kernel/sync/lock/mutex.rs +1 -0
@@ -93,6 +93,7 @@ macro_rules! new_mutex {unsafe impl super ::Backend for MutexBackend {type State = bindings::mutex ;type GuardState = (); +type Context <'a> = ();unsafe fn init ( ptr: *mut Self::State,
rust/kernel/sync/lock/spinlock.rs +1 -0
@@ -92,6 +92,7 @@ macro_rules! new_spinlock {unsafe impl super ::Backend for SpinLockBackend {type State = bindings::spinlock_t ;type GuardState = (); +type Context <'a> = ();unsafe fn init ( ptr: *mut Self::State,
Signature · 1 line
2.46.0
Re: [PATCH v5 2/3] rust: sync: Introduce lock::Backend::Context
Quoted 16 lines · Lyude Paul
Now that we've introduced an
IrqDisabledtoken for marking contexts in which IRQs are disabled, we need a way to be able to pass it to locks that require that IRQs are disabled. In order to continue using thelock::Backendtype instead of inventing our own thing, we accomplish this by adding the associated Context type, along with alock_with()function that can accept a Context when acquiring a lock. To allow current users of context-less locks to keep using the normallock()method, we take an example from Wedson Almeida Filho's work and add awhere T<'a>: Defaultbound tolock()so that it can only be called on lock types where the context is simply a placeholder value, then re-implement it through the newlock_with()function.Signed-off-by Lyude Paul <[email protected]>---
Quoted 8 lines
V3:
* Use explicit lifetimes inlock_with()to ensure self and_contexthave the same lifetime (Benno)
* Use () for locks that don't need a Context instead of PhantomData (Benno) V4:
* Fix typo (Dirk)Signed-off-by Lyude Paul <[email protected]>
I don't think that you need your SOB twice.
Quoted 5 lines
--- rust/kernel/sync/lock.rs | 17 +++++++++++++++-- rust/kernel/sync/lock/mutex.rs | 1 + rust/kernel/sync/lock/spinlock.rs | 1 + 3 files changed, 17 insertions(+), 2 deletions(-)
This looks good:
---
Cheers,
Benno
Re: [PATCH v5 2/3] rust: sync: Introduce lock::Backend::Context
In reply to Lyude PaulLyude Paul
reviewerPATCH v5 3/3 rust: sync: Add SpinLockIrq
In reply to Lyude PaulA variant of SpinLock that is expected to be used in noirq contexts, and thus requires that the user provide an kernel::irq::IrqDisabled to prove they are in such a context upon lock acquisition. This is the rust equivalent of spin_lock_irqsave()/spin_lock_irqrestore().
---
V2:
* s/IrqSpinLock/SpinLockIrq/
* Implement lock::Backend now that we have Context
* Add missing periods
* Make sure rustdoc examples compile correctly
* Add documentation suggestions
--- rust/kernel/sync.rs | 2 +- rust/kernel/sync/lock/spinlock.rs | 104 ++++++++++++++++++++++++++++++ 2 files changed, 105 insertions(+), 1 deletion(-)
rust/kernel/sync.rs +1 -1
@@ -15,7 +15,7 @@pub use arc::{Arc ,ArcBorrow ,UniqueArc };pub use condvar::{new_condvar,CondVar ,CondVarTimeoutResult };pub use lock::mutex::{new_mutex,Mutex }; -pub use lock::spinlock::{new_spinlock,SpinLock }; +pub use lock::spinlock::{new_spinlock, new_spinlock_irq,SpinLock ,SpinLockIrq };pub use locked_by::LockedBy ;/// Represents a lockdep class. It's a wrapper around C's `lock_class_key`.
rust/kernel/sync/lock/spinlock.rs +104 -0
113 lines not on this page · raw message
Signature · 1 line
2.46.0
Re: [PATCH v5 3/3] rust: sync: Add SpinLockIrq
Quoted 16 lines · Lyude Paul
A variant of SpinLock that is expected to be used in noirq contexts, and thus requires that the user provide an
kernel::irq::IrqDisabledto prove they are in such a context upon lock acquisition. This is the rust equivalent of spin_lock_irqsave()/spin_lock_irqrestore().Signed-off-by Lyude Paul <[email protected]>---
V2:
* s/IrqSpinLock/SpinLockIrq/
* Implementlock::Backendnow that we haveContext
* Add missing periods
* Make sure rustdoc examples compile correctly
* Add documentation suggestions
Quoted 5 lines
Signed-off-by Lyude Paul <[email protected]>--- rust/kernel/sync.rs | 2 +- rust/kernel/sync/lock/spinlock.rs | 104 ++++++++++++++++++++++++++++++ 2 files changed, 105 insertions(+), 1 deletion(-)
---
Cheers,
Benno
Re: [PATCH v5 3/3] rust: sync: Add SpinLockIrq
In reply to Lyude PaulDaniel Almeida
maintainerThis series looks good to me. Thanks for working on it.
— Daniel
Quoted 28 lines · On Thu, 12 Sep 2024 15:04:15 -0400 Lyude Paul <[email protected]> wrote:
This adds a simple interface for disabling and enabling CPUs, along with the ability to mark a function as expecting interrupts be disabled - along with adding bindings for spin_lock_irqsave/spin_lock_irqrestore().
Current example usecase (very much WIP driver) in rvkms:
https://gitlab.freedesktop.org/lyudess/linux/-/commits/rvkms-example-08012024
specifically
drivers/gpu/drm/rvkms/crtc.rsLyude Paul (3):
rust: Introduce irq module
rust: sync: Introducelock::Backend::Context
rust: sync: Add SpinLockIrqrust/helpers/helpers.c | 1 + rust/helpers/irq.c | 22 +++++++ rust/kernel/irq.rs | 90 +++++++++++++++++++++++++ rust/kernel/lib.rs | 1 + rust/kernel/sync.rs | 2 +- rust/kernel/sync/lock.rs | 17 ++++- rust/kernel/sync/lock/mutex.rs | 1 + rust/kernel/sync/lock/spinlock.rs | 105 ++++++++++++++++++++++++++++++ 8 files changed, 236 insertions(+), 3 deletions(-) create mode 100644 rust/helpers/irq.c create mode 100644 rust/kernel/irq.rs
Quoted 1 line
base-commit:
93dc3be19450447a3a7090bd1dfb9f3daac3e8d2
With the invariant documentation of IrqDisabled fixed: