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

Relocate boot component in physical memory to be adjacent to kernel #183

Closed
gparmer opened this issue Jun 9, 2016 · 2 comments
Closed

Comments

@gparmer
Copy link
Collaborator

gparmer commented Jun 9, 2016

Currently, GRUB tends to place the boot component into physical memory significantly offset from the end of the kernel. There is, as far as I can see, very little reason for this offset.

This proposal is to mem_move (note we can't memcpy) the booter to be physically contiguous with the kernel memory during the early boot process (i.e. modifications in kernel.c) while updating where the boot-time dynamic allocations, and untyped memory are located. These will overlap with the current boot component memory, so it will likely need to be zero-ed out. This will reclaim around 10MB-50MB of memory which is lost for no real reason.

@georgit
Copy link
Contributor

georgit commented Jun 14, 2016

Sounds good. Are there any obstacles to this?

@gparmer
Copy link
Collaborator Author

gparmer commented Jun 14, 2016

Not really. It is a straightforward change as far as I can tell, but one that is lower priority at this point than other things (tcaps, embedded VM, cbufs on Speck, etc...).

BTW, in the above, I certainly meant memmove. My mistake.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants