This follow-up series wires existing GPU event sources into the
render-node EVENTFD subscription infrastructure.

The EVENTFD infrastructure and subscription handling are provided by the
base series:
https://patchwork.freedesktop.org/series/164618/#rev7

This series adds the event producer side by reusing existing code paths
that already detect these conditions and notifying the matching EVENTFD
subscribers.

The events wired up are:

USERQ_EOP
QUEUE_RESET
MEMORY_EXCEPTION
SCRATCH
GPU_RESET

USERQ_EOP, QUEUE_RESET, and SCRATCH are queue-scoped and use the
affected queue object for signaling.

MEMORY_EXCEPTION and GPU_RESET are GPU-scoped and do not use queue
objects. All subscribers associated with the device are notified.

EVENTFD remains notification-only and does not carry event payloads.

Compile-tested only.

Srinivasan Shanmugam (5):
  drm/amdgpu/gfx11: Signal USERQ_EOP EVENTFD notifications
  drm/amdgpu: Signal QUEUE_RESET EVENTFD notifications
  drm/amdgpu: Signal SCRATCH EVENTFD notifications
  drm/amdgpu/gmc11: Signal MEMORY_EXCEPTION EVENTFD notifications
  drm/amdgpu: Signal GPU_RESET EVENTFD notifications

 drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 30 +++++++++++++++++++++-
 drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c  |  9 ++++++-
 drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c     | 15 +++++++++++
 drivers/gpu/drm/amd/amdgpu/gmc_v11_0.c     | 14 ++++++++++
 drivers/gpu/drm/amd/amdgpu/mes_userqueue.c |  9 +++++++
 5 files changed, 75 insertions(+), 2 deletions(-)


base-commit: 43b7fade995f082c15e0c0935d14aecba3e50356
-- 
2.34.1

Reply via email to