LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: linux-kernel@vger.kernel.org, Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: PATCH/RFC: bzImage payload as compressed ELF file.
Date: Mon, 28 Jan 2008 15:20:03 -0800 [thread overview]
Message-ID: <479E6323.5030200@zytor.com> (raw)
In-Reply-To: <1201560133.17053.36.camel@cthulhu.hellion.org.uk>
Ian Campbell wrote:
>
> What would be the preferred way of allowing bootloaders/domain builders
> to find the compressed payload? Tacking the offset from the end onto the
> end as I have done for the moment seems pretty skanky...
>
As Jeremy already mentioned, putting a pointer to the compressed ELF
image in the bzImage header (and bumping the version number to 2.08) is
the right way to go about it. The compression format (for now, always
gzip) can then be identified in the usual way via compression format
magic number.
As I've previously expressed, I'm much happier with this approach than
having the compressor portion itself be an ELF image, so I'm happy to
see this patch. However, I think it needs to ride a cycle in -mm, so
although I didn't see any problems from a cursory look I might not get a
chance to do a detailed review until the merge window is over.
-hpa
next prev parent reply other threads:[~2008-01-28 23:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 22:42 Ian Campbell
2008-01-28 22:54 ` Jeremy Fitzhardinge
2008-01-29 9:34 ` Ian Campbell
2008-01-29 17:54 ` Jeremy Fitzhardinge
2008-01-29 18:05 ` H. Peter Anvin
2008-01-29 18:31 ` Jeremy Fitzhardinge
2008-01-29 18:34 ` H. Peter Anvin
2008-01-29 20:38 ` Ian Campbell
2008-01-29 21:50 ` H. Peter Anvin
2008-01-29 21:55 ` Ian Campbell
2008-01-29 22:09 ` H. Peter Anvin
2008-01-28 23:20 ` H. Peter Anvin [this message]
2008-01-29 9:31 ` Ian Campbell
2008-02-01 13:10 ` Ingo Molnar
2008-02-01 18:05 ` H. Peter Anvin
2008-02-01 18:15 ` 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=479E6323.5030200@zytor.com \
--to=hpa@zytor.com \
--cc=ijc@hellion.org.uk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: PATCH/RFC: bzImage payload as compressed ELF file.' \
/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).