qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Thomas Huth <thuth@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-ppc@nongnu.org, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 0/2] Clean up the ppc default configs
Date: Tue, 16 Jan 2018 12:19:35 +1100	[thread overview]
Message-ID: <20180116011935.GA30352@umbus.fritz.box> (raw)
In-Reply-To: <e83d019b-2a88-f4e4-4be8-79f93731b549@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]

On Mon, Jan 15, 2018 at 03:42:09PM +0100, Thomas Huth wrote:
> On 15.01.2018 14:01, Peter Maydell wrote:
> > On 15 January 2018 at 09:30, Thomas Huth <thuth@redhat.com> wrote:
> >> (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...)
> > 
> > There are some specific differences guarded by TARGET_PPCEMB, like
> > the way it has a different TARGET_PAGE_BITS value, and some code
> > in target/ppc/kvm.c related to telling KVM about interrupts. You
> > would need to make those all be runtime decisions I assume.
> 
> True ... but while we maybe could turn those into runtime checks, I now
> rather think it's maybe better to go the other way round: Maybe we
> should not include each and everything into ppc64-softmmu, but put the
> embedded stuff only in ppcemb-softmmu and the 32-bit stuff only in
> ppc-softmmu instead? That way we could, for example, also make the
> output of "-cpu help" and "-device help" a little bit more user friendly...

I tend to agree.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-01-16  1:22 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 ` [Qemu-devel] [Qemu-ppc] [PATCH 0/2] Clean up the ppc default configs Greg Kurz
2018-01-15 14:26   ` 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 [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=20180116011935.GA30352@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=peter.maydell@linaro.org \
    --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).