vulkan: move alignment of host-visible allocations outside of ff_vk_alloc_mem

The issue is that if dedicated allocation is used, VkBufferCreateInfo.size
and the actual allocated size mismatched, which is a validation error.
master
Lynne 2 months ago
parent 3565903c63
commit 9eb7e8d2a4
No known key found for this signature in database
GPG Key ID: A2FEA5F03F034464
  1. 9
      libavutil/vulkan.c

@ -883,10 +883,6 @@ int ff_vk_alloc_mem(FFVulkanContext *s, VkMemoryRequirements *req,
.pNext = alloc_extension,
};
/* Align if we need to */
if ((req_flags != UINT32_MAX) && req_flags & VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT)
req->size = FFALIGN(req->size, s->props.properties.limits.minMemoryMapAlignment);
alloc_info.allocationSize = req->size;
/* The vulkan spec requires memory types to be sorted in the "optimal"
@ -939,8 +935,9 @@ int ff_vk_create_buf(FFVulkanContext *s, FFVkBuffer *buf, size_t size,
.pNext = pNext,
.usage = usage,
.sharingMode = VK_SHARING_MODE_EXCLUSIVE,
.size = size, /* Gets FFALIGNED during alloc if host visible
but should be ok */
.size = flags & VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT ?
FFALIGN(size, s->props.properties.limits.minMemoryMapAlignment) :
size,
};
VkMemoryAllocateFlagsInfo alloc_flags = {

Loading…
Cancel
Save