This is the work around I'm using to address issue #4 where multiboot_info_structure is zeroed out as it is allocated to the kernel page table.
The PR reserves the page where the multiboot_info_structure resides in.
Test
Attach GDB to the running kernel and inspect address 0xffffffff80010000 with x/32xg 0xffffffff80010000.
It should contain information from multiboot now.
Description
This is the work around I'm using to address issue #4 where
multiboot_info_structureis zeroed out as it is allocated to the kernel page table.The PR reserves the page where the
multiboot_info_structureresides in.Test
Attach GDB to the running kernel and inspect address
0xffffffff80010000withx/32xg 0xffffffff80010000. It should contain information from multiboot now.