anonymous/yuzu - yuzu is the world's most popular, open-source, Nintendo Switch emulator — started by the creators of Citra. It is written in C++ with portability in mind,

	Commit message (Collapse)	Author	Files	Lines
2023-11-12	renderer_vulkan: Introduce separate cmd buffer for uploads	GPUCode	1	-10/+19

2023-06-22	general: remove atomic signal and wait	Liam	1	-13/+9

2023-06-18	renderer_vulkan: add missing include	Liam	1	-0/+1

2023-05-28	renderer_vulkan: Remove timeline semaphore wait	GPUCode	1	-7/+4

2023-05-20	vk_master_semaphore: Move fence wait on separate thread	GPUCode	1	-2/+44

2023-04-15	vulkan: use plain fences when timeline semaphores are not available	Liam	1	-1/+138

2022-12-04	vulkan_common: clean up extension usage	Liam	1	-4/+4

2022-04-23	general: Convert source file copyright comments over to SPDX	Morph	1	-3/+2
	This formats all copyright comments according to SPDX formatting guidelines. Additionally, this resolves the remaining GPLv2 only licensed files by relicensing them to GPLv2.0-or-later.
2021-06-22	vk_master_semaphore: Use jthread for debug thread	ReinUsesLisp	1	-14/+4

2021-04-15	common: Move settings to common from core.	bunnei	1	-1/+1
	- Removes a dependency on core and input_common from common.
2021-01-04	renderer_vulkan: Move device abstraction to vulkan_common	ReinUsesLisp	1	-1/+1

2021-01-03	renderer_vulkan: Rename VKDevice to Device	ReinUsesLisp	1	-1/+1
	The "VK" prefix predates the "Vulkan" namespace. It was carried around the codebase for consistency. "VKDevice" currently is a bad alias with "VkDevice" (only an upcase character of difference) that can cause confusion. Rename all instances of it.
2020-12-31	vulkan_common: Rename renderer_vulkan/wrapper.h to vulkan_common/vulkan_wrapper.h	ReinUsesLisp	1	-1/+1
	Allows sharing Vulkan wrapper code between different rendering backends.
2020-09-19	renderer_vulkan: Make unconditional use of VK_KHR_timeline_semaphore	ReinUsesLisp	1	-0/+56
	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.