mirror of
https://github.com/torvalds/linux.git
synced 2026-05-12 16:18:45 +02:00
rust: drm: dispatch work items to the private data
This implementation dispatches any work enqueued on ARef<drm::Device<T>> to
its driver-provided handler. It does so by building upon the newly-added
ARef<T> support in workqueue.rs in order to call into the driver
implementations for work_container_of and raw_get_work.
This is notably important for work items that need access to the drm
device, as it was not possible to enqueue work on a ARef<drm::Device<T>>
previously without failing the orphan rule.
The current implementation needs T::Data to live inline with drm::Device in
order for work_container_of to function. This restriction is already
captured by the trait bounds. Drivers that need to share their ownership of
T::Data may trivially get around this:
// Lives inline in drm::Device
struct DataWrapper {
work: ...,
// Heap-allocated, shared ownership.
data: Arc<DriverData>,
}
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
Acked-by: Danilo Krummrich <dakr@kernel.org>
Signed-off-by: Daniel Almeida <daniel.almeida@collabora.com>
Link: https://lore.kernel.org/r/20260323-aref-workitem-v3-2-f59729b812aa@collabora.com
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
This commit is contained in:
parent
f5e841e496
commit
72a723df8d
|
|
@ -6,8 +6,7 @@
|
|||
|
||||
use crate::{
|
||||
alloc::allocator::Kmalloc,
|
||||
bindings,
|
||||
device,
|
||||
bindings, device,
|
||||
drm::{
|
||||
self,
|
||||
driver::AllocImpl, //
|
||||
|
|
@ -18,7 +17,12 @@
|
|||
ARef,
|
||||
AlwaysRefCounted, //
|
||||
},
|
||||
types::Opaque, //
|
||||
types::Opaque,
|
||||
workqueue::{
|
||||
HasWork,
|
||||
Work,
|
||||
WorkItem, //
|
||||
},
|
||||
};
|
||||
use core::{
|
||||
alloc::Layout,
|
||||
|
|
@ -241,3 +245,49 @@ unsafe impl<T: drm::Driver> Send for Device<T> {}
|
|||
// SAFETY: A `drm::Device` can be shared among threads because all immutable methods are protected
|
||||
// by the synchronization in `struct drm_device`.
|
||||
unsafe impl<T: drm::Driver> Sync for Device<T> {}
|
||||
|
||||
impl<T, const ID: u64> WorkItem<ID> for Device<T>
|
||||
where
|
||||
T: drm::Driver,
|
||||
T::Data: WorkItem<ID, Pointer = ARef<Device<T>>>,
|
||||
T::Data: HasWork<Device<T>, ID>,
|
||||
{
|
||||
type Pointer = ARef<Device<T>>;
|
||||
|
||||
fn run(ptr: ARef<Device<T>>) {
|
||||
T::Data::run(ptr);
|
||||
}
|
||||
}
|
||||
|
||||
// SAFETY:
|
||||
//
|
||||
// - `raw_get_work` and `work_container_of` return valid pointers by relying on
|
||||
// `T::Data::raw_get_work` and `container_of`. In particular, `T::Data` is
|
||||
// stored inline in `drm::Device`, so the `container_of` call is valid.
|
||||
//
|
||||
// - The two methods are true inverses of each other: given `ptr: *mut
|
||||
// Device<T>`, `raw_get_work` will return a `*mut Work<Device<T>, ID>` through
|
||||
// `T::Data::raw_get_work` and given a `ptr: *mut Work<Device<T>, ID>`,
|
||||
// `work_container_of` will return a `*mut Device<T>` through `container_of`.
|
||||
unsafe impl<T, const ID: u64> HasWork<Device<T>, ID> for Device<T>
|
||||
where
|
||||
T: drm::Driver,
|
||||
T::Data: HasWork<Device<T>, ID>,
|
||||
{
|
||||
unsafe fn raw_get_work(ptr: *mut Self) -> *mut Work<Device<T>, ID> {
|
||||
// SAFETY: The caller promises that `ptr` points to a valid `Device<T>`.
|
||||
let data_ptr = unsafe { &raw mut (*ptr).data };
|
||||
|
||||
// SAFETY: `data_ptr` is a valid pointer to `T::Data`.
|
||||
unsafe { T::Data::raw_get_work(data_ptr) }
|
||||
}
|
||||
|
||||
unsafe fn work_container_of(ptr: *mut Work<Device<T>, ID>) -> *mut Self {
|
||||
// SAFETY: The caller promises that `ptr` points at a `Work` field in
|
||||
// `T::Data`.
|
||||
let data_ptr = unsafe { T::Data::work_container_of(ptr) };
|
||||
|
||||
// SAFETY: `T::Data` is stored as the `data` field in `Device<T>`.
|
||||
unsafe { crate::container_of!(data_ptr, Self, data) }
|
||||
}
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user