Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unmap efiloader remnants once we're in the kernel #64

Open
1 of 3 tasks
IsaacWoods opened this issue Jul 31, 2021 · 0 comments
Open
1 of 3 tasks

Unmap efiloader remnants once we're in the kernel #64

IsaacWoods opened this issue Jul 31, 2021 · 0 comments
Labels
A-x86_64 Affects the x86_64 architecture C-bootloader Component: bootloader (combine with arch label) C-kernel Component: kernel

Comments

@IsaacWoods
Copy link
Owner

IsaacWoods commented Jul 31, 2021

We need to map loader code and data into the kernel's page tables in efiloader as we jump into the kernel, so we can continue fetching code once we switch to them, but before we jump into the kernel. However, it's not great to keep it lingering around for no reason, as we want to reclaim the physical memory.

  • Pass sections that remain mapped in the memory map
  • Mark them as free in the physical memory manager
  • Unmap them from the kernel's page tables
@IsaacWoods IsaacWoods added A-x86_64 Affects the x86_64 architecture C-kernel Component: kernel C-bootloader Component: bootloader (combine with arch label) labels Jul 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-x86_64 Affects the x86_64 architecture C-bootloader Component: bootloader (combine with arch label) C-kernel Component: kernel
Projects
None yet
Development

No branches or pull requests

1 participant