From: Anthony Liguori <aliguori@us.ibm.com>
To: Scott Wood <scottwood@freescale.com>
Cc: qemu-devel@nongnu.org, "Alexander Graf" <agraf@suse.de>,
qemu-ppc@nongnu.org, aurel@aurel32.net,
"Andreas Färber" <afaerber@suse.de>,
"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 14:02:47 -0500 [thread overview]
Message-ID: <87li6dltpk.fsf@codemonkey.ws> (raw)
In-Reply-To: <1371149061.2028.18@snotra>
Scott Wood <scottwood@freescale.com> writes:
> On 06/13/2013 01:31:48 PM, Anthony Liguori wrote:
>> 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.
>
> Why?
I believe it's there only because libfdt used to be optional. libfdt is
no longer optional.
> As long as it's present in the default ppc64 build, you'll have a
> default machine. If a user makes a custom config without it,
> presumably they know they want to run some other machine, so why do you
> need a default?
That's fair.
Regards,
Anthony Liguori
>
> QEMU has too much mandatory stuff as is.
>
> -Scott
next prev parent reply other threads:[~2013-06-13 19:04 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
2013-06-13 18:44 ` Scott Wood
2013-06-13 19:02 ` Anthony Liguori [this message]
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=87li6dltpk.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 \
--cc=scottwood@freescale.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).