On Fri, Jun 02, 2023 at 06:17:13PM +0200, Ard Biesheuvel wrote:
'EFI code' is ambiguous here.
Most of the decompressor code is constructed in a way that permits
- booting 'native EFI' via the EFI stub
- booting 'pseudo-EFI' where GRUB or another Linux/x86 specific
bootloader populates boot_params with all the EFI specific information
(system table, memory map, etc)
This distinction has been abstracted away here, and so we might be
dealing with the second case, and booting from a GRUB that does not
understand accepted memory, but simply copied the EFI memory map
(including unaccepted regions) as it normally does. (Note that the
second case also covers kexec boot, so we do need to support it)
Right, I was hoping there to be some glue which sanity-checks
boot_params.efi_info instead relying on users to do so and thus have
a bunch of duplicated code.
So, yes, right after populating the boot_params pointer...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette