v3dv: implement VK_KHR_workgroup_memory_explicit_layout

There is an issue with some Amber tests for this feature using
a larger number of workgroup invocations than supported without
checking the limit. I filed and issue [1] (and a CL with a fix), but
meanwhile we want to flag those as expected crashes for CI.

[1] https://gitlab.khronos.org/Tracker/vk-gl-cts/-/issues/3913

Reviewed-by: Alejandro Piñeiro <apinheiro@igalia.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/18337>
This commit is contained in:
Iago Toral Quiroga
2022-08-31 12:39:32 +02:00
committed by Marge Bot
parent 2b00ba23c2
commit ffd3ef35bb
4 changed files with 23 additions and 3 deletions

View File

@@ -530,7 +530,7 @@ Khronos extensions that are not part of any Vulkan version:
VK_KHR_swapchain DONE (anv, dzn, lvp, panvk, pvr, radv, tu, v3dv, vn)
VK_KHR_swapchain_mutable_format DONE (anv, lvp, radv, tu, v3dv, vn)
VK_KHR_wayland_surface DONE (anv, dzn, lvp, panvk, radv, tu, v3dv, vn)
VK_KHR_workgroup_memory_explicit_layout DONE (anv, radv)
VK_KHR_workgroup_memory_explicit_layout DONE (anv, radv, v3dv)
VK_KHR_win32_keyed_mutex not started
VK_KHR_win32_surface DONE (dzn, lvp)
VK_KHR_xcb_surface DONE (anv, dzn, lvp, radv, tu, v3dv, vn)