From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Benjamin Herrenschmidt <benh@au1.ibm.com>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
Alexander Graf <agraf@suse.de>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/1] Support ppc64le binfmt registration
Date: Thu, 28 Aug 2014 01:09:46 +0200 [thread overview]
Message-ID: <20140827230945.GB28935@mail.hallyn.com> (raw)
In-Reply-To: <20140827230524.GA28935@mail.hallyn.com>
Quoting Serge E. Hallyn (serge@hallyn.com):
> Quoting Alexander Graf (agraf@suse.de):
> >
> >
> > On 27.08.14 23:35, Peter Maydell wrote:
> > > On 27 August 2014 22:30, Alexander Graf <agraf@suse.de> wrote:
> > >>
> > >>
> > >> On 27.08.14 21:01, Peter Maydell wrote:
> > >>> [adding qemu-ppc]
> > >>>
> > >>> On 27 August 2014 19:45, Serge E. Hallyn <serge@hallyn.com> wrote:
> > >>>> Quoting Peter Maydell (peter.maydell@linaro.org):
> > >>>>> On 27 August 2014 18:55, Serge E. Hallyn <serge@hallyn.com> wrote:
> > >>>>>> This is a part of a patch proposed by jaejunh at
> > >>>>>> https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1358268
> > >>>>>> which enables running ppc64le binaries through qemu-user.
> > >>>>>
> > >>>>> I'm confused -- wouldn't these be handled by the existing
> > >>>>> "ppc64le" support?
> > >>>
> > >>>> It looks to me like the point was to add a TARGET_ABI32=y
> > >>>> version (and I dunno, something about CONFIG_LIBDECNUMBER=y
> > >>>> for 32-bit).
> > >>>
> > >>> Wouldn't that be a "ppc64leabi32" target?
> > >>
> > >> There is no LE support for 32bit on PPC :).
> > >
> > > ...in that case what is the original bug reporter actually
> > > asking for?
> >
> > Not sure - the only thing that remotely resembles what he's describing
> > would be if you enable the 32bit personality:
> >
> > $ /uname-a.sh
> > Linux tempranillo 3.17.0-rc1-2-default+ #1 SMP Thu Jan 1 01:04:00 CET
> > 1970 ppc64le ppc64le ppc64le GNU/Linux
> >
> > $ perl -e 'syscall(136, 8); exec "/uname-a.sh"'
> > Linux tempranillo 3.17.0-rc1-2-default+ #1 SMP Thu Jan 1 01:04:00 CET
> > 1970 ppcle ppcle ppcle GNU/Linux
> >
> > but that doesn't mean that there is an actual ABI change. The ABI is
> > still ppc64le, as all binaries are still running in 64bit mode.
> >
> > So before we add anything to QEMU, I would like to first see someone
> > point me to kernel patches that actually enable LE on Linux for 32bit
> > user space. So far I'm not aware of any (and I doubt it makes much sense).
>
> Thanks, guys, I'll ping him for that.
(Fwiw my reading of the original bug description is that in fact he
is working on the kernel patch in question)
next prev parent reply other threads:[~2014-08-27 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 17:55 [Qemu-devel] [PATCH 1/1] Support ppc64le binfmt registration Serge E. Hallyn
2014-08-27 18:20 ` Peter Maydell
2014-08-27 18:45 ` Serge E. Hallyn
2014-08-27 19:01 ` Peter Maydell
2014-08-27 21:30 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-08-27 21:35 ` Peter Maydell
2014-08-27 22:40 ` Alexander Graf
2014-08-27 23:05 ` Serge E. Hallyn
2014-08-27 23:09 ` Serge E. Hallyn [this message]
2014-08-28 7:42 ` Peter Maydell
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=20140827230945.GB28935@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=agraf@suse.de \
--cc=benh@au1.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).