-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add VUID 01778 #2089
Add VUID 01778 #2089
Conversation
Validade implied image creation parameters of VkSwapchainCreateInfoKHR: The implied image creation parameters of the swapchain must be supported as reported by vkGetPhysicalDeviceImageFormatProperties
Check validation of implied image creation parameters of VkSwapchainCreateInfoKHR, by providing parameters that are confirmed to fail vkGetPhysicalDeviceImageFormatProperties function
Running through CI. |
Looks great, thanks! |
These two commits caused crashes on some android devices. This was missed due to a CI glitch, and these two commits have been temporarily reverted until we can get this sorted out. Sorry for the churn. |
Oh thanks for the info. Could you please share details of crash, when you'll have them? |
@evgenKh, determined that it is the test commit that causes the crashes, but not in your test. The test framework for Android is a bit unique as it doesn't do a complete teardown between tests. So even though this test passes nicely, some side-effect it has causes the Here's the Galaxy logcat info, which looks pretty much the same as the NexusPlayer stack:
|
Found and fixed two errors: Validation was checking |
Passed, pushed again to Master. |
Big thanks for your help, @mark-lunarg ! |
Implemented validation VUID-VkSwapchainCreateInfoKHR-imageFormat-01778.
The implied image creation parameters of the swapchain must be supported as reported by vkGetPhysicalDeviceImageFormatProperties
Also added test for this VUID. Test is running vkCreateSwapchainKHR with imageUsage and imageFormat params, that meet GetPhysicalDeviceSurfaceCapabilitiesKHR capabilities, but confirmed to fail vkGetPhysicalDeviceImageFormatProperties function. Not trying to make it fail with imageArrayLayers or imageExtent params, since I wasn't able to get right values for that in my setup.
Partially used code from #496 pull request that was adding same VUID, but hasn't been merged ever since, and outdated a bit.
In Mesa we already had several issues created which should have been avoided if this validation was present, i.e. https://gitlab.freedesktop.org/mesa/mesa/-/issues/3201 and https://gitlab.freedesktop.org/mesa/mesa/-/issues/178