As mentioned before, with EGL we use a shared context and can avoid paying the price for `MakeCurrent()` - the main blocker on NV for that is a reliable way to get a transparent Xvisual though, see https://github.com/KhronosGroup/EGL-Registry/pull/124. James: hint hint - do you think you could 1. ack the extension and 2. implement it in the NV binary driver? It's also needed for GTK4. Sounds to me like the other proposed solution would require quite a bit of work without a guarantee of success. Pushing EGL in turn would also unlock faster WebGL with DMABUF. IMO that's what we should do, and in the mean time disable HW acceleration on NV again. We've done that for ever until recently, so it's not a big regression.
Bug 1716049 Comment 16 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
As mentioned before, with EGL we use a shared context and can avoid paying the price for `MakeCurrent()` - the main blocker on NV for that is a reliable way to get a transparent Xvisual though, see https://github.com/KhronosGroup/EGL-Registry/pull/124. James: hint hint - do you think you could 1. ack the extension and 2. implement it in the NV binary driver? It's also needed for GTK4. Sounds to me like the other proposed solution would require quite a bit of work without a guarantee of success. Pushing EGL in turn would also unlock faster WebGL with DMABUF. IMO that's what we should do, and in the mean time disable HW acceleration on NV again. We've done that for ever until recently, so it's not a big regression. Edit: see also bug 1702546