From: Laurent Vivier <laurent@vivier.eu>
To: Aaron Sierra <asierra@xes-inc.com>, Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: Support explicit targets for PowerPC
Date: Tue, 7 Nov 2017 07:57:59 +0100 [thread overview]
Message-ID: <03986f7a-f1f8-751a-4967-ab7d1a5093fd@vivier.eu> (raw)
In-Reply-To: <492245211.936616.1510023015797.JavaMail.zimbra@xes-inc.com>
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.
Thanks,
Laurent
next prev parent reply other threads:[~2017-11-07 6:58 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 [this message]
2017-11-07 9:29 ` Peter Maydell
2017-11-07 9:41 ` Laurent Vivier
2017-11-07 15:25 ` Aaron Sierra
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=03986f7a-f1f8-751a-4967-ab7d1a5093fd@vivier.eu \
--to=laurent@vivier.eu \
--cc=asierra@xes-inc.com \
--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).