linux.git/rust/kernel/drm, branch v7.2-rc1

rust/drm/gem: Use DeviceContext with GEM objects

2026-06-02T20:51:16+00:00

Now that we have the ability to represent the context in which a DRM device
is in at compile-time, we can start carrying around this context with GEM
object types in order to allow a driver to safely create GEM objects before
a DRM device has registered with userspace.

Signed-off-by: Lyude Paul 
Reviewed-by: Daniel Almeida 
Link: https://patch.msgid.link/20260507220044.3204919-4-lyude@redhat.com
Signed-off-by: Danilo Krummrich

rust/drm/gem: Add DriverAllocImpl type alias

2026-06-02T20:51:02+00:00

This is just a type alias that resolves into the AllocImpl for a given
T: drm::gem::DriverObject.

Signed-off-by: Lyude Paul 
Reviewed-by: Daniel Almeida 
Link: https://patch.msgid.link/20260507220044.3204919-3-lyude@redhat.com
Signed-off-by: Danilo Krummrich

rust/drm: Introduce DeviceContext

2026-06-02T19:35:25+00:00

One of the tricky things about DRM bindings in Rust is the fact that
initialization of a DRM device is a multi-step process. It's quite normal
for a device driver to start making use of its DRM device for tasks like
creating GEM objects before userspace registration happens. This is an
issue in rust though, since prior to userspace registration the device is
only partly initialized. This means there's a plethora of DRM device
operations we can't yet expose without opening up the door to UB if the DRM
device in question isn't yet registered.

Additionally, this isn't something we can reliably check at runtime. And
even if we could, performing an operation which requires the device be
registered when the device isn't actually registered is a programmer bug,
meaning there's no real way to gracefully handle such a mistake at runtime.
And even if that wasn't the case, it would be horrendously annoying and
noisy to have to check if a device is registered constantly throughout a
driver.

In order to solve this, we first take inspiration from
`kernel::device::DeviceContext` and introduce `kernel::drm::DeviceContext`.
This provides us with a ZST type that we can generalize over to represent
contexts where a device is known to have been registered with userspace at
some point in time (`Registered`), along with contexts where we can't make
such a guarantee (`Uninit`).

It's important to note we intentionally do not provide a `DeviceContext`
which represents an unregistered device. This is because there's no
reasonable way to guarantee that a device with long-living references to
itself will not be registered eventually with userspace. Instead, we
provide a new-type for this: `UnregisteredDevice` which can
provide a guarantee that the `Device` has never been registered with
userspace. To ensure this, we modify `Registration` so that creating a new
`Registration` requires passing ownership of an `UnregisteredDevice`.

Signed-off-by: Lyude Paul 
Reviewed-by: Daniel Almeida 
Link: https://patch.msgid.link/20260507220044.3204919-2-lyude@redhat.com
Signed-off-by: Danilo Krummrich

rust: drm: gem: s/device::Device/Device/ for shmem.rs

2026-06-02T17:16:03+00:00

We're about to start explicitly mentioning kernel devices as well in this
file, so this makes it easier to differentiate the two by allowing us to
import `device` as `kernel::device`.

Signed-off-by: Lyude Paul 
Reviewed-by: Alexandre Courbot 
Reviewed-by: Alice Ryhl 
Link: https://patch.msgid.link/20260428190605.3355690-2-lyude@redhat.com

rust: drm: add FEAT_RENDER flag for render node support

2026-05-28T22:19:04+00:00

Add FEAT_RENDER bool constant to the Driver trait to control
render node support. When enabled, the driver exposes /dev/dri/renderDXX
render nodes to userspace. The flag defaults to false, drivers can opt
in by setting it to true in their Driver implementation.

This is then enabled in the Tyr driver, while it's left disabled for
Nova for the time being.

Co-developed-by: Daniel Almeida 
Signed-off-by: Daniel Almeida 
Reviewed-by: Alice Ryhl 
Signed-off-by: Laura Nao 
Link: https://patch.msgid.link/20260507080914.95478-2-laura.nao@collabora.com
Signed-off-by: Danilo Krummrich

Merge remote-tracking branch 'drm/drm-next' into drm-rust-next

2026-05-28T19:48:11+00:00

Backmerge to pull in commit 838d852da850 ("rust: allow
`clippy::collapsible_match` globally"), in order to get rid of spurious
warnings messing with developer tooling.

Signed-off-by: Danilo Krummrich

drm/gpuvm: rust: add RUST_DRM_GPUVM option to Kconfig

2026-05-05T10:59:41+00:00

Since Rust uses GPUVM via the kernel crate, which is built-in, the GPUVM
module must also be built-in to use GPUVM from Rust. Adjust the Kconfig
settings accordingly.

Suggested-by: Danilo Krummrich 
Signed-off-by: Alice Ryhl 
Link: https://patch.msgid.link/20260427-gpuvm-config-v1-1-8ece03771f8a@google.com
Signed-off-by: Danilo Krummrich

rust: gpuvm: add GpuVmCore::sm_map()

2026-05-05T10:52:49+00:00

Finally also add the operation for creating new mappings. Mapping
operations need extra data in the context since they involve a vm_bo
coming from the outside.

Co-developed-by: Asahi Lina 
Signed-off-by: Asahi Lina 
Reviewed-by: Daniel Almeida 
Signed-off-by: Alice Ryhl 
Link: https://patch.msgid.link/20260409-gpuvm-rust-v6-5-b16e6ada7261@google.com
Signed-off-by: Danilo Krummrich

rust: gpuvm: add GpuVmCore::sm_unmap()

2026-05-05T10:52:49+00:00

Add the entrypoint for unmapping ranges in the GPUVM, and provide
callbacks and VA types for the implementation.

Co-developed-by: Asahi Lina 
Signed-off-by: Asahi Lina 
Reviewed-by: Daniel Almeida 
Signed-off-by: Alice Ryhl 
Link: https://patch.msgid.link/20260409-gpuvm-rust-v6-4-b16e6ada7261@google.com
Signed-off-by: Danilo Krummrich

rust: gpuvm: add GpuVa struct

2026-05-05T10:52:49+00:00

This struct will be used to keep track of individual mapped ranges in
the GPU's virtual memory.

Sparse VAs are not yet supported.

Co-developed-by: Asahi Lina 
Signed-off-by: Asahi Lina 
Co-developed-by: Daniel Almeida 
Signed-off-by: Daniel Almeida 
Reviewed-by: Daniel Almeida 
Signed-off-by: Alice Ryhl 
Link: https://patch.msgid.link/20260409-gpuvm-rust-v6-3-b16e6ada7261@google.com
Signed-off-by: Danilo Krummrich