From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60917) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uu6sY-0006FJ-UI for qemu-devel@nongnu.org; Tue, 02 Jul 2013 16:08:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uu6sX-0007JP-G7 for qemu-devel@nongnu.org; Tue, 02 Jul 2013 16:08:46 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40730) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uu6sX-0007JG-6c for qemu-devel@nongnu.org; Tue, 02 Jul 2013 16:08:45 -0400 Message-ID: <51D33347.2050909@redhat.com> Date: Tue, 02 Jul 2013 14:08:39 -0600 From: Eric Blake MIME-Version: 1.0 References: <1371644677-11041-1-git-send-email-akong@redhat.com> <878v1pqak4.fsf@codemonkey.ws> <51D2F1B3.1080903@redhat.com> <20130702153945.GZ2524@redhat.com> <51D3035A.1060605@redhat.com> <877gh8j012.fsf@codemonkey.ws> <51D3314F.1070609@redhat.com> In-Reply-To: <51D3314F.1070609@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="----enig2GDBFTXIVEOEKCFVEJNTL" Subject: Re: [Qemu-devel] [PATCH] full introspection support for QMP List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Anthony Liguori , qemu-devel@nongnu.org, armbru@redhat.com, lcapitulino@redhat.com, qiaonuohan@cn.fujitsu.com, Amos Kong This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2GDBFTXIVEOEKCFVEJNTL Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 07/02/2013 02:00 PM, Paolo Bonzini wrote: > Il 02/07/2013 20:21, Anthony Liguori ha scritto: >>>> >>>> Indeed, I wouldn't mind a one-time pass over qapi-schema.json to mak= e it >>>> follow a more rigid format if that made it easier to use it as-is wi= th >>>> less post-processing. It won't be very nice to backport such a >>>> conversion, but I don't know how much distros are planning on >>>> backporting introspection in the first place. >> We consume the schema in QEMU. No reason for us to consume it in a >> different format than libvirt. >=20 > One reason could be that qapi-schema.json, as written, lacks a schema > that can be expressed itself using QAPI. Indeed - it was my attempt to write a structured set of QAPI that led to the more rigid and more verbose layout, rather than shorthand. On the other hand, there's nothing stopping us from stating that QAPI itself can be extended to express new concepts (after all, we want to express the full structure of events as part of qapi-schema.json someday); we even have the 'qmp_capabilities' handshake to advertise whether use of such extensions will be understood by the client. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org ------enig2GDBFTXIVEOEKCFVEJNTL 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/ iQEcBAEBCAAGBQJR0zNHAAoJEKeha0olJ0NqdrIH/Rmvo93JEux6dSD2e1/YFmiQ tmxuTlk81XZ6GKkuyhfZe245yGSQ3iPaaHKSNzbMiFpEnzpKar2e+6AzkNZWl1fW VGLXHqBBOIIsGub4D9qo2YKgA+hBGsNgIyZd858MDmY3t/LGNf63/G8uptHDpKVV 0n4+m21kFxpjNFliFO76FIenddzcFWzyGDwfgTNURQGpUPUxLsAsOraFTa/pVDls BnFapD5VioJIjKKJAdVMBK1LMFTAEqGNb8XfSDcoroQdGY18XgsKhGZwwx8a6Fuc c2k8jBvzCt0WX8TmADqO1pnRhiAIZVf642P3l1rRc/1B7R/MxWLh+p5ivywqt7w= =kxtG -----END PGP SIGNATURE----- ------enig2GDBFTXIVEOEKCFVEJNTL--