From: Aaron Sierra <asierra@xes-inc.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Laurent Vivier <laurent@vivier.eu>,
Riku Voipio <riku.voipio@iki.fi>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] linux-user: Support explicit targets for PowerPC
Date: Tue, 7 Nov 2017 09:25:16 -0600 (CST) [thread overview]
Message-ID: <1590616620.194475.1510068316265.JavaMail.zimbra@xes-inc.com> (raw)
In-Reply-To: <CAFEAcA8kXjH5dSM6KCGX5gfgJWJMAymz=D3BTMxjLwZQ7_s5hg@mail.gmail.com>
----- Original Message -----
> From: "Peter Maydell" <peter.maydell@linaro.org>
> Sent: Tuesday, November 7, 2017 3:29:21 AM
> On 7 November 2017 at 06:57, Laurent Vivier <laurent@vivier.eu> wrote:
>> Le 07/11/2017 à 03:50, Aaron Sierra a écrit :
>>> Enable building PowerPC targets supporting a specific CPU, without
>>> having to set QEMU_CPU via the environment. For example these build
>>> targets (and many more) become available:
>>>
>>> qemu-ppc.e500mc
>>> qemu-ppc.e500v2
>>> qemu-ppc.e5500
>>> qemu-ppc.e600
>>> qemu-ppc.e6500
>>>
>>> These (statically compiled) binaries have proven useful for emulating
>>> PowerPC CPUs within Docker containers, where it's hard to reliably
>>> define environment variables that are available for every process.
>>
>> I agree with you.
>>
>> I have patches to do that for years, perhaps we can merge our both
>> solutions to have something working:
>>
>> linux-user: define default cpu model in configure instead of
>> linux-user/main.c
>> https://github.com/vivier/qemu-m68k/commit/1488df8c9fa3a5b099bbc4f41c077a6c69305cc2
>>
>> linux-user: specify the cpu model during configure
>> https://github.com/vivier/qemu-m68k/commit/496f804fd97d5f0ef26da1090e1d95ad15bcc50e
>>
>> The part missing in my series is to rename the qemu binaries with the
>> suffix of the default CPU.
>
> I don't really like this -- it means we'll end up with a huge
> extra range of executables, and every time a new CPU type is
> added a new binary has to be plumbed in to our own 'make
> install' machinery and into every distro's packaging.
Peter,
Yes, there is a huge new range of binaries (there's actually no practical
upper bound), but I don't really anticipate this feature being used en masse
by distributions. I do see it as a very useful tool for developers to be
able to leverage when the situation arises.
-Aaron S.
> The 'look at argv[0]' approach is perhaps a bit more
> palatable. Or you could just write and use wrapper
> scripts.
>
> I take it there's no good "-cpu any" option for PPC that
> would run all these binaries?
>
> thanks
> -- PMM
next prev parent reply other threads:[~2017-11-07 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 2:50 [Qemu-devel] [PATCH] linux-user: Support explicit targets for PowerPC Aaron Sierra
2017-11-07 4:48 ` no-reply
2017-11-07 4:51 ` no-reply
2017-11-07 6:57 ` Laurent Vivier
2017-11-07 9:29 ` Peter Maydell
2017-11-07 9:41 ` Laurent Vivier
2017-11-07 15:25 ` Aaron Sierra [this message]
2017-11-07 9:24 ` Laurent Vivier
2017-11-07 15:20 ` Aaron Sierra
2017-11-07 15:24 ` Peter Maydell
2017-11-07 15:28 ` Aaron Sierra
2017-11-07 15:27 ` Laurent Vivier
2017-11-07 15:42 ` Aaron Sierra
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=1590616620.194475.1510068316265.JavaMail.zimbra@xes-inc.com \
--to=asierra@xes-inc.com \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).