Add driverUUID and driverVersion to settings file device configuration parameters#1778
Merged
charles-lunarg merged 2 commits intoOct 2, 2025
Conversation
|
CI Vulkan-Loader build queued with queue ID 540303. |
|
CI Vulkan-Loader build # 3201 running. |
|
CI Vulkan-Loader build queued with queue ID 540321. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
CI Vulkan-Loader build # 3202 running. |
|
CI Vulkan-Loader build # 3202 failed. |
ziga-lunarg
reviewed
Sep 26, 2025
ziga-lunarg
approved these changes
Sep 26, 2025
charles-lunarg
force-pushed
the
add_driver_details_to_settings
branch
from
447a673 to
5699f86
Compare
|
CI Vulkan-Loader build queued with queue ID 540427. |
1 similar comment
|
CI Vulkan-Loader build queued with queue ID 540427. |
|
CI Vulkan-Loader build # 3203 running. |
Allows for the loader_log call to not have 16+ parameters.
…n parameters deviceUUID is not sufficient to be able to distinguish VkPhysicalDevices as there can be multiple ICD's that report the same VkPhysicalDevice. This can easily occur when a development build of a driver is present alongside a stable build on a system. driverUUID then helps differentiate ICD's reporting the same VkPhysicalDevice, but isn't sufficient as some drivers use the same driverUUID across all builds (RADV from Mesa as example). Thus, driverVersion is used for that purpose.
charles-lunarg
force-pushed
the
add_driver_details_to_settings
branch
from
5699f86 to
66d32bc
Compare
|
CI Vulkan-Loader build queued with queue ID 540456. |
|
CI Vulkan-Loader build # 3204 running. |
|
CI Vulkan-Loader build # 3204 passed. |
Contributor
|
@charles-lunarg, could you document in the description, what the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
deviceUUID is not sufficient to be able to distinguish VkPhysicalDevices as there can be multiple
ICD's that report the same VkPhysicalDevice. This can easily occur when a development build of
a driver is present alongside a stable build on a system. driverUUID then helps differentiate ICD's
reporting the same VkPhysicalDevice, but isn't sufficient as some drivers use the same driverUUID
across all builds (RADV from Mesa as example). Thus, driverVersion is used for that purpose.