Memory Allocation Stuff #2
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Question
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#3 Process Creation & Binary Support
shibedrill/gila
Reference: shibedrill/gila#2
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Need to get the memory allocation stuff worked out. I don't know how any of it works. :/
Currently, the OS is able to enumerate the page lists provided by the bootloader. Next, it has to create its own page tables (levels 4 through 1), populate them with new page mappings, and then switch to the new page table, before it can begin allocating page table entries for processes.
It is important to note that the kernel must be able to create these structures on 4KiB boundaries.