iris/bufmgr: Add I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS for vram mappable buffers
Signed-off-by: Jordan Justen <jordan.l.justen@intel.com> Reviewed-by: Kenneth Graunke <kenneth@whitecape.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16739>
This commit is contained in:
parent
fae88d8791
commit
ab4939dfff
|
@ -997,11 +997,10 @@ alloc_fresh_bo(struct iris_bufmgr *bufmgr, uint64_t bo_size, unsigned flags)
|
||||||
.extensions = (uintptr_t)&ext_regions,
|
.extensions = (uintptr_t)&ext_regions,
|
||||||
};
|
};
|
||||||
|
|
||||||
/* TODO: Add I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS to create.flags
|
if (!bufmgr->all_vram_mappable &&
|
||||||
* for IRIS_HEAP_DEVICE_LOCAL_PREFERRED when small BAR uapi is
|
bo->real.heap == IRIS_HEAP_DEVICE_LOCAL_PREFERRED) {
|
||||||
* stabilized.
|
create.flags |= I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS;
|
||||||
*/
|
}
|
||||||
assert(bufmgr->all_vram_mappable);
|
|
||||||
|
|
||||||
/* It should be safe to use GEM_CREATE_EXT without checking, since we are
|
/* It should be safe to use GEM_CREATE_EXT without checking, since we are
|
||||||
* in the side of the branch where discrete memory is available. So we
|
* in the side of the branch where discrete memory is available. So we
|
||||||
|
|
Loading…
Reference in New Issue