From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59421) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIDSm-0006EQ-29 for qemu-devel@nongnu.org; Tue, 25 Feb 2014 03:34:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WIDSd-0006fS-Mk for qemu-devel@nongnu.org; Tue, 25 Feb 2014 03:34:03 -0500 Received: from cantor2.suse.de ([195.135.220.15]:36450 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIDSd-0006fC-GA for qemu-devel@nongnu.org; Tue, 25 Feb 2014 03:33:55 -0500 Message-ID: <530C556E.2020305@suse.de> Date: Tue, 25 Feb 2014 09:33:50 +0100 From: =?ISO-8859-15?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <20140221091629.GE11907@stefanha-thinkpad.redhat.com> <530764B0.40500@redhat.com> <5307BE7A.5050007@redhat.com> <87ha7o6hhj.fsf@blackfin.pond.sub.org> <530B6E85.30709@redhat.com> <87y50zsinq.fsf@blackfin.pond.sub.org> <530C54B4.10102@redhat.com> In-Reply-To: <530C54B4.10102@redhat.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] QOM vs QAPI for QMP APIs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , Markus Armbruster , Eric Blake Cc: Stefan Hajnoczi , qemu-devel@nongnu.org, Michael Roth , Luiz Capitulino , Anthony Liguori , Anthony Liguori Am 25.02.2014 09:30, schrieb Paolo Bonzini: > Il 25/02/2014 09:25, Markus Armbruster ha scritto: >>> > Haven't we already done that in the past? For example, object-add >>> > currently takes an unspecified dictionary of options, where you wou= ld >>> > have to consult QOM documentation to learn what makes sense to send= . >> My question isn't about where the command details are documented, or >> even whether they are documented. It's about ABI promises, or lack >> thereof. The general promise for QMP is we treat it as stable ABI. I= f >> we add QMP commands to examine and manipulate QOM, doesn't that move a= ll >> of QOM under the QMP ABI promise, unless we explicitly excempt it? >=20 > We did already exempt it, in general. QOM is not declared stable. Negative, QOM is stable in that properties may not change their type incompatibly. Properties may be dropped/renamed, since that is discoverable via qom-list, so it is less stable than the command line interface. Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg