On 10.04.2024 11:41, Ross Lagerwall wrote: > On Mon, Apr 8, 2024 at 11:25 AM Jan Beulich <jbeul...@suse.com> wrote: >> On 28.03.2024 16:11, Ross Lagerwall wrote: >>> * The image base address is set to 0 since it must necessarily be below >>> 4 GiB and the loader will relocate it anyway. >> >> While technically okay, what is the reason for this adjustment? > > The multiboot2 spec generally uses 32 bit addresses for everything and > says: > > "The bootloader must not load any part of the kernel, the modules, the > Multiboot2 information structure, etc. higher than 4 GiB - 1." > > An image base address above 4 GiB causes trouble because multiboot2 > wasn't designed for this.
Yet mb2 doesn't care about that PE header field at all, does it? In which case my question remains: What purpose does this particular modification of the image have? Jan