summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c
diff options
context:
space:
mode:
authorNitin Gote <nitin.r.gote@intel.com>2024-10-15 17:57:10 +0300
committerAndi Shyti <andi.shyti@linux.intel.com>2024-10-22 12:35:07 +0300
commit6ef0e3ef2662db71d363af77ce31fa940bb7d525 (patch)
tree1299f8a8ee504c2212b59a9cec8dd29bf39d2844 /drivers/gpu/drm/amd/amdgpu/amdgpu_job.c
parente217f22041fe2478e8ab6e4cfa1774089db9a918 (diff)
downloadlinux-6ef0e3ef2662db71d363af77ce31fa940bb7d525.tar.xz
drm/i915/gt: Retry RING_HEAD reset until it get sticks
we see an issue where resets fails because the engine resumes from an incorrect RING_HEAD. Since the RING_HEAD doesn't point to the remaining requests to re-run, but may instead point into the uninitialised portion of the ring, the GPU may be then fed invalid instructions from a privileged context, oft pushing the GPU into an unrecoverable hang. If at first the write doesn't succeed, try, try again. v2: Avoid unnecessary timeout macro (Andi) v3: Correct comment format (Andi) v4: Make it generic for all platform as it won't impact (Chris) Link: https://gitlab.freedesktop.org/drm/intel/-/issues/5432 Testcase: igt/i915_selftest/hangcheck Signed-off-by: Chris Wilson <chris.p.wilson@linux.intel.com> Signed-off-by: Nitin Gote <nitin.r.gote@intel.com> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20241015145710.2478599-1-nitin.r.gote@intel.com
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_job.c')
0 files changed, 0 insertions, 0 deletions