aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915/gt/uc/selftest_guc_multi_lrc.c
diff options
context:
space:
mode:
authorLucas Stach <l.stach@pengutronix.de>2021-12-22 01:17:28 +0100
committerLucas Stach <l.stach@pengutronix.de>2021-12-23 20:21:33 +0100
commitcdd156955f946beaa5f3a00d8ccf90e5a197becc (patch)
tree638df9e2b7ba10dbae634dc4c29779631f469ba1 /drivers/gpu/drm/i915/gt/uc/selftest_guc_multi_lrc.c
parentdrm/etnaviv: limit submit sizes (diff)
downloadlinux-dev-cdd156955f946beaa5f3a00d8ccf90e5a197becc.tar.xz
linux-dev-cdd156955f946beaa5f3a00d8ccf90e5a197becc.zip
drm/etnaviv: consider completed fence seqno in hang check
Some GPU heavy test programs manage to trigger the hangcheck quite often. If there are no other GPU users in the system and the test program exhibits a very regular structure in the commandstreams that are being submitted, we can end up with two distinct submits managing to trigger the hangcheck with the FE in a very similar address range. This leads the hangcheck to believe that the GPU is stuck, while in reality the GPU is already busy working on a different job. To avoid those spurious GPU resets, also remember and consider the last completed fence seqno in the hang check. Reported-by: Joerg Albert <joerg.albert@iav.de> Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
Diffstat (limited to 'drivers/gpu/drm/i915/gt/uc/selftest_guc_multi_lrc.c')
0 files changed, 0 insertions, 0 deletions