GNOME Bugzilla – Bug 787925
Explicit fencing/synchronization for Mutter/Wayland
Last modified: 2021-07-05 13:52:42 UTC
The attached patch implements explicit fencing/synchronization for Mutter's Wayland backend when running natively. This is implemented as a more direct match to Vulkan's vkQueuePresentKHR / vkAcquireNextImageKHR semantics, which allow applications to provide more restrictive fences to synchronize against than the implicit fences, as well as for the winsys to provide an explicit fence for the client to check against. Exposing this information to the compositor also allows for more smart scheduling, where the compositor could potentially decide to defer rendering of newer client buffers until their rendering has completed.
Created attachment 360093 [details] [review] wayland: Support explicit synchronization and fencing Support zwp_linux_explicit_synchronization_v1, to allow clients to control fencing of the buffers they send to a Wayland compositor. Only implemented on the native backend, as it requires EGL.
Created attachment 363125 [details] [review] wayland: Support explicit synchronization and fencing Same patch as before but with a few changes to apply cleanly on top of master.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/mutter/-/issues/ Thank you for your understanding and your help.