From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Cc: Alexander Graf <alex@csgraf.de>
Subject: Re: [Qemu-devel] [PATCH] Make the ELF loader aware of backwards compatibility
Date: Sat, 28 Feb 2009 17:58:35 +0200 [thread overview]
Message-ID: <f43fc5580902280758j26b3ddf2l4451d7489bf20a52@mail.gmail.com> (raw)
In-Reply-To: <F98AE244-D968-4577-A02D-60A71A71E2DE@web.de>
On 2/28/09, Andreas Färber <andreas.faerber@web.de> wrote:
>
> Am 28.02.2009 um 16:30 schrieb Blue Swirl:
>
>
> > 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.
> >
>
> Same for ppc. To install Linux, you need to type "install64" at the prompt,
> the default "install" crashes on a G5.
Not exactly. I guess it's possible to construct a dual PPC32/PPC64
kernel for 32 bit mode because even though the MMUs are not
compatible, instruction sets are. But Sparc32 supervisor instructions
do wildly different things on a Sparc64.
next prev parent reply other threads:[~2009-02-28 15:58 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 [this message]
2009-03-11 23:32 ` Alexander Graf
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=f43fc5580902280758j26b3ddf2l4451d7489bf20a52@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=alex@csgraf.de \
--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).