mirror of
https://gitlab.freedesktop.org/plymouth/plymouth.git
synced 2026-05-07 17:48:01 +02:00
read-only mirror of https://gitlab.freedesktop.org/plymouth/plymouth
42ee6809b0
During the initial monitor/connector enumeration on boot the kernel fires a large number of change events. If we process these 1 by 1, we spend a lot of time probing the DRM-connectors. So instead we collect them all and then coalescence them so that if there are multiple change events pending for a single card, we only re-probe the card once. Here are some numbers of the probing times before / after this patch: 1. Lenovo X1 carbon 8th gen connected to a Lenovo Thunderbolt dock gen 2 with 2 FullHD monitors connected: Before: add event card0: 00:00:02.543 last change complete at: 00:00:04.250, 12 change events processed, 13 probes done! After: add event card0: 00:00:02.548 last change complete at: 00:00:04.049 1 change event processed, 2 probes done! 2. Intel skylake CPU + iGPU based desktop with 2 FullHD monitors connected: Before: add event card0: 00:00:02.394 last change complete at: 00:00:05.024, 5 change events processed, 6 probes done! After: add event card0: 00:00:02.343 last change complete at: 00:00:03.744, 1 change event processed, 2 probes done! In the Thunderbolt dock case we probe the DRM-connectors 2 times instead of 13 times after this change. This does not lead to a big speed-up though because the dock caches the monitors EDID info and the DP aux channel to the dock is quite fast. In the desktop case we only reduce the amount of probes from 6 to 2, so less then in the Thunderbolt dock case, but since we don't have the EDID caching happening there this does reduce the time which it takes to probe the DRM-connectors from 2.6 seconds to 1.4 seconds which is a huge improvement. Signed-off-by: Hans de Goede <hdegoede@redhat.com> |
||
|---|---|---|
| docs | ||
| images | ||
| po | ||
| scripts | ||
| src | ||
| systemd-units | ||
| themes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| acinclude.m4 | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.ac | ||
| COPYING | ||
| INSTALL | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| TODO | ||
plymouth - graphical boot animation and logger Plymouth is an application that runs very early in the boot process (even before the root filesystem is mounted!) that provides a graphical boot animation while the boot process happens in the background. It is designed to work on systems with DRM modesetting drivers. The idea is that early on in the boot process the native mode for the computer is set, plymouth uses that mode, and that mode stays throughout the entire boot process up to and after X starts. Ideally, the goal is to get rid of all flicker during startup. For systems that don't have DRM mode settings drivers, plymouth falls back to text mode (it can also use a legacy /dev/fb interface). In either text or graphics mode, the boot messages are completely occluded. After the root file system is mounted read-write, the messages are dumped to /var/log/boot.log. Also, the user can see the messages at any time during boot up by hitting the escape key. Plymouth isn't really designed to be built from source by end users. For it to work correctly, it needs integration with the distribution. Because it starts so early, it needs to be packed into the distribution's initial ram disk, and the distribution needs to poke plymouth to tell it how boot is progressing. plymouth ships with two binaries: /sbin/plymouthd and /bin/plymouth The first one, plymouthd, does all the heavy lifting. It logs the session and shows the splash screen. The second one, /bin/plymouth, is the control interface to plymouthd. It supports things like plymouth show-splash, or plymouth ask-for-password, which trigger the associated action in plymouthd. Plymouth supports various "splash" themes which are analogous to screensavers, but happen at boot time. There are several sample themes shipped with plymouth, but most distributions that use plymouth ship something customized for their distribution. Plymouth isn't done yet. It's still under active development, but is used in several popular distros already, including Fedora, Mandriva, Ubuntu and others. See the distributions page for more information. As with other projects hosted on freedesktop.org, Plymouth follows its Code of Conduct, based on the Contributor Covenant. Please conduct yourself in a respectful and civilized manner when using the above mailing lists, bug trackers, etc: https://www.freedesktop.org/wiki/CodeOfConduct