All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Vivek Goyal <vgoyal@in.ibm.com>,
	Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@suse.de>,
	v12n <virtualization@lists.linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 6/7] i386: make the bzImage payload an ELF file
Date: Wed, 06 Jun 2007 17:08:54 -0700	[thread overview]
Message-ID: <46674C96.7090104@zytor.com> (raw)
In-Reply-To: <466749C8.2010700@goop.org>

Jeremy Fitzhardinge wrote:
> 
> I'm not sure I fully understand the mechanism you're proposing.  You
> have the 16-bit setup code, the 32-bit decompressor, and an ELF.gz. Once
> the decompressor has extracted the actual ELF file, are you proposing
> that it properly parse the ELF file and follow its instuctions to put
> the segments in the appropriate places, or are you assuming that the
> decompressor can just skip that part and plonk the ELF file where it wants?
> 
> In other words, do you see the Phdrs as being descriptive or prescriptive?
> 

I was thinking prescriptive, having the decompressor read the output
stream and interpret it as ELF.  I guess a descriptive approach could be
made to work, too (I haven't really thought about that avenue of
approach), but the prescriptive model seems more powerful, at least to me.

	-hpa

  parent reply	other threads:[~2007-06-07  0:09 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 22:58 [PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting Jeremy Fitzhardinge
2007-06-06 22:58 ` Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 1/7] update boot spec to 2.07 Jeremy Fitzhardinge
2007-06-06 22:58   ` Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 2/7] add WEAK() for creating weak asm labels Jeremy Fitzhardinge
2007-06-06 22:58   ` Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 3/7] allow linux/elf.h to be included in assembler Jeremy Fitzhardinge
2007-06-06 22:58   ` Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 4/7] define ELF notes for adding to a boot image Jeremy Fitzhardinge
2007-06-06 22:58   ` Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 5/7] i386: clean up bzImage generation Jeremy Fitzhardinge
2007-06-06 22:58   ` Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 6/7] i386: make the bzImage payload an ELF file Jeremy Fitzhardinge
2007-06-06 22:58   ` Jeremy Fitzhardinge
2007-06-06 23:41   ` H. Peter Anvin
2007-06-06 23:41     ` H. Peter Anvin
2007-06-06 23:56     ` Jeremy Fitzhardinge
2007-06-06 23:56     ` Jeremy Fitzhardinge
2007-06-07  0:08       ` H. Peter Anvin
2007-06-07  0:08       ` H. Peter Anvin [this message]
2007-06-07  0:20         ` Jeremy Fitzhardinge
2007-06-07  0:20         ` Jeremy Fitzhardinge
2007-06-07  0:42           ` H. Peter Anvin
2007-06-07  0:42           ` H. Peter Anvin
2007-06-07  1:01             ` Jeremy Fitzhardinge
2007-06-07  1:01             ` Jeremy Fitzhardinge
2007-06-08  3:49             ` Vivek Goyal
2007-06-08  3:49             ` Vivek Goyal
2007-06-08  4:01               ` H. Peter Anvin
2007-06-08  4:01               ` H. Peter Anvin
2007-06-07  1:47     ` Rob Landley
2007-06-07  1:47     ` Rob Landley
2007-06-07  1:54       ` H. Peter Anvin
2007-06-07  1:54         ` H. Peter Anvin
2007-06-07 16:08         ` Rob Landley
2007-06-07 16:08         ` Rob Landley
2007-06-07 16:14           ` H. Peter Anvin
2007-06-07 16:14             ` H. Peter Anvin
2007-06-06 22:58 ` [PATCH RFC 7/7] i386: paravirt boot sequence Jeremy Fitzhardinge
2007-06-06 22:58   ` Jeremy Fitzhardinge

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=46674C96.7090104@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@suse.de \
    --cc=ebiederm@xmission.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=vgoyal@in.ibm.com \
    --cc=virtualization@lists.linux-foundation.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.