From: Greg Kurz <groug@kaod.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "David Gibson" <david@gibson.dropbear.id.au>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
"Murilo Opsfelder Araújo" <muriloo@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 0/2] Clean up the ppc default configs
Date: Mon, 15 Jan 2018 12:05:43 +0100 [thread overview]
Message-ID: <20180115120543.1f825292@bahia.lan> (raw)
In-Reply-To: <1516008655-31732-1-git-send-email-thuth@redhat.com>
On Mon, 15 Jan 2018 10:30:53 +0100
Thomas Huth <thuth@redhat.com> wrote:
> ppc64-softmmu is a superset of ppc-softmmu which in turn is a superset
Hi Thomas,
Per curiosity. I understand that a 64-bit ppc CPU is expected to support
32-bit ppc code, but does QEMU really need to emulate setups that likely
never existed in real life (like a PowerMac G5 or a pSeries with an
internal floppy disk controller for example) ?
I ask because Murilo and I had a chat about removing CONFIG_FDC from
default-configs/ppc64-softmmu.mak the other day :)
Cheers,
--
Greg
> of ppcemb-softmmu. But since the config files are currently independent
> from each other, we missed to define some CONFIG switches in the super-
> sets: CONFIG_SUNGEM is missing from the ppc64-softmmu config, and the
> CONFIG_IDE_SII3112 switch is only defined in ppcemb-softmmu.
>
> Let's fix this by including the subsets instead of duplicating all the
> switches all over the place.
>
> (off-topic question: Do we still need a separate ppcemb-softmmu nowadays?
> It seemed to be useful 10 years ago when everybody was doing KVM on
> embedded PPC, but these days seem to be pretty much over now, so IMHO
> just using ppc-softmmu for embedded should be enough nowadays? We could
> save quite some compilation- and "make check"-time if we could finally get
> rid of ppcemb-softmmu again...)
>
> Thomas Huth (2):
> default-configs/ppc64-softmmu: Include 32-bit configs instead of
> copying them
> default-configs/ppc-softmmu: Restructure the switches according to the
> machines
>
> default-configs/ppc-softmmu.mak | 59 +++++++++++++++----------------------
> default-configs/ppc64-softmmu.mak | 61 +++++----------------------------------
> 2 files changed, 32 insertions(+), 88 deletions(-)
>
next prev parent reply other threads:[~2018-01-15 11:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 9:30 [Qemu-devel] [PATCH 0/2] Clean up the ppc default configs Thomas Huth
2018-01-15 9:30 ` [Qemu-devel] [PATCH 1/2] default-configs/ppc64-softmmu: Include 32-bit configs instead of copying them Thomas Huth
2018-01-15 9:30 ` [Qemu-devel] [PATCH 2/2] default-configs/ppc-softmmu: Restructure the switches according to the machines Thomas Huth
2018-01-15 11:05 ` Greg Kurz [this message]
2018-01-15 14:26 ` [Qemu-devel] [Qemu-ppc] [PATCH 0/2] Clean up the ppc default configs Thomas Huth
2018-01-15 12:00 ` BALATON Zoltan
2018-01-15 14:38 ` Thomas Huth
2018-01-16 10:41 ` Thomas Huth
2018-01-16 10:51 ` Peter Maydell
2018-01-16 11:10 ` Thomas Huth
2018-01-15 13:01 ` [Qemu-devel] " Peter Maydell
2018-01-15 14:42 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2018-01-16 1:19 ` David Gibson
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=20180115120543.1f825292@bahia.lan \
--to=groug@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=muriloo@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).