4.12 Merge window part 1

Posted May 4, 2017 6:58 UTC (Thu) by alison (subscriber, #63752)
Parent article: 4.12 Merge window part 1

'The new "AnalyzeBoot" tool can create a timeline of the kernel's bootstrap process in HTML format.'

How is AnalyzeBoot different from systemd-bootchart? Speaking of systemd, are we right to assume that Andy Lutomirski has killed the most recent attempt to get D-Bus-like broadcast IPC notifications into the kernel?

4.12 Merge window part 1

Posted May 4, 2017 16:01 UTC (Thu) by Tara_Li (guest, #26706) [Link]

Hopefully, AnalyzeBoot doesn't *depend* on systemd. There actually *are* people who prefer to use a different init system.

4.12 Merge window part 1

Posted May 4, 2017 16:20 UTC (Thu) by smcv (subscriber, #53363) [Link]

As a user-space component, systemd-bootchart doesn't know anything before pid 1 comes up (it starts as pid 1, forks to run in the background, and execs the real init as pid 1). It also doesn't have access to kernel internals in detail.

If the majority of your boot cost is happening in user-space, systemd-bootchart is probably still the more useful tool (particularly for low-hanging fruit like "everything seems to be waiting for foo, can I avoid that?"), but if a large part of your boot cost is in kernel-space, this new thing is how you would analyze that part.

4.12 Merge window part 1

Posted May 6, 2017 9:10 UTC (Sat) by flussence (guest, #85566) [Link]

To take that question further back in history: how is systemd-bootchart different from pybootchart?