From: André Almeida Date: Tue, 17 Jun 2025 12:49:47 +0000 (-0300) Subject: drm/doc: Add a section about "Task information" for the wedge API X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=cd37124b40934377d7ccdcc1bb22c8a880b516db;p=thirdparty%2Fkernel%2Flinux.git drm/doc: Add a section about "Task information" for the wedge API Add a section about "Task information" for the wedge API. Reviewed-by: Krzysztof Karas Reviewed-by: Raag Jadav Reviewed-by: Christian König Link: https://lore.kernel.org/r/20250617124949.2151549-5-andrealmeid@igalia.com Signed-off-by: André Almeida --- diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst index 4863a4deb0ee5..263e5a97c0807 100644 --- a/Documentation/gpu/drm-uapi.rst +++ b/Documentation/gpu/drm-uapi.rst @@ -446,6 +446,23 @@ telemetry information (devcoredump, syslog). This is useful because the first hang is usually the most critical one which can result in consequential hangs or complete wedging. +Task information +--------------- + +The information about which application (if any) was involved in the device +wedging is useful for userspace if they want to notify the user about what +happened (e.g. the compositor display a message to the user "The +caused a graphical error and the system recovered") or to implement policies +(e.g. the daemon may "ban" an task that keeps resetting the device). If the task +information is available, the uevent will display as ``PID=`` and +``TASK=``. Otherwise, ``PID`` and ``TASK`` will not appear in the +event string. + +The reliability of this information is driver and hardware specific, and should +be taken with a caution regarding it's precision. To have a big picture of what +really happened, the devcoredump file provides should have much more detailed +information about the device state and about the event. + Consumer prerequisites ----------------------