Re: [Mesa-dev] [RFC 1/2] glx|egl: allow to test if glthread is safe enough on X11 platform

2017-05-03 Thread Nicolai Hähnle
On 28.04.2017 23:11, Gregory Hainaut wrote: I extended the struct __DRIbackgroundCallableExtensionRec because the other function pointer is already related for glthread. DRI2/DRI3 glx code path check that display can be locked (basically XInitThread was called) EGL code path is more tricky as

Re: [Mesa-dev] [RFC 1/2] glx|egl: allow to test if glthread is safe enough on X11 platform

2017-04-28 Thread Matt Turner
On Fri, Apr 28, 2017 at 2:11 PM, Gregory Hainaut wrote: > I extended the struct __DRIbackgroundCallableExtensionRec because > the other function pointer is already related for glthread. > > DRI2/DRI3 glx code path check that display can be locked (basically >

[Mesa-dev] [RFC 1/2] glx|egl: allow to test if glthread is safe enough on X11 platform

2017-04-28 Thread Gregory Hainaut
I extended the struct __DRIbackgroundCallableExtensionRec because the other function pointer is already related for glthread. DRI2/DRI3 glx code path check that display can be locked (basically XInitThread was called) EGL code path is more tricky as we don't want to pull X11 header. Instead the