drm/amdkfd: Fix and simplify sync object handling for KFD
authorFelix Kuehling <Felix.Kuehling@amd.com>
Tue, 13 Mar 2018 20:05:59 +0000 (16:05 -0400)
committerAlex Deucher <alexander.deucher@amd.com>
Tue, 20 Nov 2018 19:01:05 +0000 (14:01 -0500)
commit5aae7335b1ee609da13e5c9fa535802654171e10
tree24be45b6686f03ffb398683043e7212fad3d5959
parent3d97da4463d87148269a087c26422a2a5304d5d3
drm/amdkfd: Fix and simplify sync object handling for KFD

The adev parameter in amdgpu_sync_fence and amdgpu_sync_resv is only
needed for updating sync->last_vm_update. This breaks if different
adevs are passed to calls for the same sync object.

Always pass NULL for calls from KFD because sync objects used for
KFD don't belong to any particular device, and KFD doesn't need the
sync->last_vm_update fence.

This fixes kernel log warnings on multi-GPU systems after recent
changes in amdgpu_amdkfd_gpuvm_restore_process_bos.

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