summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c
diff options
context:
space:
mode:
authorshaoyunl <Shaoyun.Liu@amd.com>2018-10-25 15:40:51 -0400
committerAlex Deucher <alexander.deucher@amd.com>2019-05-24 12:21:01 -0500
commite14ba95b908f049dc98915e3452705dec5e506c6 (patch)
tree36d3995012e827d305c7a61d0e12f289e70672df /drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c
parentfa722f0d9820a84952a3cbaccb888c31f9bfca2a (diff)
downloadlinux-e14ba95b908f049dc98915e3452705dec5e506c6.tar.bz2
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 <Shaoyun.Liu@amd.com> Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com> Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c')
0 files changed, 0 insertions, 0 deletions