All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: memory allocator enhancements...
Date: Sun, 05 Apr 2009 15:24:04 +0300	[thread overview]
Message-ID: <49D8A2E4.3030908@nic.fi> (raw)

Hi All,

I have been thinking on how to improve memory allocator (thou hasn't got
too much time lately to play with it) so it could aid in following
scenarios:

1. Move VBE BIOS thunks or other code from kernel to actual driver
- specially named segment that gets allocated to lowmem in order to call
VBE BIOS extensions
- These should be located right after kernel in lowmem
- Seems to be a bit tricky to patch relocation info properly (at least
this is what I was last debugging). Ideas are welcome. Perhaps my code
was not just modified properly...

2. Allocate memory for BIOS extensions in order to support BIOS drive
mapping and El Torito or what ever someone needs.
- Probably need to make hole to memory map that is passed to OS so
allocated memory needs to be at end of lowmem so no holes within low
memory are present
- Perhaps this should be only done at last step of boot process. Eg
allocate first memory to high mem and then when boot decision has been
made, then allocate to low mem and make necessary hooks

3. Load OS image at start of highmem. I do not remember which OS needed
this thou...

4. Allocate memory for GRUB code/modules/data. This can be at end of
highmem.

Are there any other needs?

So what does people feel about these changes. I am afraid if too much
freedom is given it will make it complex...

Thanks,
Vesa Jääskeläinen



             reply	other threads:[~2009-04-05 12:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05 12:24 Vesa Jääskeläinen [this message]
2009-04-05 12:49 ` memory allocator enhancements phcoder
2009-04-06 17:13   ` phcoder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49D8A2E4.3030908@nic.fi \
    --to=chaac@nic.fi \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.