drm/amdgpu: disable concurrent flushes for Navi10 v2
authorChristian König <christian.koenig@amd.com>
Thu, 7 Feb 2019 11:10:29 +0000 (12:10 +0100)
committerAlex Deucher <alexander.deucher@amd.com>
Fri, 21 Jun 2019 23:58:21 +0000 (18:58 -0500)
Navi10 have a bug in the SDMA which can theoretically cause memory
corruption with concurrent VMID flushes

v2: explicitely check Navi10

Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drivers/gpu/drm/amd/amdgpu/amdgpu_ids.c

index df9b173c3d0b000462ce0731bbe2695c92f35d59..5899d214187bbac7ad4f6ed153439337257e4401 100644 (file)
@@ -364,8 +364,11 @@ static int amdgpu_vmid_grab_used(struct amdgpu_vm *vm,
                if (updates && (!flushed || dma_fence_is_later(updates, flushed)))
                        needs_flush = true;
 
-               /* Concurrent flushes are only possible starting with Vega10 */
-               if (adev->asic_type < CHIP_VEGA10 && needs_flush)
+               /* Concurrent flushes are only possible starting with Vega10 and
+                * are broken on Navi10 and Navi14.
+                */
+               if (needs_flush && (adev->asic_type < CHIP_VEGA10 ||
+                                   adev->asic_type == CHIP_NAVI10))
                        continue;
 
                /* Good, we can use this VMID. Remember this submission as