Previous version of this patch series:
https://patchwork.freedesktop.org/series/160217/#rev5
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.
Series-wide changes
V2:
* s/DeviceCtx/DeviceContext/ for consistency
* Move private driver-data availability to the Registration
DeviceContext
* s/AnyCtx/Init/
V4:
* Split out DriverAllocImpl into it's own patch
V6:
* Rebase
More changes described in each patch description.
Lyude Paul (3):
rust/drm: Introduce DeviceContext
rust/drm/gem: Add DriverAllocImpl type alias
rust/drm/gem: Use DeviceContext with GEM objects
drivers/gpu/drm/nova/driver.rs | 10 +-
drivers/gpu/drm/nova/gem.rs | 15 ++-
drivers/gpu/drm/tyr/driver.rs | 12 +-
drivers/gpu/drm/tyr/gem.rs | 11 +-
rust/kernel/drm/device.rs | 240 +++++++++++++++++++++++++--------
rust/kernel/drm/driver.rs | 37 +++--
rust/kernel/drm/gem/mod.rs | 72 +++++++---
rust/kernel/drm/gem/shmem.rs | 57 ++++----
rust/kernel/drm/mod.rs | 4 +
9 files changed, 333 insertions(+), 125 deletions(-)
base-commit: 37f748ed0c19e007e7c5677f5d605d6b93841792
--
2.54.0