From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:59767) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ufzgp-0006Zl-BY for qemu-devel@nongnu.org; Fri, 24 May 2013 17:38:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ufzgn-0005Fy-Ct for qemu-devel@nongnu.org; Fri, 24 May 2013 17:38:19 -0400 Message-ID: <519FDDBD.7030201@redhat.com> Date: Fri, 24 May 2013 15:38:05 -0600 From: Eric Blake MIME-Version: 1.0 References: <1369066884-431-1-git-send-email-peter.maydell@linaro.org> <519A50EE.8040804@redhat.com> <871u8zp34w.fsf@codemonkey.ws> <87y5b7hyuo.fsf@codemonkey.ws> In-Reply-To: <87y5b7hyuo.fsf@codemonkey.ws> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="----enig2UOFFUIDGOWADBPSTPTFB" Subject: Re: [Qemu-devel] [libvirt] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Peter Maydell , John Rigby , patches@linaro.org, qemu-trivial@nongnu.org, qemu-devel@nongnu.org, Libvirt , Paolo Bonzini , =?UTF-8?B?RsOkcmJlcg==?= This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2UOFFUIDGOWADBPSTPTFB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 05/22/2013 08:29 AM, Anthony Liguori wrote: > Peter Maydell writes: >=20 >> On 22 May 2013 14:15, Anthony Liguori wrote: >>> Paolo Bonzini writes: >>>> You >>>> don't need to know what targets were supported in the version that y= ou >>>> compiled from. Only one target is supported in this executable >>>> anyway. >>> >>> It seems useful to me. One day we may support multiple targets per >>> executable. >> >> Why would you care about which architectures the executable supports? >> What you actually want to know is which machine models are supported; >> whether board foo happens to be ARM or PPC isn't really very interesti= ng >> IMHO. >=20 > That's a very good point. It was the libvirt folks that requested > this. Perhaps they can shed some light on the logic? I think knowing the architecture (such as x86 vs. pseries ppc) is used by libvirt to know what default devices the board supports (for example, whether usb is present by default). There's probably still room for improvement for communication between libvirt and qemu on what exactly is being supported, and knowing an architecture type may be too broad of a knob compared to what is really wanted, except that I don't have a good handle on what is really wanted. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org ------enig2UOFFUIDGOWADBPSTPTFB 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.4.13 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJRn929AAoJEKeha0olJ0Nq0JYIAJVYmByS+92I9gYsoggDoFy/ 7BM/b/6e/FB1VZROqEv1uLIN+hWmMCOGLO+jtElRyFEbtosegQUhRn4bC7jhpYEF qJ0m7F5r/MkRUPI+1kBi8J+QuLBYla49L3pmg4+5T76uVCuIsVK+QlFMoAvMCw5y 0FW805jJTOob/Jcrj/+06RVv+m2ikFUaE6N9UxfbqCDRgyjkyaJAKxSTctgox+3x vHKYYsJrkfX8D7VtJnppF6VMIMgVZMZ5wd7fprfT4x54YrqIfNNRFcuW5tgbxXwJ LNVw6Yjd/4QeL6rKm492P4bThxRhvTbpwpweplJOP932Qm+j2WKnyom/VeNOF6g= =ehm6 -----END PGP SIGNATURE----- ------enig2UOFFUIDGOWADBPSTPTFB--