Instead of abusing the mapping function. Has the clear advantage that unmap_range can't fail with page tables allocation should anything go wrong.
Signed-off-by: Christian König <[email protected]> --- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c index 55bfe4eebc190..bdbd40e29528b 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c @@ -1675,9 +1675,8 @@ int amdgpu_vm_clear_freed(struct amdgpu_device *adev, struct amdgpu_bo_va_mapping, list); list_del(&mapping->list); - r = amdgpu_vm_map_range(adev, vm, true, false, - &sync, mapping->start, mapping->last, - 0, 0, 0, NULL, NULL, NULL, &f); + r = amdgpu_vm_unmap_range(adev, vm, false, &sync, + mapping->start, mapping->last, &f); amdgpu_vm_free_mapping(adev, vm, mapping, f); if (r) { dma_fence_put(f); -- 2.43.0
