gecko-dev/gfx/config
Andrew Osmond 925d668db0 Bug 1739996 - Select compositor or renderer thread for WebGL OOP depending on threadsafe GL status. r=jgilbert
If GL is threadsafe, we can run on the compositor thread. This appears
to have performance benefits, possibly because the renderer thread is
too busy. If GL is not threadsafe, we must run the WebGL OOP instances
on the renderer thread.

At the time of writing, only the nouveau drivers on Linux are considered
to be not threadsafe, so most users will see WebGL running on the
compositor thread. This patch also adds prefers to override the
blocklist to either assume GL is threadsafe
(webgl.threadsafe-gl.force-enabled) and not threadsafe
(webgl.threadsafe-gl.force-disabled).

Differential Revision: https://phabricator.services.mozilla.com/D130634
2021-11-09 17:33:46 +00:00
..
gfxConfig.cpp Bug 1541472 - Remove Advanced Layers, since it's disabled everywhere now. r=jrmuizel 2021-02-10 02:04:41 +00:00
gfxConfig.h
gfxConfigManager.cpp Bug 1725388 - Remove pref/envvars that can disable WebRender. r=jrmuizel 2021-08-12 20:28:53 +00:00
gfxConfigManager.h Bug 1725388 - Remove pref/envvars that can disable WebRender. r=jrmuizel 2021-08-12 20:28:53 +00:00
gfxFallback.h
gfxFeature.cpp Bug 1687312 - Expose gfx.feature.webrender probe to geckoview_streaming telemetry. r=jrmuizel,aosmond 2021-01-18 22:39:24 +00:00
gfxFeature.h Bug 1734505 - Add Feature::WINDOW_OCCLUSION r=gfx-reviewers,nical 2021-10-08 13:11:52 +00:00
gfxVarReceiver.h
gfxVars.cpp
gfxVars.h Bug 1739996 - Select compositor or renderer thread for WebGL OOP depending on threadsafe GL status. r=jgilbert 2021-11-09 17:33:46 +00:00
moz.build