| /device/generic/vulkan-cereal/third-party/angle/src/common/ |
| D | PoolAlloc_unittest.cpp | 23 void *allocation = poolAllocator.allocate(numBytes); in TEST() local
25 EXPECT_NE(nullptr, allocation); in TEST()
27 uint32_t *writePtr = static_cast<uint32_t *>(allocation); in TEST()
31 allocation = poolAllocator.allocate(numBytes); in TEST()
32 EXPECT_NE(nullptr, allocation); in TEST()
34 allocation = poolAllocator.allocate(10 * 1024); in TEST()
43 allocation = poolAllocator.allocate(numBytes); in TEST()
44 EXPECT_NE(nullptr, allocation); in TEST()
47 memset(allocation, 0xb8, numBytes); in TEST()
67 void *allocation = poolAllocator.allocate((rand() % (1024 * 4)) + 1); in TEST_P() local
[all …]
|
| /device/generic/vulkan-cereal/third-party/angle/src/libANGLE/renderer/vulkan/ |
| D | vk_mem_alloc_wrapper.cpp | 67 void FreeMemory(VmaAllocator allocator, VmaAllocation allocation) in FreeMemory() argument
69 vmaFreeMemory(allocator, allocation); in FreeMemory()
118 VkResult MapMemory(VmaAllocator allocator, VmaAllocation allocation, void **ppData) in MapMemory() argument
120 return vmaMapMemory(allocator, allocation, ppData); in MapMemory()
123 void UnmapMemory(VmaAllocator allocator, VmaAllocation allocation) in UnmapMemory() argument
125 return vmaUnmapMemory(allocator, allocation); in UnmapMemory()
129 VmaAllocation allocation, in FlushAllocation() argument
133 vmaFlushAllocation(allocator, allocation, offset, size); in FlushAllocation()
137 VmaAllocation allocation, in InvalidateAllocation() argument
141 vmaInvalidateAllocation(allocator, allocation, offset, size); in InvalidateAllocation()
|
| D | vk_mem_alloc_wrapper.h | 28 void FreeMemory(VmaAllocator allocator, VmaAllocation allocation); in VK_DEFINE_HANDLE()
50 VkResult MapMemory(VmaAllocator allocator, VmaAllocation allocation, void **ppData); in VK_DEFINE_HANDLE()
52 void UnmapMemory(VmaAllocator allocator, VmaAllocation allocation); in VK_DEFINE_HANDLE()
55 VmaAllocation allocation, in VK_DEFINE_HANDLE()
60 VmaAllocation allocation, in VK_DEFINE_HANDLE()
|
| D | vk_utils.cpp | 447 Allocation *allocation, in InitMappableAllocation() argument
453 allocation->map(allocator, &mapPointer); in InitMappableAllocation()
458 allocation->flush(allocator, 0, size); in InitMappableAllocation()
461 allocation->unmap(allocator); in InitMappableAllocation()
|
| /device/generic/vulkan-cereal/protocols/vulkan/appendices/ |
| D | VK_KHR_dedicated_allocation.txt | 21 This extension enables resources to be bound to a dedicated allocation,
24 allocation is recommended, in which case using a dedicated allocation may:
27 allocation, memory aliasing and sparse binding, which could interfere with
29 Applications should query the implementation for when a dedicated allocation
39 and memory allocation: a new structure that flags whether an image/buffer
40 should have a dedicated allocation, and a structure indicating the image or
41 buffer that an allocation will be bound to.
57 // Create an image with a dedicated allocation based on the
131 // Take the normal memory sub-allocation path
|
| D | VK_EXT_external_memory_host.txt | 36 heap that is otherwise not usable for regular memory object allocation and
39 2) Can the application still access the contents of the host allocation
45 3) Can the application free the host allocation?
48 Using the memory object imported from a host allocation that is already
58 allocation, although the same physical pages will be used.
68 6) Can the same host allocation be imported multiple times into a given
|
| D | VK_EXT_device_memory_report.txt | 44 2) Can we extend and use the existing internal allocation callbacks instead
88 allocation reporting design (which is essentially what this extension is
125 along with a dlink:VK_NULL_HANDLE for this bulk allocation.
126 Instead, this bulk allocation is considered as a layer below what this
129 from the bulk allocation, we ask the implementation to report the valid
144 7) Should we add an additional "`allocation failed`" event type with things
153 Right now the allocation failure could have happened anywhere during
|
| D | VK_NV_dedicated_allocation.txt | 29 allocation: a new structure that flags whether am image/buffer will have a
30 dedicated allocation, and a structure indicating the image or buffer that an
31 allocation will be bound to.
|
| D | VK_KHR_maintenance3.txt | 27 * A limit on the maximum size of a single memory allocation.
29 allocation.
|
| D | VK_EXT_global_priority.txt | 28 The driver implementation will attempt to skew hardware resource allocation
44 The driver implementation may fail the queue allocation request if resources
|
| D | VK_EXT_pageable_device_local_memory.txt | 37 at the time memory consumption was queried, and a device-local allocation
46 memory and the application should adjust its memory allocation strategy
|
| D | VK_ANDROID_external_memory_android_hardware_buffer.txt | 62 allocation size reported by flink:vkGetImageMemoryRequirements to be
65 *RESOLVED*: Allow the allocation size to be unspecified when allocating the
68 basetype:AHardwareBuffer allocation happens in flink:vkAllocateMemory, and
|
| D | VK_EXT_image_drm_format_modifier.txt | 293 - *Undedicated allocation by default.* When importing or exporting a set
306 - *Separation of image creation and memory allocation.* When importing a
311 In Vulkan, image creation and memory allocation are independent unless a
312 dedicated allocation is used (as in `VK_KHR_dedicated_allocation`).
313 Therefore, without requiring dedicated allocation, Vulkan cannot query
316 Even if dedication allocation were required, Vulkan cannot calculate the
|
| D | VK_NV_dedicated_allocation_image_aliasing.txt | 22 image for which the allocation was created, and every other image parameter
|
| D | VK_EXT_memory_priority.txt | 17 This extension adds a pname:priority value specified at memory allocation
|
| /device/generic/vulkan-cereal/protocols/vulkan/chapters/ |
| D | memory.txt | 25 [[memory-allocation]]
34 memory allocation logging.
36 …backs',desc='Structure containing callback function pointers for memory allocation',type='structs']
51 application-defined memory allocation function.
83 [open,refpage='PFN_vkAllocationFunction',desc='Application-defined memory allocation function',type…
92 * pname:size is the size in bytes of the requested allocation.
93 * pname:alignment is the requested alignment of the allocation in bytes
96 specifying the allocation scope of the lifetime of the allocation, as
97 described <<memory-host-allocation-scope,here>>.
102 If the allocation was successful, it must: return a valid pointer to memory
[all …]
|
| D | VK_EXT_private_data.txt | 40 * pname:pAllocator controls host memory allocation as described in the
41 <<memory-allocation, Memory Allocation>> chapter.
90 * pname:pAllocator controls host memory allocation as described in the
91 <<memory-allocation, Memory Allocation>> chapter.
|
| D | VK_EXT_debug_report.txt | 32 * pname:pAllocator controls host memory allocation as described in the
33 <<memory-allocation, Memory Allocation>> chapter.
283 * pname:pAllocator controls host memory allocation as described in the
284 <<memory-allocation, Memory Allocation>> chapter.
|
| D | initialization.txt | 231 ename:VK_ERROR_OUT_OF_HOST_MEMORY in the case of a failed memory allocation.
246 * pname:pAllocator controls host memory allocation as described in the
247 <<memory-allocation, Memory Allocation>> chapter.
487 * pname:pAllocator controls host memory allocation as described in the
488 <<memory-allocation, Memory Allocation>> chapter.
|
| /device/generic/vulkan-cereal/protocols/vulkan/chapters/commonvalidity/ |
| D | bind_image_common.txt | 16 If pname:image requires a dedicated allocation (as reported by
33 If the <<features-dedicatedAllocationImageAliasing,dedicated allocation
42 If the <<features-dedicatedAllocationImageAliasing,dedicated allocation
54 original image for which the allocation was created; and the
56 or smaller than the original image for which the allocation was created
|
| /device/generic/vulkan-cereal/protocols/vulkan/chapters/VK_EXT_display_control/ |
| D | fence_events.txt | 21 * pname:pAllocator controls host memory allocation as described in the
22 <<memory-allocation, Memory Allocation>> chapter.
69 * pname:pAllocator controls host memory allocation as described in the
70 <<memory-allocation, Memory Allocation>> chapter.
|
| /device/generic/vulkan-cereal/protocols/vulkan/chapters/VK_NVX_device_generated_commands/ |
| D | objecttable.txt | 38 * pname:pAllocator controls host memory allocation as described in the
39 <<memory-allocation, Memory Allocation>> chapter.
172 * pname:pAllocator controls host memory allocation as described in the
173 <<memory-allocation, Memory Allocation>> chapter.
|
| D | indirectcommands.txt | 238 * pname:pAllocator controls host memory allocation as described in the
239 <<memory-allocation, Memory Allocation>> chapter.
359 * pname:pAllocator controls host memory allocation as described in the
360 <<memory-allocation, Memory Allocation>> chapter.
|
| /device/generic/vulkan-cereal/protocols/vulkan/chapters/VK_KHR_deferred_host_operations/ |
| D | deferred_host_operations.txt | 102 * pname:pAllocator controls host memory allocation as described in the
103 <<memory-allocation,Memory Allocation>> chapter.
175 * pname:pAllocator controls host memory allocation as described in the
176 <<memory-allocation,Memory Allocation>> chapter.
|
| /device/generic/vulkan-cereal/protocols/vulkan/chapters/VK_NV_external_memory/ |
| D | allocate_memory.txt | 22 Multiple handle types may: be requested for the same allocation as long
|