-
Notifications
You must be signed in to change notification settings - Fork 8
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
Mallocation #30
Comments
Ok, so I'm a bit stumped - I've been stuck on this issue for a while, in particular trying to get the
The line with This is my first exposure to writing code in a bootloader, so I'm really enjoying this :) |
^^^ for historical purposes (forgive me, it's late at night) Yes, your suspicion is correct. Luckily |
Just an update: I'm able to get the first few hundred kilobytes mapped! I was able to verify the mapping using gdb, and I am working on getting it to work for many mappings. I believe we talked about using bitmaps, so I think I can get a simple page allocator in a week or so! |
Memory management!
Querying the BIOS to know what memory is available must be done to know what memory we have.
Once that is done, an allocator can be made using the free regions.
This will be difficult, and despite sharing the same concept of CSE220's malloc project,
it will be nothing like that project.
The OS should do all the bookkeeping itself (also unlike CSE 220's malloc).
It is recommended that allocation occurs in 4KiB blocks (pages).
The text was updated successfully, but these errors were encountered: