GNU GRUB - Bugs: bug #38145, Add support for boot benchmarking
You are not allowed to post comments on this tracker with your current authentication level.
bug #38145: Add support for boot benchmarking
Submitter: | Jordan Uggla <jordanu> | ||
Submitted: | Tue 22 Jan 2013 08:05:46 PM UTC | ||
Category: | None | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Feature Request |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Open | Release: | Bazaar - trunk |
Release: | Reproducibility: | None | |
Planned Release: | 2.03+ |
Wed 30 Jan 2013 09:00:11 AM UTC, comment #2: |
Andrei Borzenkov <arvidjaar>![]() |
Sat 26 Jan 2013 09:00:02 PM UTC, comment #1: I see no reason to make something like this EFI-specific or in EFI-specific way. This should be all-platform feature. We have a ms-resolution timer on all platforms except very old BIOS-based machines. |
Vladimir Serbinenko <phcoder>![]() |
Tue 22 Jan 2013 08:05:46 PM UTC, original submission:
Systemd-analyze can report how much time was spent at boot in firmware initialization and the bootloader if the bootloader sets specific UEFI variables (LoaderTicksInit and LoaderTicksExec) as described here:
|
Jordan Uggla <jordanu> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
EFI provides convenient interface to pass information from bootloader to kernel via variables. I am not sure how to do it e.g. on BIOS, except piggybacking on kernel command line.
Am I right that you are not against this idea as long as it is implemented in generic enough way?