All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Fabrice Bellard <fabrice@bellard.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: fix run of 32 bits Linux executables on 64 bits targets
Date: Thu, 11 Oct 2007 16:17:24 +0100	[thread overview]
Message-ID: <20071011151724.GD3379@networkno.de> (raw)
In-Reply-To: <470D1C9A.2000505@bellard.org>

Fabrice Bellard wrote:
> Thiemo Seufer wrote:
>> Fabrice Bellard wrote:
>>> J. Mayer wrote:
>>>> Following the patches done for elfload32, it appeared to me that there
>>>> were still problems that would prevent 32 bits executables to run on 64
>>>> bits target in linux user mode emulation.
>>>> [...]
>>> Are you sure it is a good idea to try to add 32 bit executable support to 
>>> a 64 bit target ? In the end you will need to write a 64 bit to 32 bit 
>>> linux syscall converter which would mean duplicating all the linux-user 
>>> code of the corresponding 32 bit target (think of ioctls with strutures, 
>>> signals frames, etc...).
>> I would think this feature will be limited to platforms which can handle
>> 32bit and 64bit binaries with a single personality.
>
> I am not sure it is a common case !
>
> However, I suggest to emulate a 32 bit user linux system with a 64 bit 
> guest CPU running in 32 bit compatibily mode. It would be useful to test 64 
> bit CPUs in 32 bit compatibility mode. The only required modification in 
> linux user is to rename target_ulong so that it can have a different size 
> of the CPU word default size.

Doesn't work for MIPS64, since it doesn't quite have a compatibility mode
in the traditional sense. It needs to retain 64bit register width when
running N32 ABI binaries. (Thus the somewhat odd overrides I added for
the preliminary N32 support.)


Thiemo

  parent reply	other threads:[~2007-10-11 15:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10  7:42 [Qemu-devel] RFC: fix run of 32 bits Linux executables on 64 bits targets J. Mayer
2007-10-10  8:18 ` Fabrice Bellard
2007-10-10 16:09   ` Blue Swirl
2007-10-10 17:49   ` Thiemo Seufer
2007-10-10 18:40     ` Fabrice Bellard
2007-10-10 19:02       ` Blue Swirl
2007-10-10 21:51         ` J. Mayer
2007-10-11 15:17       ` Thiemo Seufer [this message]
2007-10-11 15:47         ` Blue Swirl
2007-10-11 16:00           ` Thiemo Seufer
2007-10-11 19:26       ` Blue Swirl
2007-10-11 22:00         ` J. Mayer
2007-10-12 16:21           ` Blue Swirl
2007-10-12 18:42             ` Thiemo Seufer
2007-10-12 19:37               ` Blue Swirl
2007-10-12 20:24                 ` Thiemo Seufer
2007-10-10 16:01 ` Blue Swirl
2007-10-10 18:42   ` J. Mayer

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=20071011151724.GD3379@networkno.de \
    --to=ths@networkno.de \
    --cc=fabrice@bellard.org \
    --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 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.