commit 16c253fca727329eded651a640fb80ec39c044f5
author Piers Daniell <PDANIELL@nvidia.com> Wed May 30 14:34:05 2018 -0600
committer Mike Schuchardt <mikes@lunarg.com> Tue Jun 26 08:27:09 2018 -0600
tree f05389f75eb1a0c801e8f176f6c696b79fe5f90b
parent 17de5fdb64b43aac8824a9bd1c1ba949cb7b7635

Add core validation for VK_KHR_get_display_properties2

This adds core validation for VK_KHR_get_display_properties2, which is
based on the existing validation for the corresponding functions in
VK_KHR_display. The VK_KHR_get_display_properties2 has no explicit VUs,
only implicit ones that correct generated in the param validation
layer.

This MR also adds object tracking for VkDisplayKHR and
VkDisplayModeKHR for both VK_KHR_display and
VK_KHR_get_display_properties2. Note that the lifetime of these objects
is tied to the physical device. They aren't "created" just queried by
the application. Similar to how VkQueue objects are with respect to a
VkDevice.

This has been tested with the Vulkan CTS
VK_KHR_get_display_properties2 tests and showed some valid usage
violations in the test. These violations are reported here
Tracker/vk-gl-cts#1155 (closed) and fixed here
https://gerrit.khronos.org/#/c/2507/.

scripts/object_tracker_generator.py

diff --git a/scripts/object_tracker_generator.py b/scripts/object_tracker_generator.py
index 710d1e9..0a6626a 100644
--- a/scripts/object_tracker_generator.py
+++ b/scripts/object_tracker_generator.py
@@ -188,6 +188,9 @@
             'vkCmdInsertDebugUtilsLabelEXT',
             'vkGetDisplayModePropertiesKHR',
             'vkGetPhysicalDeviceDisplayPropertiesKHR',
+            'vkGetPhysicalDeviceDisplayProperties2KHR',
+            'vkGetDisplayPlaneSupportedDisplaysKHR',
+            'vkGetDisplayModeProperties2KHR',
             ]
         # These VUIDS are not implicit, but are best handled in this layer. Codegen for vkDestroy calls will generate a key
         # which is translated here into a good VU.  Saves ~40 checks.