Previous version of this patch series:
  https://patchwork.freedesktop.org/series/160217/#rev2

One of the unsolved issues we still have with the rust DRM bindings is
the ability to limit certain Device operations to contexts where we can
guarantee that a Device has been fully initialized and registered with
userspace, or vice-versa (e.g. must be unregistered).

While the previous solution for this that I had was simply not exposing
drm::Device at all until the device has been registered with userspace,
unfortunately this isn't enough since:

* As we found out with Tyr, drivers occasionally need to be able to
  create GEM objects before device registration
* We would still need to be able to handle KMS callbacks which could be
  invoked after KMS init but before userspace registration (not handled
  in this series specifically, but DeviceContext will be required for
  handling this).

This patch series provides a pretty nice solution to this, by
implementing a very similar solution to kernel::device::DeviceContext:
introducing our own DeviceContext type state.

This patch series depends on the two pre-requisite patch series:

* https://patchwork.freedesktop.org/series/160523/

                          Series-wide changes

V2:
* s/DeviceCtx/DeviceContext/ for consistency
* Move private driver-data availability to the Registration
  DeviceContext
* s/AnyCtx/Init/

More changes described in each patch description.

Lyude Paul (3):
  rust/drm: Introduce DeviceContext
  rust/drm: Don't setup private driver data until registration
  rust/drm/gem: Use DeviceContext with GEM objects

 drivers/gpu/drm/nova/driver.rs |  10 +-
 drivers/gpu/drm/nova/gem.rs    |  11 +-
 drivers/gpu/drm/tyr/driver.rs  |  12 +-
 drivers/gpu/drm/tyr/gem.rs     |   3 +-
 rust/kernel/drm/device.rs      | 250 +++++++++++++++++++++++++--------
 rust/kernel/drm/driver.rs      |  52 +++++--
 rust/kernel/drm/gem/mod.rs     |  64 ++++++---
 rust/kernel/drm/mod.rs         |   4 +
 8 files changed, 305 insertions(+), 101 deletions(-)


base-commit: 5ec66bbc74883b73d169ceb25dcb7a5cb22e275b
prerequisite-patch-id: ddb20be75c8fc92ba2d48a5c4aa8e724202de1ff
prerequisite-patch-id: 87e69cd89a806392d3275b19fbfb160d44d957c9
-- 
2.52.0

Hi Lyude,

> On 24 Jan 2026, at 00:10, Lyude Paul <lyude@redhat.com> wrote:
> 
> Previous version of this patch series:
>  https://patchwork.freedesktop.org/series/160217/#rev2
> 
> One of the unsolved issues we still have with the rust DRM bindings is
> the ability to limit certain Device operations to contexts where we can
> guarantee that a Device has been fully initialized and registered with
> userspace, or vice-versa (e.g. must be unregistered).
> 
> While the previous solution for this that I had was simply not exposing
> drm::Device at all until the device has been registered with userspace,
> unfortunately this isn't enough since:
> 
> * As we found out with Tyr, drivers occasionally need to be able to
>  create GEM objects before device registration
> * We would still need to be able to handle KMS callbacks which could be
>  invoked after KMS init but before userspace registration (not handled
>  in this series specifically, but DeviceContext will be required for
>  handling this).
> 
> This patch series provides a pretty nice solution to this, by
> implementing a very similar solution to kernel::device::DeviceContext:
> introducing our own DeviceContext type state.
> 
> This patch series depends on the two pre-requisite patch series:
> 
> * https://patchwork.freedesktop.org/series/160523/
> 
>                          Series-wide changes
> 
> V2:
> * s/DeviceCtx/DeviceContext/ for consistency
> * Move private driver-data availability to the Registration
>  DeviceContext
> * s/AnyCtx/Init/
> 

Did you forget the changelog for v3 and v4?


> More changes described in each patch description.

Seems to be the case for the individual patches as well.

Anyways, I will do a second round of reviews here; please
wait a bit before potentially merging a new iteration.


— Daniel