summaryrefslogtreecommitdiffstats
path: root/src/video_core/renderer_vulkan/vk_command_pool.h (follow)
Commit message (Collapse)AuthorAgeFilesLines
* vk_command_pool: Move definition of Pool into the cpp fileLioncash2020-09-251-4/+1
| | | | | Allows the implementation details to be changed without recompiling any files that include this header.
* vk_command_pool: Make use of override on destructorLioncash2020-09-251-1/+1
|
* vk_command_pool: Add missing header guardLioncash2020-09-251-0/+2
|
* renderer_vulkan: Make unconditional use of VK_KHR_timeline_semaphoreReinUsesLisp2020-09-191-0/+35
This reworks how host<->device synchronization works on the Vulkan backend. Instead of "protecting" resources with a fence and signalling these as free when the fence is known to be signalled by the host GPU, use timeline semaphores. Vulkan timeline semaphores allow use to work on a subset of D3D12 fences. As far as we are concerned, timeline semaphores are a value set by the host or the device that can be waited by either of them. Taking advantange of this, we can have a monolithically increasing atomic value for each submission to the graphics queue. Instead of protecting resources with a fence, we simply store the current logical tick (the atomic value stored in CPU memory). When we want to know if a resource is free, it can be compared to the current GPU tick. This greatly simplifies resource management code and the free status of resources should have less false negatives. To workaround bugs in validation layers, when these are attached there's a thread waiting for timeline semaphores.