[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5FA40D95-4FB4-4E71-8FDA-3DEC3A7FF0A5@collabora.com>
Date: Wed, 23 Jul 2025 13:18:11 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Danilo Krummrich <dakr@...nel.org>
Cc: Boqun Feng <boqun.feng@...il.com>,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>,
Trevor Gross <tmgross@...ch.edu>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Krzysztof Wilczy´nski <kwilczynski@...nel.org>,
Benno Lossin <lossin@...nel.org>,
linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org,
linux-pci@...r.kernel.org
Subject: Re: [PATCH v7 3/6] rust: irq: add support for non-threaded IRQs and
handlers
> On 23 Jul 2025, at 13:11, Danilo Krummrich <dakr@...nel.org> wrote:
>
> On Wed Jul 23, 2025 at 6:07 PM CEST, Daniel Almeida wrote:
>> On top of that, we can use the
>> words "interior mutability" somewhere in the example as well to make it even
>> clearer.
>
> You *can* have this example and I encourage it, I think it is valuable. You can
> have spinlock or mutex for this purpose in threaded handler, no?
Right, but then what goes in the hard-irq part for ThreadedHandler? I guess we
can leave that one blank then and only touch the data from the threaded part.
If that’s the case, then I think it can work too.
— Daniel
Powered by blists - more mailing lists