I was thinking something along an array of memory descriptor structs,
listing -
- Base
- Length
- Type (Conventional memory, Kernel + Modules, GRUB structures like
the MBI
- Attributes (read protected, write protected, cacheability attributes)
The advantages over the old mmap_ entries being that the kernel has a
clear idea
of what is available memory, what is memory used by the bootloader
(and its structures like the MBI), and what
memory is used by everything associated with the loaded kernel (which
includes modules, additional ELF sections and the section headers
loaded).
Andrei Evgenievich Warkentin
[EMAIL PROTECTED]
Cell: (+1) (847) 321-15-55
On 24.03.2007, at 18:01, Yoshinori K. Okuji wrote:
On Saturday 24 March 2007 21:14, Andrei E. Warkentin wrote:
Actually, even now a Multiboot kernel has to do way too much work in
terms of memory initialization. The real problem is that GRUB only
gives you the BIOS memory map and the lowmem/highmem, which means you
need to figure out an "in use" memory map for yourself, by seeing if
any kernel modules are present, if any ELF section headers +
sections have been loaded, etc.
It would be nicer if the memory map passed by GRUB was a bit more
complete than listing generally-available memory. If I could find out
which memory is used by GRUB structures, which memory is used to load
my kernel (+ modules), that would be much better.
Could you suggest an example? How should information be passed to
make it
easy?
Okuji
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
