drm/amdgpu: Reset CP_VMID_PREEMPT after trailing fence signaled
authorJiadong Zhu <Jiadong.Zhu@amd.com>
Wed, 24 May 2023 03:42:19 +0000 (11:42 +0800)
committerAlex Deucher <alexander.deucher@amd.com>
Tue, 13 Jun 2023 20:51:05 +0000 (16:51 -0400)
commit1dbcf770cc2d15baf8a1e8174d6fd014a68b45ca
treec35dc479e88f7e695057fe0687ca32f5d1a62861
parent858fd168a95c5b9669aac8db6c14a9aeab446375
drm/amdgpu: Reset CP_VMID_PREEMPT after trailing fence signaled

When MEC executes unmap_queue for mid command buffer preemption, it will
kick the write pointer of the gfx ring, set CP_VMID_PREEMPT to trigger the
preemption and wait for CP_VMID_PREEMPT becomes zero after the preemption
done. There is a race condition that PFP may excute the resetting command
before MEC set CP_VMID_PREEMPT. As a result, hang happens as
CP_VMID_PREEMPT is always 0xffff.

To avoid this, we send resetting CP_VMID_PREEMPT command after the trailing
fence is siganled and update gfx write pointer explicitly.

Signed-off-by: Jiadong Zhu <Jiadong.Zhu@amd.com>
Acked-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org # 6.3.x
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2535
drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c