diff options
| author | Alexandros Frantzis <alexandros.frantzis@collabora.com> | 2018-11-29 11:35:30 +0200 |
|---|---|---|
| committer | Pekka Paalanen <pekka.paalanen@collabora.com> | 2018-12-14 14:01:54 +0200 |
| commit | 57423eac60cc234ebfad15f394488a47f69afe16 (patch) | |
| tree | c439069d96fd0c9bc4a20b1617467832e866c559 | |
| parent | 08903bdf90d8051b9e650ac2bcef3d73188a03e6 (diff) | |
linux-explicit-synchronization: Clarify implicit synchronization guarantees of release events
Clarify that after zwp_buffer_release_v1 events, otherwise unused
buffers can be reused without any additional implicit synchronization.
This is in contrast to wl_buffer.release, which doesn't guarantee that
implicit synchronization is not required to safely use a buffer after
the event is received.
Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>
Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.com>
| -rw-r--r-- | unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml b/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml index 6d5783d..d0a8cf0 100644 --- a/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml +++ b/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml @@ -226,6 +226,11 @@ signaled when all operations by the compositor on that buffer for that commit have finished. + Once the fence has signaled, and assuming the associated buffer is not + pending release from other wl_surface.commit requests, no additional + explicit or implicit synchronization is required to safely reuse or + destroy the buffer. + This event destroys the zwp_linux_buffer_release_v1 object. </description> <arg name="fence" type="fd" summary="fence for last operation on buffer"/> @@ -238,6 +243,11 @@ using it, or has a guarantee that all its operations on that buffer for that commit have finished. + Once this event is received, and assuming the associated buffer is not + pending release from other wl_surface.commit requests, no additional + explicit or implicit synchronization is required to safely reuse or + destroy the buffer. + This event destroys the zwp_linux_buffer_release_v1 object. </description> </event> |