You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mock_icd needs to report valid limit/feature information for all extensions it reported as supported. Currently mock_icd ignores the pNext chain for vkGetPhysicalDeviceFeatures2KHR where the extension features are queried.
However, when validation support is added for an extension, the features and limits need to be reported back with valid (for example guaranteed minimums given in the spec) values in order for validation to have proper bounds/feature checks and for validation testing to function correctly.
The text was updated successfully, but these errors were encountered:
We didn't quite get the check on whether a format can be legally
queried on a particular GPU quite right. We were checking against
the instance version only. We need to check agains the driver's
supported API version as well.
KarenGhavam-lunarG
changed the title
icd: Add support for vkGetPhysicalDeviceFeatures2KHR pNext extension queries
Mock icd: Add support for vkGetPhysicalDeviceFeatures2KHR pNext extension queries
Dec 20, 2019
If MockICD does need to support the Feature bits in the future, something could be generated to set all VkPhysicalDevice*Features structs' VkBool32 to true, but for now I see no use case to do this in MockICD and not profiles
Issue by jzulauf-lunarg (MIGRATED)
Friday Jan 26, 2018 at 22:40 GMT
Originally opened as KhronosGroup/Vulkan-LoaderAndValidationLayers#2374
The mock_icd needs to report valid limit/feature information for all extensions it reported as supported. Currently mock_icd ignores the pNext chain for vkGetPhysicalDeviceFeatures2KHR where the extension features are queried.
However, when validation support is added for an extension, the features and limits need to be reported back with valid (for example guaranteed minimums given in the spec) values in order for validation to have proper bounds/feature checks and for validation testing to function correctly.
The text was updated successfully, but these errors were encountered: