anv/device: fail to initialize device if we have queues with unsupported flags
This is not strictly necessary since users should not be requesting any flags that are not valid for the list of enabled features requested and we already fail if they attempt to use an unsupported feature, however it is an easy to implement sanity check that would help developes realize that they are doing things wrong, so we might as well do it. Reviewed-by: Jason Ekstrand <jason@jlekstrand.net>
This commit is contained in:
parent
b262f17b15
commit
605fd7c0da
|
@ -1467,6 +1467,15 @@ VkResult anv_CreateDevice(
|
|||
}
|
||||
}
|
||||
|
||||
/* Check requested queues and fail if we are requested to create any
|
||||
* queues with flags we don't support.
|
||||
*/
|
||||
assert(pCreateInfo->queueCreateInfoCount > 0);
|
||||
for (uint32_t i = 0; i < pCreateInfo->queueCreateInfoCount; i++) {
|
||||
if (pCreateInfo->pQueueCreateInfos[i].flags != 0)
|
||||
return vk_error(VK_ERROR_INITIALIZATION_FAILED);
|
||||
}
|
||||
|
||||
/* Check if client specified queue priority. */
|
||||
const VkDeviceQueueGlobalPriorityCreateInfoEXT *queue_priority =
|
||||
vk_find_struct_const(pCreateInfo->pQueueCreateInfos[0].pNext,
|
||||
|
|
Loading…
Reference in New Issue