aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
diff options
context:
space:
mode:
authorshaoyunl <[email protected]>2018-10-25 19:40:51 +0000
committerAlex Deucher <[email protected]>2019-05-24 17:21:01 +0000
commite14ba95b908f049dc98915e3452705dec5e506c6 (patch)
tree36d3995012e827d305c7a61d0e12f289e70672df /drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
parentdrm/amdkfd: Preserve ttmp[4:5] instead of ttmp[14:15] (diff)
downloadkernel-e14ba95b908f049dc98915e3452705dec5e506c6.tar.gz
kernel-e14ba95b908f049dc98915e3452705dec5e506c6.zip
drm/amdgpu: Use heavy weight for tlb invalidation on xgmi configuration
There is a bug found in vml2 xgmi logic: mtype is always sent as NC on the VMC to TC interface for a page walk, regardless of whether the request is being sent to local or remote GPU. NC means non-coherent and will cause the VMC return data to be cached in the TCC (versus UC – uncached will not cache the data). Since the page table updates are being done by SDMA/HDP, then TCC will never be updated and the GC VML2 will continue to hit on the TCC and never get the updated page tables and result in a fault. Heave weigh tlb invalidation does a WB/INVAL of the L1/L2 GL data caches so TCC will not be hit on next request Signed-off-by: shaoyunl <[email protected]> Reviewed-by: Felix Kuehling <[email protected]> Signed-off-by: Felix Kuehling <[email protected]> Signed-off-by: Alex Deucher <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c')
0 files changed, 0 insertions, 0 deletions