summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c
diff options
context:
space:
mode:
authorYunxiang Li <Yunxiang.Li@amd.com>2024-05-24 13:46:50 -0400
committerAlex Deucher <alexander.deucher@amd.com>2024-06-14 16:15:58 -0400
commit1802b042a343c1705e5ef45b93d1fd088344d3c2 (patch)
tree577f416b34904d06092bf872c393b740b3e3f774 /drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c
parent5c0a1cdd17ce9eb315102c65084af899622ed268 (diff)
downloadlinux-1802b042a343c1705e5ef45b93d1fd088344d3c2.tar.gz
linux-1802b042a343c1705e5ef45b93d1fd088344d3c2.tar.bz2
linux-1802b042a343c1705e5ef45b93d1fd088344d3c2.zip
drm/amdgpu/kfd: remove is_hws_hang and is_resetting
is_hws_hang and is_resetting serves pretty much the same purpose and they all duplicates the work of the reset_domain lock, just check that directly instead. This also eliminate a few bugs listed below and get rid of dqm->ops.pre_reset. kfd_hws_hang did not need to avoid scheduling another reset. If the on-going reset decided to skip GPU reset we have a bad time, otherwise the extra reset will get cancelled anyway. remove_queue_mes forgot to check is_resetting flag compared to the pre-MES path unmap_queue_cpsch, so it did not block hw access during reset correctly. Signed-off-by: Yunxiang Li <Yunxiang.Li@amd.com> Reviewed-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_gtt_mgr.c')
0 files changed, 0 insertions, 0 deletions