[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
VkInstance
setup/teardown into managed class. Previously, theVkInstance
was directly owned by theVulkanDeviceAPI
. Now,VulkanDeviceAPI
owns atvm::runtime::vulkan::VulkanInstance
that does setup/teardown of theVkInstance
. This way, the teardown is done even if a later initialization step throws an exception.Renamed
VulkanContext
toVulkanDevice
, to match with thetvm.context
totvm.device
rename.Extracted
VulkanDevice
initialization intoVulkanDevice
classRemoved the
VkPhysicalDeviceProperties
member variable fromVulkanDevice
. With the separateVulkanDeviceProperties
class, this moves all device parameter query/access to a single path.