qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: "Eric Blake" <eblake@redhat.com>, "Ján Tomko" <jtomko@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Michael Roth" <mdroth@linux.vnet.ibm.com>,
	"Anthony Liguori" <aliguori@amazon.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] Should we have a 2.0-rc3 ?
Date: Thu, 10 Apr 2014 17:42:42 +0200	[thread overview]
Message-ID: <5346BBF2.4040600@suse.de> (raw)
In-Reply-To: <5346BB11.7070507@redhat.com>


On 10.04.14 17:38, Eric Blake wrote:
> On 04/10/2014 09:27 AM, Alexander Graf wrote:
>> Hrm, so what if we just ditch pre-2.0 support for PPC in libvirt? Then
>> it'd become
>>
>> if (machine_type == pc || machine_type == pseries || machine_type ==
>> ppce500)
>>    assume QEMU_CAPS_PCI_MULTIBUS
>> else ...
>>
>> and everyone is happy, no? :)
> No, because there (may be) people clamoring for (at least some specific
> machine types of) PPC support to be backported to pre-2.0 versions.

Then I'm happy if they die a painful death :).

> The point is that the pre-2.0 behavior is a mess of special casing,
> which can't be helped, but what CAN be helped is no NEW special casing
> without introspection.  We failed at adding the introspection in time,
> and the only other alternative to adding introspection is to change ALL
> machines at the same time; since neither of those can happen in time for
> 2.0, it leaves reverting the PPC change and letting 2.0 behave like
> pre-2.0 as the path with the fewest special casing requirements.

I really don't see how you would even remotely want to use pre-2.0 QEMU 
in production environments for PPC. Heck, we even get patch sets today 
that try to fix migration with libvirt that aren't even upstream yet :).


Alex

  reply	other threads:[~2014-04-10 15:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 11:17 [Qemu-devel] Should we have a 2.0-rc3 ? Peter Maydell
2014-04-10 11:24 ` Alexander Graf
2014-04-10 15:22   ` Michael S. Tsirkin
2014-04-10 11:49 ` Kevin Wolf
2014-04-10 12:44 ` Eric Blake
2014-04-10 12:46   ` Alexander Graf
2014-04-10 12:51     ` Eric Blake
2014-04-10 12:56       ` Alexander Graf
2014-04-10 13:41     ` Ján Tomko
2014-04-10 13:45       ` Alexander Graf
2014-04-10 15:02         ` Eric Blake
2014-04-10 15:27           ` Alexander Graf
2014-04-10 15:38             ` Eric Blake
2014-04-10 15:42               ` Alexander Graf [this message]
2014-04-11  8:01           ` Markus Armbruster
2014-04-11  8:37             ` Daniel P. Berrange
2014-04-10 15:26 ` Michael S. Tsirkin
2014-04-10 18:55 ` Cole Robinson
2014-04-10 21:30 ` Peter Maydell
2014-04-11 17:37 ` Peter Maydell
2014-04-11 22:55   ` Alexander Graf
2014-04-12  1:49   ` Paolo Bonzini
2014-04-12  8:48   ` Michael Tokarev

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=5346BBF2.4040600@suse.de \
    --to=agraf@suse.de \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=eblake@redhat.com \
    --cc=jtomko@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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).