From: "Gary Guo" <gary@garyguo.net>
To: "Danilo Krummrich" <dakr@kernel.org>, <abdiel.janulgue@gmail.com>,
<daniel.almeida@collabora.com>, <robin.murphy@arm.com>,
<a.hindborg@kernel.org>, <gregkh@linuxfoundation.org>,
<rafael@kernel.org>, <aliceryhl@google.com>,
<acourbot@nvidia.com>, <ojeda@kernel.org>, <boqun@kernel.org>,
<gary@garyguo.net>, <bjorn3_gh@protonmail.com>,
<lossin@kernel.org>, <tmgross@umich.edu>, <tamird@kernel.org>,
<work@onurozkan.dev>, <mmaurer@google.com>
Cc: <driver-core@lists.linux.dev>, <nova-gpu@lists.linux.dev>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH 4/4] rust: dma: tie Coherent and CoherentBox to the device's bound lifetime
Date: Thu, 03 Sep 2026 14:20:07 +0100 [thread overview]
Message-ID: <DL5PMZZO1S7X.3BMZVKVUMYVM0@garyguo.net> (raw)
In-Reply-To: <20260830193824.471089-5-dakr@kernel.org>
On Sun Aug 30, 2026 at 8:37 PM BST, Danilo Krummrich wrote:
> Add a lifetime parameter to Coherent and CoherentBox that ties the DMA
> allocation to the device's bound scope, ensuring it is freed before the
> device is unbound.
>
> DMA allocations carry device resources (e.g. IOMMU mappings) that must
> not outlive the device's bound lifetime. Without a lifetime parameter,
> there was no compile-time enforcement that a Coherent or CoherentBox is
> dropped before the device is unbound.
>
> Propagate the new lifetime parameter through all users.
>
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
The rust/kernel code looks good to me. Haven't checked nova part in detail, but
it looks like a mechanical conversion, so would be fine if it builds.
Reviewed-by: Gary Guo <gary@garyguo.net>
Sashiko points out that the `Coherent` could be leaked -- what's the implication
when that happens? I think it's not going to be as problematic like
registrations because coherent allocation carries no callbacks, so we probably
don't need this to be unsafe, but I do wonder how'd DMA subsystem handle this.
Best,
Gary
> ---
> drivers/gpu/nova-core/falcon.rs | 2 +-
> drivers/gpu/nova-core/fb.rs | 2 +-
> drivers/gpu/nova-core/firmware/booter.rs | 2 +-
> drivers/gpu/nova-core/firmware/fsp.rs | 8 +-
> .../nova-core/firmware/fwsec/bootloader.rs | 12 +-
> drivers/gpu/nova-core/firmware/gsp.rs | 14 +-
> drivers/gpu/nova-core/firmware/riscv.rs | 8 +-
> drivers/gpu/nova-core/fsp.rs | 20 +--
> drivers/gpu/nova-core/gpu.rs | 4 +-
> drivers/gpu/nova-core/gsp.rs | 30 ++---
> drivers/gpu/nova-core/gsp/boot.rs | 10 +-
> drivers/gpu/nova-core/gsp/cmdq.rs | 35 +++--
> drivers/gpu/nova-core/gsp/commands.rs | 2 +-
> drivers/gpu/nova-core/gsp/fw.rs | 12 +-
> drivers/gpu/nova-core/gsp/hal.rs | 14 +-
> drivers/gpu/nova-core/gsp/hal/gh100.rs | 16 +--
> drivers/gpu/nova-core/gsp/hal/tu102.rs | 34 ++---
> drivers/gpu/nova-core/gsp/sequencer.rs | 6 +-
> rust/kernel/dma.rs | 121 +++++++++---------
> rust/kernel/uaccess.rs | 4 +-
> samples/rust/rust_dma.rs | 4 +-
> 21 files changed, 176 insertions(+), 184 deletions(-)
next prev parent reply other threads:[~2026-09-03 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 19:37 [PATCH 0/4] rust: dma: tie DMA allocations to the device's bound lifetime Danilo Krummrich
2026-08-30 19:37 ` [PATCH 1/4] rust: debugfs: drop 'static bound from ScopedDir file creation methods Danilo Krummrich
2026-09-03 13:12 ` Gary Guo
2026-09-03 15:07 ` Danilo Krummrich
2026-09-03 15:16 ` Gary Guo
2026-08-30 19:37 ` [PATCH 2/4] rust: dma: tie CoherentHandle to the device's bound lifetime Danilo Krummrich
2026-09-03 13:12 ` Gary Guo
2026-08-30 19:37 ` [PATCH 3/4] samples: rust_dma: separate driver type from driver data Danilo Krummrich
2026-09-03 13:13 ` Gary Guo
2026-08-30 19:37 ` [PATCH 4/4] rust: dma: tie Coherent and CoherentBox to the device's bound lifetime Danilo Krummrich
2026-09-03 13:20 ` Gary Guo [this message]
2026-09-03 15:22 ` Danilo Krummrich
2026-09-03 15:42 ` Gary Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DL5PMZZO1S7X.3BMZVKVUMYVM0@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mmaurer@google.com \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox