[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2b019479-2d32-433f-af78-c3378dee4e2b@gmail.com>
Date: Tue, 18 Feb 2025 11:58:33 +0200
From: Abdiel Janulgue <abdiel.janulgue@...il.com>
To: Robin Murphy <robin.murphy@....com>,
Daniel Almeida <daniel.almeida@...labora.com>
Cc: rust-for-linux@...r.kernel.org, dakr@...nel.org, aliceryhl@...gle.com,
Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...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@...nel.org>, Trevor Gross <tmgross@...ch.edu>,
Valentin Obst <kernel@...entinobst.de>,
open list <linux-kernel@...r.kernel.org>, Christoph Hellwig <hch@....de>,
Marek Szyprowski <m.szyprowski@...sung.com>, airlied@...hat.com,
"open list:DMA MAPPING HELPERS" <iommu@...ts.linux.dev>
Subject: Re: [PATCH v11 2/3] rust: add dma coherent allocator abstraction.
Hi Robin,
On 17/02/2025 15:52, Robin Murphy wrote:
> FWIW we've been wanting to steer away from relying on the default mask
> in new code, so it would be quite neat to actually enforce that
> allocations fail if dma_coherent_mask hasn't been explicitly set
> (assuming it's sufficiently cheap to keep a flag in the Device handle or
> something like that - it's not the end of the world if it isn't practical).
I just had a quick look on how to possible approach this and indeed
would refactor the Device binding a bit. If it is okay with you this
could go in a follow-up patch? I was hoping to upstream the initial
support first - at least with the dma_set_mask/dma_set_coherent_mask put
in place already.
Thanks!
/Abdiel
Powered by blists - more mailing lists