All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Paul Brook <paul@codesourcery.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, Goswin von Brederlow <goswin-v-b@web.de>
Subject: Re: [Qemu-devel] Support for multiboot images in elf64 (EM_X86_64) format
Date: Thu, 09 Feb 2012 14:07:56 +0100	[thread overview]
Message-ID: <87liocqhn7.fsf@frosties.localnet> (raw)
In-Reply-To: <201202090035.12216.paul@codesourcery.com> (Paul Brook's message of "Thu, 9 Feb 2012 00:35:11 +0000")

Paul Brook <paul@codesourcery.com> writes:

>> > starting your own toy kernel is a fun thing to do and there are many
>> > tutorials out there on how to do it. Unfortunately when one wants to
>> > write a kernel in 64bit it becomes much harder because one can't
>> > compile 64bit code as elf32 image and converting a elf64 image to
>> > elf32 format is a major hassle and looses debug information and symbols.
>
> So just have two versions of your image:
> - The elf64 image that has debug info, symbols, etc.  Point gdb at this.
> - An elf32 image that you give to the bootloader (in this case kvm)
>
> Generating the latter from the former is a trivial objcopy invocation.

Is it? I tried for a while and couldn't figure it out. I checked how
linux does it and it does quite a dance to achieve it.

> The bootloader variant only needs enough information to get the loadable 
> sections into memory.  We don't care about non-resident clutter like debug 
> info or symbols.  Anything that cares about those will be using the full elf64 
> image.
>
> This is all standard practice.  I don't think I've never actually used a 
> system where the image loaded by the target is the same file as the one that 
> comes out of the linker and is used by the debugger.
>
>> Yes, this is why I asked about support in other software.  If each
>> bootloader implements a different custom method then it will be a pain
>> to run your binary on real hardware in the future.  It's worth at
>> least checking their source first - maybe there is already a similar
>> code path that we can be compatible with, hence making life easier for
>> developers who want to play with 64-bit payloads in multiboot
>> executables.
>
> The whole idea of entering a 64-bit image in 32-bit mode seems distinctly 
> sketchy.  Surely it'd make more sense to define a 64-bit multiboot variant and 
> do the job properly.
>
> Paul

That will happen in multiboot2 format and is a much larger patch,
including a complete new boot rom actualy. I do have patches for that
too but there aren't complete yet. I only support the bare minimum of
the multiboot2 specs so far.

MfG
        Goswin

  reply	other threads:[~2012-02-09 13:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 17:38 [Qemu-devel] Support for multiboot images in elf64 (EM_X86_64) format Goswin von Brederlow
2012-02-06 12:38 ` Stefan Hajnoczi
2012-02-08  9:53   ` Goswin von Brederlow
2012-02-08 11:30     ` Kevin Wolf
2012-02-08 12:06     ` Stefan Hajnoczi
2012-02-09  0:35       ` Paul Brook
2012-02-09 13:07         ` Goswin von Brederlow [this message]
2012-02-09 13:36           ` Paul Brook
2012-02-09 15:38             ` Goswin von Brederlow
2012-02-09 16:01               ` Paul Brook

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=87liocqhn7.fsf@frosties.localnet \
    --to=goswin-v-b@web.de \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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.