-
Notifications
You must be signed in to change notification settings - Fork 25
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
Virtual Memory #25
Comments
So far I have mapped physical memory (exception stacks, memory mapped io et all), kernel code and kernel data into the virtual address space. Working on enabling the MMU to recognize the page tables, but not sure how to test if it's actually translating addresses correctly. |
Virtual memory kind of "works" but is in dire need of an overhaul. The datastructures for the VAS overwrote the L1 page table, and the system only worked because we overwrote the L1 Page table after the VM did. We discovered this bug by adding page table entries before we initialized the VM, we have currently just limited the amount the VM allocates (1024 instead of 4096 VAS'). I would also propose to relocate the page table to physical address 0x4000 as there is space there anyways between the IVT and the kernel start. |
This is currently being worked on in the #45 branch |
Resolved by #45 |
Implemented hardware translations so that it's easier to allocate and manage memory
The text was updated successfully, but these errors were encountered: