All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC, PATCH] Support for loading 32 bit ELF files for 64 bit linux-user
Date: Sun, 07 Oct 2007 19:35:52 +0200	[thread overview]
Message-ID: <1191778553.9976.32.camel@rapid> (raw)
In-Reply-To: <f43fc5580710071007s494b3c21ua51a23278925dbbe@mail.gmail.com>

On Sun, 2007-10-07 at 20:07 +0300, Blue Swirl wrote:
> On 10/7/07, Thiemo Seufer <ths@networkno.de> wrote:
> > Blue Swirl wrote:
> > [snip]
> > > Index: qemu/linux-user/qemu.h
> > > ===================================================================
> > > --- qemu.orig/linux-user/qemu.h       2007-10-07 10:50:05.000000000 +0000
> > > +++ qemu/linux-user/qemu.h    2007-10-07 10:51:09.000000000 +0000
> > > @@ -33,6 +33,7 @@
> > >          target_ulong    data_offset;
> > >          char            **host_argv;
> > >       int             personality;
> > > +        int             is_64bits;
> > >  };
> >
> > I think the 64bit-ness should be part of the personality. In the end,
> > we need a notion of the ABI in use, not just a specific cpu feature flag.
> 
> Good point. I've updated the patch to use the personality field
> instead, for that I updated the personality stuff.

Well done !
I really like this new version as it is far less intrusive. And I guess
it can quite easily be used by other 64 bits targets.

-- 
J. Mayer <l_indien@magic.fr>
Never organized

      reply	other threads:[~2007-10-07 17:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-07 12:45 [Qemu-devel] [RFC, PATCH] Support for loading 32 bit ELF files for 64 bit linux-user Blue Swirl
2007-10-07 14:01 ` J. Mayer
2007-10-07 14:38   ` Blue Swirl
2007-10-07 14:49     ` J. Mayer
2007-10-07 15:15       ` Blue Swirl
2007-10-07 15:46         ` J. Mayer
2007-10-07 16:21 ` Thiemo Seufer
2007-10-07 17:07   ` Blue Swirl
2007-10-07 17:35     ` J. Mayer [this message]

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=1191778553.9976.32.camel@rapid \
    --to=l_indien@magic.fr \
    --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 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.