[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZqQTXUl4w6LRPqLh@boqun-archlinux>
Date: Fri, 26 Jul 2024 14:21:33 -0700
From: Boqun Feng <boqun.feng@...il.com>
To: Lyude Paul <lyude@...hat.com>
Cc: rust-for-linux@...r.kernel.org, Danilo Krummrich <dakr@...hat.com>,
airlied@...hat.com, Ingo Molnar <mingo@...hat.com>,
Will Deacon <will@...nel.org>, Waiman Long <longman@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...sung.com>,
Alice Ryhl <aliceryhl@...gle.com>,
Martin Rodriguez Reboredo <yakoyoku@...il.com>,
FUJITA Tomonori <fujita.tomonori@...il.com>,
Aakash Sen Sharma <aakashsensharma@...il.com>,
Valentin Obst <kernel@...entinobst.de>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] rust: Introduce irq module
On Thu, Jul 25, 2024 at 06:27:50PM -0400, Lyude Paul wrote:
[...]
> +pub struct IrqDisabled<'a>(PhantomData<&'a ()>);
I think you need to make this type !Send and !Sync (because you are
going to make it Copy). Otherwise, you will be able to pass the irq
disabled token to another thread on a different CPU which doesn't have
irq disabled.
Regards,
Boqun
Powered by blists - more mailing lists