LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Etienne Lorrain <etienne_lorrain@yahoo.fr>,
linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] Compressed ia32 ELF file generation for loading by Gujin 1/3
Date: Tue, 6 Feb 2007 12:03:21 +0530 [thread overview]
Message-ID: <20070206063320.GA26462@in.ibm.com> (raw)
In-Reply-To: <45C81D5B.3050408@zytor.com>
On Mon, Feb 05, 2007 at 10:16:59PM -0800, H. Peter Anvin wrote:
> Vivek Goyal wrote:
> >
> >I don't know much about Gujin, but advantage here seems to be that it has
> >capability to load elf files and that's why the attempt to turn kernel
> >binary
> >into a compressed elf image. Why don't we then simply add an ELF header to
> >bzImage and Gujin and any ELF loader including Gujin, should be able to
> >load
> >it? (As Eric had done in one of the implementations in the past?) Why to
> >create the new infrastructure?
> >
>
> Well, Gujin wants additional code too.
>
> Putting an ELF header on bzImage broke some bootloaders (GRUB, I
> believe), so that's not going to happen again. See the relocatable
> bzImage thread...
>
That time, grub was working fine but lilo had broken on one of Andrew's
machine. I could not reproduce the problem on my setup and had no clue what
was the issue. Hence got rid of ELF header from bzImage which was non-essential
stuff for relocatable kernel. But that issue should be fixable.
Thanks
Vivek
next prev parent reply other threads:[~2007-02-06 6:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 23:56 Etienne Lorrain
2007-02-06 0:37 ` H. Peter Anvin
2007-02-06 5:25 ` Vivek Goyal
2007-02-06 6:16 ` H. Peter Anvin
2007-02-06 6:33 ` Vivek Goyal [this message]
2007-02-06 6:38 ` H. Peter Anvin
2007-02-06 6:51 ` Vivek Goyal
2007-02-06 7:24 ` Eric W. Biederman
2007-02-06 15:50 ` H. Peter Anvin
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=20070206063320.GA26462@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=ebiederm@xmission.com \
--cc=etienne_lorrain@yahoo.fr \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH] Compressed ia32 ELF file generation for loading by Gujin 1/3' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).