From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58539) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WYH4I-0002Pg-Hf for qemu-devel@nongnu.org; Thu, 10 Apr 2014 11:39:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WYH4C-00079f-1N for qemu-devel@nongnu.org; Thu, 10 Apr 2014 11:39:10 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38758) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WYH4B-00079b-O7 for qemu-devel@nongnu.org; Thu, 10 Apr 2014 11:39:03 -0400 Message-ID: <5346BB11.7070507@redhat.com> Date: Thu, 10 Apr 2014 09:38:57 -0600 From: Eric Blake MIME-Version: 1.0 References: <5346921A.2050705@redhat.com> <4FBBA28F-184E-45A4-A7B8-6F4ED4EFC205@suse.de> <53469F8D.2040808@redhat.com> <5346A07B.9070608@suse.de> <5346B2A3.1080900@redhat.com> <5346B84B.4030506@suse.de> In-Reply-To: <5346B84B.4030506@suse.de> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Mqm2jD6FvxOw6r35LDXrDGfdf9cihfwCm" Subject: Re: [Qemu-devel] Should we have a 2.0-rc3 ? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf , =?UTF-8?B?SsOhbiBUb21rbw==?= Cc: Peter Maydell , "Michael S. Tsirkin" , QEMU Developers , Michael Roth , Anthony Liguori , Paolo Bonzini , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Mqm2jD6FvxOw6r35LDXrDGfdf9cihfwCm Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 04/10/2014 09:27 AM, Alexander Graf wrote: >=20 > Hrm, so what if we just ditch pre-2.0 support for PPC in libvirt? Then > it'd become >=20 > if (machine_type =3D=3D pc || machine_type =3D=3D pseries || machine_ty= pe =3D=3D > ppce500) > assume QEMU_CAPS_PCI_MULTIBUS > else ... >=20 > 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. 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. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --Mqm2jD6FvxOw6r35LDXrDGfdf9cihfwCm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJTRrsRAAoJEKeha0olJ0Nq1W8H/1jUHppGsi2UlUXoyN04gtE2 JnoLyOYcyvweqri420mUSDn9SBlPen2SjZayYsyo68QJ7Gb3jvZB3iRNn6k/HN+J fUI7dkxLiqUSKY0BHHF49rBk6OV2/vyTRXrzDzUwkW3iGPc2XVP5xREzBOtd7hC9 7AVxkvslceHHYDlfqtqy6ktpTqSgbddrE/zYx2qQ/46lK/4yMGdd+nUFs93AG3Bi MdakNOUT4uWFZKDSALYoMHZX3eE6oa/Y1MO5KLp7Nxi/JYWyS7EmuQLd7uMjVIsH qi+Ijbagk3UBxLC00XIgrdLyZAGxjl8rOGibYvYPe93W53sCMezFkSUL4gI4zIM= =r02w -----END PGP SIGNATURE----- --Mqm2jD6FvxOw6r35LDXrDGfdf9cihfwCm--