[Vulkan][Refactor] Pull out vulkan initialization into VulkanInstance and VulkanDevice #8188
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.
Next step of the refactoring initiated in #8157. Each of the following changes is implemented in a separate commit in this PR.
Broke out
VkInstancesetup/teardown into managed class. Previously, theVkInstancewas directly owned by theVulkanDeviceAPI. Now,VulkanDeviceAPIowns atvm::runtime::vulkan::VulkanInstancethat does setup/teardown of theVkInstance. This way, the teardown is done even if a later initialization step throws an exception.Renamed
VulkanContexttoVulkanDevice, to match with thetvm.contexttotvm.devicerename.Extracted
VulkanDeviceinitialization intoVulkanDeviceclassRemoved the
VkPhysicalDevicePropertiesmember variable fromVulkanDevice. With the separateVulkanDevicePropertiesclass, this moves all device parameter query/access to a single path.