From: Joe Bonasera <joe.bonasera@sun.com>
To: grub-devel@gnu.org
Subject: Re: Grub-devel Digest, Vol 33, Issue 19
Date: Wed, 22 Nov 2006 12:55:53 -0800 [thread overview]
Message-ID: <4564B959.10102@sun.com> (raw)
In-Reply-To: <iss.8f960c3c.4ebf.45648480.44026.78@relay0i.sun.com>
grub-devel-request@gnu.org wrote:
>>
>> Just to be clear. For grub2 on x86, will it be true that there is only
>> a single grub2 binary that understands both elf32 and elf64?
>
> Yes.
>
>> Would the different tags i86-pc vs x86_64 (if any) be determined by
>> knowing if which type elf gets loaded?
>
> My personal opinion is that we should not pass any information to the
> kernel about what format it is provided in.
I agree about that, the OS should intrinsically know it's own format. :)
However, it shouldn't have to figure out what format the data passed
to it from the boot loader is in. If I boot a 32 bit kernel on a
64 bit capable platform/boot loader, the 32 bit kernel shouldn't have to
deal with figuring out if it's getting 32 or 64 bit information from
the boot loader.
I think it's pretty common for people to install both 32 and 64 bit
OS mixes on a single box. (I'm composing this on a machine that can
boot either 32 bit windows, 32 bit Suse, 64bit Fedora, 32 or 64 bit
Solaris partitions) all from one copy of grub and one copy of menu.lst.
>
> If the image is an ELF64, it will be loaded as an ELF64. So in your
> case, for x86_64 hosts, provide the kernel as an ELF64 image. For
> IA-32, provide an ELF32 image.
Requiring that would be a big restriction from grub 0.9x, where the multiboot
info passed to the booted OS is always in a fixed 32 bit format. Making that information
(the "Multiboot Information Format" section of http://grub.enbug.org/MultibootDraft)
variant based hardware capability would greatly complicate the OS side of things.
Specifically a 32 bit OS would have to be able to decode both 32 and 64 bit
versions of the data. Yuck. If grub2 really needs to make the
format/content variant, I would much rather see it vary based on the
target OS type. Or better yet, just always use the larger size data types/content -
even for 32 bit booting.
Joe
>
> ~j
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 190 bytes
> Desc: not available
> Url : http://lists.gnu.org/pipermail/grub-devel/attachments/20061122/c632780d/attachment.bin
>
> ------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
> End of Grub-devel Digest, Vol 33, Issue 19
> ******************************************
next parent reply other threads:[~2006-11-22 20:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <iss.8f960c3c.4ebf.45648480.44026.78@relay0i.sun.com>
2006-11-22 20:55 ` Joe Bonasera [this message]
2006-11-25 2:09 ` multiboot2: variable data size Hollis Blanchard
2006-11-25 3:10 ` Yoshinori K. Okuji
2006-11-25 3:33 ` Hollis Blanchard
2006-11-25 3:46 ` Yoshinori K. Okuji
2006-11-25 4:08 ` Hollis Blanchard
2006-11-25 4:36 ` Yoshinori K. Okuji
2006-11-25 5:01 ` Hollis Blanchard
2006-11-28 9:29 ` Johan Rydberg
2006-11-28 11:35 ` Yoshinori K. Okuji
2006-11-28 12:46 ` bibo,mao
2006-11-28 23:29 ` Yoshinori K. Okuji
2006-11-29 1:55 ` bibo,mao
2006-11-29 2:37 ` Andrei E. Warkentin
2006-11-29 0:22 ` Johan Rydberg
2006-11-29 2:13 ` bibo,mao
2006-11-28 12:50 ` tgingold
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=4564B959.10102@sun.com \
--to=joe.bonasera@sun.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.