[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DG7SZND1GWR4.3C5NLKY4SYC0M@kernel.org>
Date: Fri, 06 Feb 2026 11:23:09 +0100
From: "Danilo Krummrich" <dakr@...nel.org>
To: "Boris Brezillon" <boris.brezillon@...labora.com>
Cc: "Philipp Stanner" <phasta@...nel.org>, "David Airlie"
<airlied@...il.com>, "Simona Vetter" <simona@...ll.ch>, "Alice Ryhl"
<aliceryhl@...gle.com>, "Gary Guo" <gary@...yguo.net>, "Benno Lossin"
<lossin@...nel.org>, Christian König
<christian.koenig@....com>, "Daniel Almeida"
<daniel.almeida@...labora.com>, "Joel Fernandes" <joelagnelf@...dia.com>,
<linux-kernel@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
<rust-for-linux@...r.kernel.org>
Subject: Re: [RFC PATCH 2/4] rust: sync: Add dma_fence abstractions
On Thu Feb 5, 2026 at 9:57 AM CET, Boris Brezillon wrote:
> On Tue, 3 Feb 2026 09:14:01 +0100
> Philipp Stanner <phasta@...nel.org> wrote:
> Unfortunately, I don't know how to translate that in rust, but we
> need a way to check if any path code path does a DmaFence.signal(),
> go back to the entry point (for a WorkItem, that would be
> WorkItem::run() for instance), and make it a DmaFenceSignallingPath.
> Not only that, but we need to know all the deps that make it so
> this path can be called (if I take the WorkItem example, that would
> be the path that leads to the WorkItem being scheduled).
I think we need a guard object for this that is not Send, just like for any
other lock.
Internally, those markers rely on lockdep, i.e. they just acquire and release a
"fake" lock.
Powered by blists - more mailing lists