Searched refs:heaps (Results 1 – 11 of 11) sorted by relevance
/hardware/google/graphics/common/libion/test/ |
D | map_test.cpp | 31 struct ion_heap_data *heap = (struct ion_heap_data *)m_heap_query.heaps; in TEST_F() 58 struct ion_heap_data *heap = (struct ion_heap_data *)m_heap_query.heaps; in TEST_F() 92 struct ion_heap_data *heap = (struct ion_heap_data *)m_heap_query.heaps; in TEST_F() 120 struct ion_heap_data *heap = (struct ion_heap_data *)m_heap_query.heaps; in TEST_F() 162 struct ion_heap_data *heap = (struct ion_heap_data *)m_heap_query.heaps; in TEST_F()
|
D | ion_test_fixture.cpp | 61 query.heaps = reinterpret_cast<__u64>(m_ionHeapData); in SetUp()
|
/hardware/google/graphics/common/libion/ |
D | ion_uapi.h | 98 __u64 heaps; member
|
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
D | VK_EXT_memory_priority.adoc | 19 On some systems with both device-local and non-device-local memory heaps,
|
D | VK_EXT_device_memory_report.adoc | 100 allocations attributed to the corresponding device memory heaps. 104 Drivers can advertise heaps that do not have any corresponding memory types
|
D | VK_EXT_pageable_device_local_memory.adoc | 29 device-local and host-local memory heaps, transparent to the application.
|
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
D | VK_EXT_mutable_descriptor_type.adoc | 110 NOTE: Samplers live in separate heaps in DirectX 12, and do not need to be mutable like this. 181 DirectX 12 descriptor heaps can be specified for general resources containing all types of buffer a…
|
D | VK_EXT_descriptor_buffer.adoc | 631 In DirectX 12 (DX12), descriptors are allocated into descriptor heaps, which work almost completely… 691 … view objects are created in non-shader visible heaps, which are then streamed into shader visible… 695 Descriptor heaps provide methods to query the “start” pointer for the descriptor heap on both the C… 724 …onsists of two operations: setting the descriptor heaps, and setting tables as offsets into those … 1037 Introducing heaps to Vulkan as-is was too complex alongside the other changes in this extension, wh…
|
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/ |
D | memory.adoc | 495 Memory properties of a physical device describe the memory heaps and memory 522 used to access memory allocated from the heaps specified by 532 access memory allocated in those heaps. 538 More than one memory type may: share each heap, and the heaps and memory 543 The number of memory heaps is given by pname:memoryHeapCount and is less 547 The number of memory types available across all memory heaps is given by 555 If there are multiple heaps that all have similar performance 747 [open,refpage='VK_MAX_MEMORY_HEAPS',desc='Length of an array of memory heaps',type='consts'] 750 structures describing memory heaps, as returned in 857 ename:VK_MEMORY_HEAP_SEU_SAFE_BIT is used to denote device memory heaps that [all …]
|
D | fundamentals.adoc | 77 Each device may: advertise one or more heaps, representing different areas 79 Memory heaps are either device-local or host-local, but are always visible 81 Further detail about memory heaps is exposed via memory types available on
|
D | devsandqueues.adoc | 239 capabilities of the system, such as how many memory heaps there are. 2404 pname:heapIndex corresponds to one of the valid heaps from the
|