Linuxydable/suyu
1
0
Fork 0
forked from suyu/suyu
Code Pull requests Activity
suyu/src/video_core/renderer_vulkan/vk_fence_manager.cpp

75 lines
2.2 KiB
C++
Raw Normal View History

vk_fence_manager: Initial implementation
2020-03-17 01:43:05 +01:00
// Copyright 2020 yuzu Emulator Project
// Licensed under GPLv2 or any later version
// Refer to the license.txt file included.
#include <memory>
#include "video_core/renderer_vulkan/vk_buffer_cache.h"
#include "video_core/renderer_vulkan/vk_fence_manager.h"
#include "video_core/renderer_vulkan/vk_scheduler.h"
#include "video_core/renderer_vulkan/vk_texture_cache.h"
renderer_vulkan: Move device abstraction to vulkan_common
2020-12-26 05:19:46 +01:00
#include "video_core/vulkan_common/vulkan_device.h"
vulkan_common: Rename renderer_vulkan/wrapper.h to vulkan_common/vulkan_wrapper.h Allows sharing Vulkan wrapper code between different rendering backends.
2020-12-25 01:30:11 +01:00
#include "video_core/vulkan_common/vulkan_wrapper.h"
vk_fence_manager: Initial implementation
2020-03-17 01:43:05 +01:00
namespace Vulkan {
vk_fence_manager: Use timeline semaphores instead of spin waits With timeline semaphores we can avoid creating objects. Instead of creating an event, grab the current tick from the scheduler and flush the current command buffer. When the fence has to be queried/waited, we can do so against the master semaphore instead of spinning on an event. If Vulkan supported NVN like events or fences, we could signal from the command buffer and wait for that without splitting things in two separate command buffers.
2021-01-08 06:37:02 +01:00
InnerFence::InnerFence(VKScheduler& scheduler_, u32 payload_, bool is_stubbed_)
: FenceBase{payload_, is_stubbed_}, scheduler{scheduler_} {}
vk_fence_manager: Initial implementation
2020-03-17 01:43:05 +01:00
vk_fence_manager: Use timeline semaphores instead of spin waits With timeline semaphores we can avoid creating objects. Instead of creating an event, grab the current tick from the scheduler and flush the current command buffer. When the fence has to be queried/waited, we can do so against the master semaphore instead of spinning on an event. If Vulkan supported NVN like events or fences, we could signal from the command buffer and wait for that without splitting things in two separate command buffers.
2021-01-08 06:37:02 +01:00
InnerFence::InnerFence(VKScheduler& scheduler_, GPUVAddr address_, u32 payload_, bool is_stubbed_)
: FenceBase{address_, payload_, is_stubbed_}, scheduler{scheduler_} {}
vk_fence_manager: Initial implementation
2020-03-17 01:43:05 +01:00
InnerFence::~InnerFence() = default;
void InnerFence::Queue() {
if (is_stubbed) {
return;
}
vk_fence_manager: Use timeline semaphores instead of spin waits With timeline semaphores we can avoid creating objects. Instead of creating an event, grab the current tick from the scheduler and flush the current command buffer. When the fence has to be queried/waited, we can do so against the master semaphore instead of spinning on an event. If Vulkan supported NVN like events or fences, we could signal from the command buffer and wait for that without splitting things in two separate command buffers.
2021-01-08 06:37:02 +01:00
// Get the current tick so we can wait for it
wait_tick = scheduler.CurrentTick();
scheduler.Flush();
vk_fence_manager: Initial implementation
2020-03-17 01:43:05 +01:00
}
bool InnerFence::IsSignaled() const {
if (is_stubbed) {
return true;
}
vk_fence_manager: Use timeline semaphores instead of spin waits With timeline semaphores we can avoid creating objects. Instead of creating an event, grab the current tick from the scheduler and flush the current command buffer. When the fence has to be queried/waited, we can do so against the master semaphore instead of spinning on an event. If Vulkan supported NVN like events or fences, we could signal from the command buffer and wait for that without splitting things in two separate command buffers.
2021-01-08 06:37:02 +01:00
return scheduler.IsFree(wait_tick);
vk_fence_manager: Initial implementation
2020-03-17 01:43:05 +01:00
}
void InnerFence::Wait() {
if (is_stubbed) {
return;
}
vk_fence_manager: Use timeline semaphores instead of spin waits With timeline semaphores we can avoid creating objects. Instead of creating an event, grab the current tick from the scheduler and flush the current command buffer. When the fence has to be queried/waited, we can do so against the master semaphore instead of spinning on an event. If Vulkan supported NVN like events or fences, we could signal from the command buffer and wait for that without splitting things in two separate command buffers.
2021-01-08 06:37:02 +01:00
scheduler.Wait(wait_tick);
vk_fence_manager: Initial implementation
2020-03-17 01:43:05 +01:00
}
video_core: Resolve more variable shadowing scenarios pt.2 Migrates the video core code closer to enabling variable shadowing warnings as errors. This primarily sorts out shadowing occurrences within the Vulkan code.
2020-12-05 10:51:14 +01:00
VKFenceManager::VKFenceManager(VideoCore::RasterizerInterface& rasterizer_, Tegra::GPU& gpu_,
video_core: Reimplement the buffer cache Reimplement the buffer cache using cached bindings and page level granularity for modification tracking. This also drops the usage of shared pointers and virtual functions from the cache. - Bindings are cached, allowing to skip work when the game changes few bits between draws. - OpenGL Assembly shaders no longer copy when a region has been modified from the GPU to emulate constant buffers, instead GL_EXT_memory_object is used to alias sub-buffers within the same allocation. - OpenGL Assembly shaders stream constant buffer data using glProgramBufferParametersIuivNV, from NV_parameter_buffer_object. In theory this should save one hash table resolve inside the driver compared to glBufferSubData. - A new OpenGL stream buffer is implemented based on fences for drivers that are not Nvidia's proprietary, due to their low performance on partial glBufferSubData calls synchronized with 3D rendering (that some games use a lot). - Most optimizations are shared between APIs now, allowing Vulkan to cache more bindings than before, skipping unnecesarry work. This commit adds the necessary infrastructure to use Vulkan object from OpenGL. Overall, it improves performance and fixes some bugs present on the old cache. There are still some edge cases hit by some games that harm performance on some vendors, this are planned to be fixed in later commits.
2021-01-17 00:48:58 +01:00
TextureCache& texture_cache_, BufferCache& buffer_cache_,
VKQueryCache& query_cache_, const Device& device_,
vk_fence_manager: Use timeline semaphores instead of spin waits With timeline semaphores we can avoid creating objects. Instead of creating an event, grab the current tick from the scheduler and flush the current command buffer. When the fence has to be queried/waited, we can do so against the master semaphore instead of spinning on an event. If Vulkan supported NVN like events or fences, we could signal from the command buffer and wait for that without splitting things in two separate command buffers.
2021-01-08 06:37:02 +01:00
VKScheduler& scheduler_)
video_core: Resolve more variable shadowing scenarios pt.2 Migrates the video core code closer to enabling variable shadowing warnings as errors. This primarily sorts out shadowing occurrences within the Vulkan code.
2020-12-05 10:51:14 +01:00
: GenericFenceManager{rasterizer_, gpu_, texture_cache_, buffer_cache_, query_cache_},
vk_fence_manager: Use timeline semaphores instead of spin waits With timeline semaphores we can avoid creating objects. Instead of creating an event, grab the current tick from the scheduler and flush the current command buffer. When the fence has to be queried/waited, we can do so against the master semaphore instead of spinning on an event. If Vulkan supported NVN like events or fences, we could signal from the command buffer and wait for that without splitting things in two separate command buffers.
2021-01-08 06:37:02 +01:00
scheduler{scheduler_} {}
vk_fence_manager: Initial implementation
2020-03-17 01:43:05 +01:00
Fence VKFenceManager::CreateFence(u32 value, bool is_stubbed) {
vk_fence_manager: Use timeline semaphores instead of spin waits With timeline semaphores we can avoid creating objects. Instead of creating an event, grab the current tick from the scheduler and flush the current command buffer. When the fence has to be queried/waited, we can do so against the master semaphore instead of spinning on an event. If Vulkan supported NVN like events or fences, we could signal from the command buffer and wait for that without splitting things in two separate command buffers.
2021-01-08 06:37:02 +01:00
return std::make_shared<InnerFence>(scheduler, value, is_stubbed);
vk_fence_manager: Initial implementation
2020-03-17 01:43:05 +01:00
}
Fence VKFenceManager::CreateFence(GPUVAddr addr, u32 value, bool is_stubbed) {
vk_fence_manager: Use timeline semaphores instead of spin waits With timeline semaphores we can avoid creating objects. Instead of creating an event, grab the current tick from the scheduler and flush the current command buffer. When the fence has to be queried/waited, we can do so against the master semaphore instead of spinning on an event. If Vulkan supported NVN like events or fences, we could signal from the command buffer and wait for that without splitting things in two separate command buffers.
2021-01-08 06:37:02 +01:00
return std::make_shared<InnerFence>(scheduler, addr, value, is_stubbed);
vk_fence_manager: Initial implementation
2020-03-17 01:43:05 +01:00
}
void VKFenceManager::QueueFence(Fence& fence) {
fence->Queue();
}
Address Feedback.
2020-04-16 18:29:53 +02:00
bool VKFenceManager::IsFenceSignaled(Fence& fence) const {
vk_fence_manager: Initial implementation
2020-03-17 01:43:05 +01:00
return fence->IsSignaled();
}
void VKFenceManager::WaitFence(Fence& fence) {
fence->Wait();
}
} // namespace Vulkan
Copy permalink