<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [EGL, i965] dEQP-EGL.functional.sharing.gles2.multithread.simple_egl_server_sync.textures.copyteximage2d_texsubimage2d_render" href="https://bugs.freedesktop.org/show_bug.cgi?id=99209#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [EGL, i965] dEQP-EGL.functional.sharing.gles2.multithread.simple_egl_server_sync.textures.copyteximage2d_texsubimage2d_render" href="https://bugs.freedesktop.org/show_bug.cgi?id=99209">bug 99209</a> from <a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> Kenneth Graunke</a> <pre>if you want to burn some cycles looking into making Mesa's texture locking less incompetent, that would probably be worthwhile. I'm also a bit concerned that I had to make the texture lock a recursive mutex a while back, when Kristian implemented meta fast clears...it may be that meta altering texturing state in this case isn't really valid - similar to our old recursive-meta hell. It may be that switching things to BLORP is more of an actual solution than the paper-over we feared it might be. But, again, feel free to look into it - I'm mostly speculating at this point.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>