anv: Implement VK_KHR_dedicated_allocation

We always recommend sub-allocation and don't do anything special for
dedicated allocations.

Reviewed-by: Samuel Iglesias Gonsálvez <siglesias@igalia.com>
Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
This commit is contained in:
Jason Ekstrand 2017-04-28 05:17:38 -07:00
parent 8c82aa5f43
commit c02da9cad6
2 changed files with 19 additions and 0 deletions

View File

@ -440,6 +440,10 @@ static const VkExtensionProperties global_extensions[] = {
};
static const VkExtensionProperties device_extensions[] = {
{
.extensionName = VK_KHR_DEDICATED_ALLOCATION_EXTENSION_NAME,
.specVersion = 1,
},
{
.extensionName = VK_KHR_DESCRIPTOR_UPDATE_TEMPLATE_EXTENSION_NAME,
.specVersion = 1,
@ -1748,6 +1752,13 @@ void anv_GetBufferMemoryRequirements2KHR(
vk_foreach_struct(ext, pMemoryRequirements->pNext) {
switch (ext->sType) {
case VK_STRUCTURE_TYPE_MEMORY_DEDICATED_REQUIREMENTS_KHR: {
VkMemoryDedicatedRequirementsKHR *requirements = (void *)ext;
requirements->prefersDedicatedAllocation = VK_FALSE;
requirements->requiresDedicatedAllocation = VK_FALSE;
break;
}
default:
anv_debug_ignored_stype(ext->sType);
break;
@ -1790,6 +1801,13 @@ void anv_GetImageMemoryRequirements2KHR(
vk_foreach_struct(ext, pMemoryRequirements->pNext) {
switch (ext->sType) {
case VK_STRUCTURE_TYPE_MEMORY_DEDICATED_REQUIREMENTS_KHR: {
VkMemoryDedicatedRequirementsKHR *requirements = (void *)ext;
requirements->prefersDedicatedAllocation = VK_FALSE;
requirements->requiresDedicatedAllocation = VK_FALSE;
break;
}
default:
anv_debug_ignored_stype(ext->sType);
break;

View File

@ -33,6 +33,7 @@ from mako.template import Template
MAX_API_VERSION = 1.0
SUPPORTED_EXTENSIONS = [
'VK_KHR_dedicated_allocation',
'VK_KHR_descriptor_update_template',
'VK_KHR_get_memory_requirements2',
'VK_KHR_get_physical_device_properties2',