summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/amd/amdkfd/kfd_mqd_manager_vi.c
diff options
context:
space:
mode:
authorFelix Kuehling <Felix.Kuehling@amd.com>2018-03-23 22:32:30 +0300
committerOded Gabbay <oded.gabbay@gmail.com>2018-03-23 22:32:30 +0300
commit6e08e0995b8f339fd2a7ee4fa11f17396405ef60 (patch)
tree629fb974b4420f93208988205bd455966e342341 /drivers/gpu/drm/amd/amdkfd/kfd_mqd_manager_vi.c
parent0919195f2b0d7437cb0de49b8975fdd7b5575490 (diff)
downloadlinux-6e08e0995b8f339fd2a7ee4fa11f17396405ef60.tar.xz
drm/amdgpu: Avoid reclaim while holding locks taken in MMU notifier
When an MMU notifier runs in memory reclaim context, it can deadlock trying to take locks that are already held in the thread causing the memory reclaim. The solution is to avoid memory reclaim while holding locks that are taken in MMU notifiers. This commit fixes kmalloc while holding rmn->lock by moving the call outside the lock. The GFX MMU notifier also locks reservation objects. I have no good solution for avoiding reclaim while holding reservation objects. The HSA MMU notifier will not lock any reservation objects. v2: Moved allocation outside lock instead of using GFP_NOIO Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com> Acked-by: Oded Gabbay <oded.gabbay@gmail.com> Reviewed-by: Christian König <christian.koenig@amd.com> Signed-off-by: Oded Gabbay <oded.gabbay@gmail.com>
Diffstat (limited to 'drivers/gpu/drm/amd/amdkfd/kfd_mqd_manager_vi.c')
0 files changed, 0 insertions, 0 deletions