<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Wayland lacks cross-process synchronisation"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=97353">97353</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Wayland lacks cross-process synchronisation
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>Wayland
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>wayland
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>wayland-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>tomek.bury@gmail.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Currently Wayland synchronisation model is build around an undefined behaviour,
which happens to work correctly with FOSS driver, but isn't guaranteed by
GL/EGL specifications. In other words a perfectly valid GL/EGL driver may not
work with Wayland.

The GL/EGL guarantees read-write synchronisation within a single context and
provides tools to synchronise multiple contexts within a single process, but
there are no guarantees or methods of achieving cross-process synchronisation,
except for Android fences, but those are Android-specific.

The only spec-compliant solution at the moment would be blocking CPU on the
compositor side (eglWaitClient() or glFinish()) before a buffer release event
is sent to the client. Alternatively, Wayland could create and mandate and
extension similar to EGL_ANDROID_native_fence_sync, where EGLSyncKHR objects
can be created from and converted to cross-process integer descriptors, that
are easy to send between client and compositor over Wayland protocol.

<a href="https://www.khronos.org/registry/egl/extensions/ANDROID/EGL_ANDROID_native_fence_sync.txt">https://www.khronos.org/registry/egl/extensions/ANDROID/EGL_ANDROID_native_fence_sync.txt</a>

Basing Wayland on an unspecified behaviour, where implementation detail of one
specific driver happens do deliver a desired result causes grief to other
driver maintainers where such behaviour isn't easy to achieve and, limits
Wayland adoption.</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>