[PATCH v6 0/3] drm: Create a task info option for wedge events
André Almeida
andrealmeid at igalia.com
Wed May 21 15:33:20 UTC 2025
This patchset implements a request made by Xaver Hugl about wedge events:
"I'd really like to have the PID of the client that triggered the GPU
reset, so that we can kill it if multiple resets are triggered in a
row (or switch to software rendering if it's KWin itself) and show a
user-friendly notification about why their app(s) crashed, but that
can be added later."
>From https://lore.kernel.org/dri-devel/CAFZQkGwJ4qgHV8WTp2=svJ_VXhb-+Y8_VNtKB=jLsk6DqMYp9w@mail.gmail.com/
For testing, I've used amdgpu's debug_mask options debug_disable_soft_recovery
and debug_disable_gpu_ring_reset to test both wedge event paths in the driver.
To trigger a ring timeout, I've used this app:
https://gitlab.freedesktop.org/andrealmeid/gpu-timeout
Thanks!
Changelog:
v6:
- Check if PID >= 0 for displaying the task info
- s/app/task in a comment
v5:
- Change from app to task also in structs, commit message and docs
- Add a check for NULL or empty task name string
v4:
- Change from APP to TASK
- Add defines for event_string and pid_string length
v3:
- Make comm_string and pid_string empty when there's no app info
- Change "app that caused ..." to "app involved ..."
- Clarify that devcoredump have more information about what happened
v2:
- Rebased on top of drm/drm-next
- Added new patch for documentation
André Almeida (3):
drm: Create a task info option for wedge events
drm/doc: Add a section about "Task information" for the wedge API
drm/amdgpu: Make use of drm_wedge_task_info
Documentation/gpu/drm-uapi.rst | 17 +++++++++++++++++
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 19 +++++++++++++++++--
drivers/gpu/drm/amd/amdgpu/amdgpu_job.c | 6 +++++-
drivers/gpu/drm/drm_drv.c | 19 +++++++++++++++----
drivers/gpu/drm/i915/gt/intel_reset.c | 3 ++-
drivers/gpu/drm/xe/xe_device.c | 3 ++-
include/drm/drm_device.h | 8 ++++++++
include/drm/drm_drv.h | 3 ++-
8 files changed, 68 insertions(+), 10 deletions(-)
--
2.49.0
More information about the Intel-gfx
mailing list