qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "Alexander Graf" <agraf@suse.de>, "Andreas Färber" <afaerber@suse.de>
Cc: aurel@aurel32.net, qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] target-ppc: Change default machine for 64-bit
Date: Thu, 13 Jun 2013 13:31:48 -0500	[thread overview]
Message-ID: <878v2d276z.fsf@codemonkey.ws> (raw)
In-Reply-To: <437ECAF8-6CF1-4015-96FA-F1CE0400A968@suse.de>

Alexander Graf <agraf@suse.de> writes:

> On 17.05.2013, at 09:42, Andreas Färber wrote:
>
>> Am 17.05.2013 06:25, schrieb David Gibson:
>>> Currently, for qemu-system-ppc64, the default machine type is 'mac99'.
>>> Since the mac99 machine is not being actively maintained, and shows quite
>>> a few signs of bitrot,
>> 
>> Please be more specific than making such general claims in a commit
>> message! As the default machine it certainly compiles, so where are you
>> seeing bitrot? The DEC bridge cleanup that I once started kind of
>> depends on the PCI cleanup you recently looked into.
>
> The mac99 machine for 64bit is actually worse than anything bitrot
> could give you. It emulates a machine that in its form never possibly
> could have existed in real hardware, which makes it very fragile and
> dependent on the guest's mercy to handle this gracefully.

I'll note that we have a CONFIG_PSERIES today.  I'd suggest getting rid
of it first before making pseries the default.

I still think spapr would be a better name than pseries FWIW since
that's what it's referred to in the code.

Regards,

Anthony Liguori

>
> Given the current state and amount of development on the pseries target, I think it makes sense to declare that as the default for qemu-system-ppc64.
>
> I would still love to see -M mac99 emulate a proper U2 or U1 based system for 32bit. And I would also love to see a real U4 based emulation model come up for qemu-system-ppc64. But I doubt I'll have time to work on either :).
>
>
> Alex

  reply	other threads:[~2013-06-13 18:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17  4:25 [Qemu-devel] [PATCH] target-ppc: Change default machine for 64-bit David Gibson
2013-05-17  4:36 ` [Qemu-devel] [Qemu-ppc] " Benjamin Herrenschmidt
2013-05-17  5:17   ` David Gibson
2013-05-17  7:17     ` Peter Maydell
2013-05-17  7:22     ` Alexander Graf
2013-05-17  7:42 ` [Qemu-devel] " Andreas Färber
2013-05-17  8:01   ` [Qemu-devel] [Qemu-ppc] " Benjamin Herrenschmidt
2013-06-13 13:49   ` Alexander Graf
2013-06-13 18:31     ` Anthony Liguori [this message]
2013-06-13 18:44       ` Scott Wood
2013-06-13 19:02         ` Anthony Liguori
2013-06-13 20:44           ` Peter Maydell
2013-06-14 16:15           ` Andreas Färber
2013-06-14 14:28     ` Andreas Färber
2013-06-14 21:58       ` Benjamin Herrenschmidt
2013-06-16 10:20       ` 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=878v2d276z.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aurel@aurel32.net \
    --cc=david@gibson.dropbear.id.au \
    --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).