<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED MOVED - Wayland lacks cross-process synchronisation" href="https://bugs.freedesktop.org/show_bug.cgi?id=97353#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED MOVED - Wayland lacks cross-process synchronisation" href="https://bugs.freedesktop.org/show_bug.cgi?id=97353">bug 97353</a> from <a class="email" href="mailto:tomek.bury@gmail.com" title="Tomek Bury <tomek.bury@gmail.com>"> Tomek Bury</a> <pre>(In reply to Daniel Stone from <a href="show_bug.cgi?id=97353#c21">comment #21</a>) > EGL was mostly written by copying GLX and changing a few terms around. > eglWaitNative is the direct analog of glXWaitX (the documentation of which > explicitly mentions XSync), and the required implementation of eglWaitNative > on X11 is glXWaitX, which necessarily involves crossing a process boundary. A spec that EGL borrows from mentioned XSync therfore EGL mandates cross-process interoperability? Wow, that's a hell of a stretch :D > EGL objects - as visible to clients - are not shareable across process > contexts. But this does not mean that EGL calls are required to never do > anything which could cross a process boundary [...] I never said that. I'm only saying that cross-process stuff is explicitly outside of EGL scope. As far as core EGL is concerned everything is inside one process. Wayland needs more therefore Wayland needs extension(s) to expose any cross-process functionality to callers. > Implementing support for any winsys apart from fbdev or GBM necessarily > imposes requirements on cross-process co-ordination; this includes exporting > synchronisation objects between processes. Yes. > If EGL banned cross-process fencing [...] But it doesn't ban cross-process and it doesn't mandate cross-process, it only says "no cross-process out of the box, wirte extension or look elsewhere if you need it".</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>