summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorAnna Maniscalco <anna.maniscalco2000@gmail.com>2026-02-10 17:29:42 +0100
committerRob Clark <robin.clark@oss.qualcomm.com>2026-03-31 13:47:27 -0700
commit01a0d6cd7032e9993feea19fadb03ef9d5b488f2 (patch)
tree15213198329f772750e772e274888bd24c1802ee /tools/perf/scripts/python
parent6a0b843a16751e3b1ebac794984d4e48384f9078 (diff)
drm/msm: always recover the gpu
Previously, in case there was no more work to do, recover worker wouldn't trigger recovery and would instead rely on the gpu going to sleep and then resuming when more work is submitted. Recover_worker will first increment the fence of the hung ring so, if there's only one job submitted to a ring and that causes an hang, it will early out. There's no guarantee that the gpu will suspend and resume before more work is submitted and if the gpu is in a hung state it will stay in that state and probably trigger a timeout again. Just stop checking and always recover the gpu. Signed-off-by: Anna Maniscalco <anna.maniscalco2000@gmail.com> Cc: stable@vger.kernel.org Patchwork: https://patchwork.freedesktop.org/patch/704066/ Message-ID: <20260210-recovery_suspend_fix-v1-1-00ed9013da04@gmail.com> Signed-off-by: Rob Clark <robin.clark@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions