summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorSunil Khatri <sunil.khatri@amd.com>2026-09-17 18:56:45 +0530
committerAlex Deucher <alexander.deucher@amd.com>2026-09-23 15:53:05 -0400
commitcd195f1616b2bb5fb7765465326c4d5d64a620a0 (patch)
tree3834e1e2847c9184fb8df23916b2a94377c450eb /tools/perf/scripts/python
parent3022bdfe3e6d776e9273d6892f7c193138ca0666 (diff)
downloadlinux-next-cd195f1616b2bb5fb7765465326c4d5d64a620a0.tar.gz
linux-next-cd195f1616b2bb5fb7765465326c4d5d64a620a0.zip
drm/amdgpu/userq: fix double jiffies conversion in hang detect timeout
Function amdgpu_userq_start_hang_detect_work() calls msecs_to_jiffies() on adev->gfx_timeout/compute_timeout/sdma_timeout before arming hang_detect_work. These timeout values already hold jiffies values from amdgpu_device_get_job_timeout_settings() at device init. This silently shrinks the real hang-detect deadline to (2 * HZ) ms instead of the intended timeout. e.g. 500ms instead of the 2000ms default on a CONFIG_HZ=250 kernel, only coincidentally correct at HZ=1000. The shortened window is easily exceeded by ordinary fence-completion latency, causing hang_detect_work to fire and trigger a per-queue or full GPU reset for queues that are not actually hung. Pass the jiffies value directly to queue_delayed_work() instead of converting it a second time. Fixes: fc3336be9c62 ("drm/amd/amdgpu: Add independent hang detect work for user queue fence") Signed-off-by: Sunil Khatri <sunil.khatri@amd.com> Reviewed-by: Christian König <christian.koenig@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> (cherry picked from commit 13d44ca033cb74756c2aef0ade54a75cdf2f6271) Cc: stable@vger.kernel.org
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions