b6c824dd16
Where possible, try to export the buffer rendered by the primary GPU as a dmabuf and import it to the secondary GPU and turn it into a DRM FB for scanout. If this works, we get a zero-copy path to secondary GPU outputs. This is especially useful on virtual drivers like EVDI (used for DisplayLink devices) which are not picky at all about what kind of FBs they can handle. The zero-copy path is prioritised after the secondary GPU copy path, which should avoid regressions for existing working systems. Attempting zero-copy would have the risk of being less performant than doing the copy on the secondary GPU. This does not affect the DisplayLink use case, because there is no GPU in a DisplayLink device. The zero-copy path is prioritised before the primary GPU and CPU copy paths. It will be tried on the first frame of an output and the copy path is executed too. If zero-copy fails, the result from the copy path will take over on that frame. Furthermore, zero-copy will not be attemped again on that output. If zero-copy succeeds, the copy path is de-initialized. Zero-copy is assumed to be always preferable over the primary GPU and CPU copy paths. Whether this is universally true remains to be seen. This patch has one unhandled failure mode: if zero-copy path first succeeds and then fails later, there is no fallback and the output is left frozen or black. https://gitlab.gnome.org/GNOME/mutter/merge_requests/810 |
||
|---|---|---|
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| clutter | ||
| cogl | ||
| data | ||
| doc | ||
| meson | ||
| po | ||
| src | ||
| tools | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| config.h.meson | ||
| COPYING | ||
| meson_options.txt | ||
| meson.build | ||
| mutter.doap | ||
| NEWS | ||
| README.md | ||
Mutter
Mutter is a Wayland display server and X11 window manager and compositor library.
When used as a Wayland display server, it runs on top of KMS and libinput. It implements the compositor side of the Wayland core protocol as well as various protocol extensions. It also has functionality related to running X11 applications using Xwayland.
When used on top of Xorg it acts as a X11 window manager and compositing manager.
It contains functionality related to, among other things, window management, window compositing, focus tracking, workspace management, keybindings and monitor configuration.
Internally it uses a fork of Cogl, a hardware acceleration abstraction library used to simplify usage of OpenGL pipelines, as well as a fork af Clutter, a scene graph and user interface toolkit.
Mutter is used by, for example, GNOME Shell, the GNOME core user interface, and by Gala, elementary OS's window manager. It can also be run standalone, using the command "mutter", but just running plain mutter is only intended for debugging purposes.
Contributing
To contribute, open merge requests at https://gitlab.gnome.org/GNOME/mutter.
The coding style used is primarily the GNU flavor of the GNOME coding
style
with some minor additions such as preferring stdint.h types over GLib
fundamental types, and a soft 80 character line limit. However, in general,
look at the file you're editing for inspiration.
Commit messages should follow the GNOME commit message guidelines. We require an URL to either an issue or a merge request in each commit.
License
Mutter is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for detalis.