The "moved" VM state is a bit unfortunately named, because BOs can end
up in this state without being physically moved. While we need to
invalidate every mapping when BOs are physically moved, in some other
cases like PRT binds/unbinds there is no need to refresh mappings except
those affected by the bind.
Full invalidation of all BO mappings manifested as severe regressions in
PRT bind performance, which this patch fixes. The offending patch is
4cdbba5a16aa ("drm/amdgpu: restructure VM state machine v4") in the
amd-staging-drm-next tree, although it has not yet propagated anywhere
else.
Fixes: 4cdbba5a16aa ("drm/amdgpu: restructure VM state machine v4")
Closes: https://gitlab.freedesktop.org/drm/amd/-/work_items/5437
Signed-off-by: Natalie Vock <natalie.vock@gmx.de>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
(cherry picked from commit
0b2fa33b4235991a100dd799c891cf5c242aaed1)
Cc: stable@vger.kernel.org
vm_bo->moved = false;
list_move(&vm_bo->vm_status, &lists->idle);
} else {
- vm_bo->moved = true;
list_move(&vm_bo->vm_status, &lists->moved);
}
amdgpu_vm_bo_unlock_lists(vm_bo);
return r;
vm->update_funcs->map_table(to_amdgpu_bo_vm(bo_base->bo));
+ bo_base->moved = true;
amdgpu_vm_bo_moved(bo_base);
}
if (r)
return r;
+ bo_base->moved = true;
amdgpu_vm_bo_moved(bo_base);
}
if (r)
return r;
+ bo_base->moved = true;
amdgpu_vm_bo_moved(bo_base);
/* It's a bit inefficient to always jump back to the start, but
if (bo_base->moved)
continue;
+ bo_base->moved = true;
amdgpu_vm_bo_moved(bo_base);
}
}