set LoaderTimeInitUSec and LoaderTimeExecUSec in GRUB #273
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number:
Fixes #272
Description of changes:
For
systemd-analyze
to report the time spent in firmware and in the boot loader, we need to setLoaderTimeInitUSec
andLoaderTimeExecUSec
, so the values can be read by efi_loader_get_boot_usec() and set by boot_timestamps().This patch series teaches GRUB to do this for x86 and aarch64. It relies on backported upstream patches from the series that added the Boot Loader Interface module]. That series implemented support for a different part of BLI: the
LoaderInfo
andLoaderDevicePartUUID
variables.Testing done:
Tested this under the different EFI implementations I have access to - edk2 via QEMU/KVM, EC2 Nitro instances, and VMware ESXi VMs.
Verified that
systemd-analyze
reports firmware and loader time:Confirmed that the variables aren't marked as non-volatile:
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.