drm/radeon: allow move_notify to be called without reservation
The few places that care should have those checks instead. This allows destruction of bo backed memory without a reservation. It's required for being able to rework the delayed destroy path, as it is no longer guaranteed to hold a reservation before unlocking. However any previous wait is still guaranteed to complete, and it's one of the last things to be done before the buffer object is freed. Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
This commit is contained in:

committed by
Dave Airlie

parent
4154f051e7
commit
6ed9ccb412
@@ -1237,7 +1237,6 @@ void radeon_vm_bo_invalidate(struct radeon_device *rdev,
|
||||
{
|
||||
struct radeon_bo_va *bo_va;
|
||||
|
||||
BUG_ON(!radeon_bo_is_reserved(bo));
|
||||
list_for_each_entry(bo_va, &bo->va, bo_list) {
|
||||
bo_va->valid = false;
|
||||
}
|
||||
|
Reference in New Issue
Block a user