LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ian Campbell <ijc@hellion.org.uk>,
	linux-kernel@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: PATCH/RFC: bzImage payload as compressed ELF file.
Date: Tue, 29 Jan 2008 10:34:30 -0800	[thread overview]
Message-ID: <479F71B6.2010305@zytor.com> (raw)
In-Reply-To: <479F70E9.40905@goop.org>

Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
>> It's also easy enough to either use objdump -h or nm to extract info 
>> from vmlinux; or for some of the simpler stuff, just parse the ELF 
>> directly (perhaps using libelf).
>>
>> There is also the -R option to ld, which imports symbols from one 
>> executable into another. 
> 
> Yes, I used -R, though it was necessary to generate a copy of vmlinux 
> with a filtered symbol list to prevent collisions.  But I'm not sure any 
> of this is necessary with Ian's approach.
> 

Probably isn't.  He just need the start and possibly length of the 
payload section, which should be objdump -h or equivalently reading the 
ELF section table.

	-hpa

  reply	other threads:[~2008-01-29 18:38 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 [this message]
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
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=479F71B6.2010305@zytor.com \
    --to=hpa@zytor.com \
    --cc=ebiederm@xmission.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).