qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <alex@csgraf.de>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] Make the ELF loader aware of backwards compatibility
Date: Thu, 12 Mar 2009 00:32:24 +0100	[thread overview]
Message-ID: <278E7B05-94BB-41D0-9F2B-EEE35B9D8DD2@csgraf.de> (raw)
In-Reply-To: <f43fc5580902280730o47bc2286gef0e4245d24f03eb@mail.gmail.com>


On 28.02.2009, at 16:30, Blue Swirl wrote:

> On 2/28/09, Alexander Graf <agraf@suse.de> wrote:
>> Most 64 bit architectures I'm aware of support running 32 bit code
>> of the same architecture as well.
>
> For Sparc64 this is only true for userland, kernel level code is not
> compatible at all. Sparc64 kernel can run Sparc64 and Sparc32
> binaries, but a Sparc32 kernel will crash on Sparc64.
>
>>  /* Load a 32 bit BIOS also on 64 bit machines */
>> -#if defined (TARGET_PPC64) && defined(CONFIG_USER_ONLY)
>> +#if defined (TARGET_PPC64)
>>  #define ELF_MACHINE     EM_PPC64
>>  #else
>>  #define ELF_MACHINE     EM_PPC
>
> The comment should be removed with the hack.

I agree.

Any functional issues with this patch? -kernel for ppc64 still doesn't  
work with current SVN :-).

Alex

  parent reply	other threads:[~2009-03-11 23:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-28 15:03 [Qemu-devel] [PATCH] Make the ELF loader aware of backwards compatibility Alexander Graf
2009-02-28 15:30 ` Blue Swirl
2009-02-28 15:40   ` Andreas Färber
2009-02-28 15:58     ` Blue Swirl
2009-03-11 23:32   ` Alexander Graf [this message]
2009-03-13 17:32     ` Blue Swirl
2009-03-13 21:17     ` Blue Swirl

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=278E7B05-94BB-41D0-9F2B-EEE35B9D8DD2@csgraf.de \
    --to=alex@csgraf.de \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.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 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).