You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
with a custom FrameAllocator implementation would be the way to go. e.g. when mapping the boot info in the bootloader's page tables, we would do something like this:
Even then, it's not a pretty solution, as we'd need to rework LegacyFrameAllocator to support allocating frames that will be marked as Usable in the memory map.
The text was updated successfully, but these errors were encountered:
When allocating frames to copy the bootloader page table, we allocate them using the default frame allocator meaning the kernel will see those regions as reserved. It also happens when mapping the boot info.
This is wrong, as the kernel should be free to overwrite the bootloader's page tables.
Solution
I think a newtype like so:
with a custom
FrameAllocator
implementation would be the way to go. e.g. when mapping the boot info in the bootloader's page tables, we would do something like this:Even then, it's not a pretty solution, as we'd need to rework
LegacyFrameAllocator
to support allocating frames that will be marked asUsable
in the memory map.The text was updated successfully, but these errors were encountered: