Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] memtest86+ fix
Date: Sat, 5 Jan 2008 02:09:14 +0100	[thread overview]
Message-ID: <200801050209.14312.okuji@enbug.org> (raw)
In-Reply-To: <20080103010637.GD6843@thorin>

On Thursday 03 January 2008 02:06, Robert Millan wrote:
> On Thu, Jan 03, 2008 at 12:46:15AM +0100, Yoshinori K. Okuji wrote:
> > On Wednesday 02 January 2008 18:05, Robert Millan wrote:
> > > This fixes boot for memtest86+ (and actually, Linux zImages since they
> > > were all affected).
> > >
> > > The problem was that the first code in grub_linux_boot_zimage copied
> > > the payload from  0x100000 to 0x10000.  Since GRUB starts at 0x8200 and
> > > is typicaly more than 8 kiB in size, it'll most likely overwrite part
> > > of it.
> > >
> > > A bit of reestructuring was necessary to allow grub_dl_unload_all() to
> > > happen unconditionally as first step, since the information on whether
> > > this is a "big linux" was not promptly available.
> > >
> > > Comments?
> >
> > It is okay, except for "grub_linux_big"... I cannot figure out what it
> > wants to say. As you want to make it global, please choose a more
> > expressive name, such as "grub_big_linux_loaded".
>
> How about "grub_linux_big_loaded", for consistency with the other vars in
> <machine/kernel.h> that also start with grub_linux_ ?

"big_loaded" sounds horrible to me. How about grub_linux_big_image_loaded?

Okuji



  reply	other threads:[~2008-01-05  1:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 17:05 [PATCH] memtest86+ fix Robert Millan
2008-01-02 23:46 ` Yoshinori K. Okuji
2008-01-03  1:06   ` Robert Millan
2008-01-05  1:09     ` Yoshinori K. Okuji [this message]
2008-01-05  1:18       ` Pavel Roskin
2008-01-05 11:50         ` Robert Millan
2008-01-05 12:04           ` Yoshinori K. Okuji
2008-01-05 12:13             ` Robert Millan

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=200801050209.14312.okuji@enbug.org \
    --to=okuji@enbug.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox