All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christoph Egger" <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: Keir Fraser <keir@xensource.com>
Subject: Re: [PATCH] mkelf32: Correct sh_link
Date: Wed, 3 Jan 2007 16:38:08 +0100	[thread overview]
Message-ID: <200701031638.09068.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C1C17A3D.705B%keir@xensource.com>

On Wednesday 03 January 2007 16:20, Keir Fraser wrote:
> On 3/1/07 15:11, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> > On Wednesday 03 January 2007 14:57, Keir Fraser wrote:
> >> SHT_PROGBITS sections do not use the sh_link field. It's used by
> >> symbol-table sections, relocation-entry sections, and suchlike, of which
> >> we don't have any. And .shstrtab section is never linked to.
> >
> > Why do you strip the symbol table and re-add it in an unusual format
> > when linking the bootable ELF image? Is this a historical relict?
>
> No bootloader would load a symbol table for us (where would it load it? How
> would it tell us about it?), so we have to internalise it into the PROGBITS
> section somehow. Stealing the Linux code to do this made sense.

The multiboot header tells us where to find the symbol and string table.
Then we can load it ourself.

Look into the NetBSD code how this would work:
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/i386/include/multiboot.h?annotate=1.4
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/i386/i386/multiboot.c?annotate=1.9

;-)

Would you accept a patch, that makes XEN bootable as an ELF image with
ELF symbol-name and string tables? If yes, then I will work on this.

Christoph

  reply	other threads:[~2007-01-03 15:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03  9:30 [PATCH] mkelf32: Correct sh_link Christoph Egger
2007-01-03 13:57 ` Keir Fraser
2007-01-03 15:11   ` Christoph Egger
2007-01-03 15:14     ` Christoph Egger
2007-01-03 15:21       ` Keir Fraser
2007-01-03 15:20     ` Keir Fraser
2007-01-03 15:38       ` Christoph Egger [this message]
2007-01-03 16:21         ` Keir Fraser
2007-01-03 18:36           ` John Levon
2007-01-03 19:14             ` Keir Fraser
2007-01-03 19:20               ` John Levon
2007-01-03 20:06                 ` Keir Fraser
2007-01-03 20:11                   ` John Levon
2007-01-03 21:21                     ` Keir Fraser
2007-01-03 21:32                       ` John Levon
2007-01-03 21:40                         ` Keir Fraser
2007-01-04 14:34                           ` John Levon
2007-01-04  8:30                 ` Christoph Egger
2007-01-04  9:58                   ` Keir Fraser
2007-01-04 11:57                     ` Christoph Egger
2007-01-03 14:08 ` grel
2007-01-04  2:58   ` Mark Williamson

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=200701031638.09068.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=keir@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    /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.