Skip to content

[Tracking] Develop a physical frame allocator under the memory subsystem #5

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

Open
7 tasks
mdpatelcsecon opened this issue Sep 9, 2024 · 0 comments
Open
7 tasks

Comments

@mdpatelcsecon
Copy link
Collaborator

mdpatelcsecon commented Sep 9, 2024

Implement all of the following features.

  • Read the Limine memory map and populate its own data structures to track usable and unusable page frames.
  • Allocate a single frame
  • Allocate n continguous frames
  • Deallocate a single frame
  • Deallocate a set of contiguous frames starting at a given physical address.
  • Track frames that are committed but not actually allocated (such as those that might eventually be required by copy-on-write or faulted in virtual memory regions)
  • For each allocated range of page frames track which virtual address spaces it is mapped into and which capabilites exist that could allow it to be mapped in the future. (Track these two things separately)
@mdpatelcsecon mdpatelcsecon changed the title develop a physical frame allocator under the memory module develop a physical frame allocator under the memory subsystem Sep 9, 2024
@mdpatelcsecon mdpatelcsecon changed the title develop a physical frame allocator under the memory subsystem [Tracking] Develop a physical frame allocator under the memory subsystem Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant