tu: Avoid extraneous set_iova
The GEM_NEW ccmd already passes the iova, so we don't need an extra SET_IOVA for newly created BOs. Signed-off-by: Rob Clark <robdclark@chromium.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/33433>
This commit is contained in:
parent
081869e591
commit
db88a490b8
1 changed files with 2 additions and 2 deletions
|
|
@ -574,8 +574,6 @@ tu_bo_init(struct tu_device *dev,
|
|||
{
|
||||
assert(dev->physical_device->has_set_iova);
|
||||
|
||||
set_iova(dev, bo->res_id, iova);
|
||||
|
||||
name = tu_debug_bos_add(dev, size, name);
|
||||
|
||||
mtx_lock(&dev->bo_mutex);
|
||||
|
|
@ -835,6 +833,8 @@ virtio_bo_init_dmabuf(struct tu_device *dev,
|
|||
*out_bo = bo;
|
||||
}
|
||||
|
||||
set_iova(dev, bo->res_id, iova);
|
||||
|
||||
out_unlock:
|
||||
mtx_unlock(&dev->vma_mutex);
|
||||
u_rwlock_wrunlock(&dev->dma_bo_lock);
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue