Home
last modified time | relevance | path

Searched refs:holes (Results 1 – 5 of 5) sorted by relevance

/hardware/google/gfxstream/guest/mesa/src/util/
Dvma.c38 list_for_each_entry(struct util_vma_hole, _hole, &(_heap)->holes, link)
41 list_for_each_entry_safe(struct util_vma_hole, _hole, &(_heap)->holes, link)
44 list_for_each_entry_safe_rev(struct util_vma_hole, _hole, &(_heap)->holes, link)
50 list_inithead(&heap->holes); in util_vma_heap_init()
81 if (&hole->link == heap->holes.next) { in util_vma_heap_validate()
348 list_add(&hole->link, &heap->holes); in util_vma_heap_free()
Dvma.h37 struct list_head holes; member
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/
Dsparsemem.adoc635 Some implementations require "`holes`" in the device virtual address range
637 These holes may: be included in the pname:size reported for the resource.
639 Including or not including the device virtual address holes in the resource
655 * If the holes are included in the size, this bind function becomes very
662 * If the holes are not included in the size, the application can: allocate
664 However, in this case the implementation must: account for the holes
672 memory for the non-tail mip levels, any holes that are present in the
677 virtual address holes with this operation.
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/
DVK_EXT_mutable_descriptor_type.adoc127 and it is expected that there will be holes in GPU memory between descriptors when smaller descript…
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/
DChangeLog.adoc4280 * Fix some holes in `<<VK_EXT_vertex_input_dynamic_state>>`, including