[Bug 84252] DRI3 rendering gets stuck waiting for present idle notify event

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=84252

--- Comment #34 from Tobias Jakobi <liquid.acid at gmx.net> ---
Hello Axel,

thanks for the explanation. So if I understand this correctly, then this issues
comes from the fact that each XCB connection object is protected by a (single)
mutex (the iolock one, if I read the libxcb code correctly), which causes
trouble in Mesa' GLX DRI3 implementation because the same XCB connection is
then used from two different threads.
One thread A uses the connection to wait for one event, which doesn't come
because thread B is blocked (XCB mutex is locked) and therefore never reaches
the point where the event is signalled.

I had a brief look at the Xnine implementation and the GLX DRI3 one, but I'm
not too familiar with it to port the "two connection" approach over.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150320/41dd9c4b/attachment.html>