All of lore.kernel.org
 help / color / mirror / Atom feed
From: BVK Chaitanya <bayapuneni_chaitanya@symantec.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Idea: Move kernel to upper memory
Date: Wed, 03 Sep 2008 16:15:33 +0530	[thread overview]
Message-ID: <48BE6ACD.7090607@symantec.com> (raw)
In-Reply-To: <20080830124058.GI16775@thorin>

Hi,


What is the conclusion of this thread?  is this idea still explored?


Robert Millan wrote:
> 
> The first concern that comes to mind is how would GRUB coexist with the
> payload area which precisely starts at 0x100000.  But I expect we'd face
> many unexpected issues.
> 

Does this mean, GRUB needs to fit within 1MB limit when all its modules 
are loaded?  More clearly, are there any limits on where (and how many) 
grub modules can be dynamically loaded currently?

Since payload(s) needs to be present at their precise positions only 
after the boot command, we can always deterministically /schedule/ 
memmove operation to be executed as part of boot command.

Since boot command is the last command executed by GRUB (correct me if 
not), we can overwrite any GRUB code/data at that point.  This also 
needs boot command to exist in low memory.

The main advantage i see here is that it removes any arbitrary limits on 
number of modules or their placement, if at all limits exists.


thanks,
--
bvk-chaitanya



  parent reply	other threads:[~2008-09-03 10:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 11:15 Idea: Move kernel to upper memory Bean
2008-08-30 12:40 ` Robert Millan
2008-08-30 15:15   ` Bean
2008-08-31 13:28     ` Robert Millan
2008-08-31 13:30     ` Robert Millan
2008-08-31 13:55       ` Bean
2008-09-03 10:45   ` BVK Chaitanya [this message]
2008-09-04 19:19     ` Robert Millan
2008-09-06 14:14       ` BVK
2009-04-19 15:45 ` Vladimir Serbinenko

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=48BE6ACD.7090607@symantec.com \
    --to=bayapuneni_chaitanya@symantec.com \
    --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.