From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37189) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMf4x-0005pK-85 for qemu-devel@nongnu.org; Fri, 22 Jan 2016 12:00:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aMf4s-00074O-82 for qemu-devel@nongnu.org; Fri, 22 Jan 2016 12:00:55 -0500 Received: from mx1.redhat.com ([209.132.183.28]:41627) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMf4s-00074J-2d for qemu-devel@nongnu.org; Fri, 22 Jan 2016 12:00:50 -0500 From: Markus Armbruster References: <1453219845-30939-1-git-send-email-eblake@redhat.com> <1453219845-30939-23-git-send-email-eblake@redhat.com> Date: Fri, 22 Jan 2016 18:00:47 +0100 In-Reply-To: <1453219845-30939-23-git-send-email-eblake@redhat.com> (Eric Blake's message of "Tue, 19 Jan 2016 09:10:30 -0700") Message-ID: <87fuxpim68.fsf@blackfin.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v9 22/37] qapi: Add visit_type_null() visitor List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: marcandre.lureau@redhat.com, qemu-devel@nongnu.org, Michael Roth Eric Blake writes: > Right now, qmp-output-visitor happens to produce a QNull result > if nothing is actually visited between the creation of the visitor > and the request for the resulting QObject. A stronger protocol > would require that a QMP output visit MUST visit something. But > to still be able to produce a JSON 'null' output, we need a new > visitor function that states our intentions. Overdue. When we extended the json-parser to accept null, we neglected to extend visitors accordingly. We need to: * Extend the visitor core (this patch). * Implement it in at least the visitors that aren't restricted to a subset: dealloc (this patch), QMP input (next patch), QMP output (patch after next, together with other stuff). * Update users, if any. * If QAPI had a 'null' type, we'd also have to use it in the generated visitor functions. It doesn't. I think the 'any' type can hold a null, but that's it. A 'null' type might be useful as an alternate member type. We'll create one when we need it. > This patch introduces the new visit_type_null() interface, and > later patches will then wire it up into the qmp visitors. > > Signed-off-by: Eric Blake > Reviewed-by: Marc-Andr=C3=A9 Lureau > > --- > v9: no change > v8: rebase to 'name' motion > v7: new patch, based on discussion about spapr_drc.c > --- > include/qapi/visitor-impl.h | 3 +++ > include/qapi/visitor.h | 8 ++++++++ > qapi/qapi-dealloc-visitor.c | 5 +++++ > qapi/qapi-visit-core.c | 5 +++++ > 4 files changed, 21 insertions(+) > > diff --git a/include/qapi/visitor-impl.h b/include/qapi/visitor-impl.h > index aab46bc..8705136 100644 > --- a/include/qapi/visitor-impl.h > +++ b/include/qapi/visitor-impl.h > @@ -75,6 +75,9 @@ struct Visitor > * visitors do not currently visit arbitrary types). */ > void (*type_any)(Visitor *v, const char *name, QObject **obj, > Error **errp); > + /* Must be provided to visit explicit null values (right now, only t= he > + * dealloc visitor supports this). */ Will need updating to match whatever convention we pick in the previous patch for documenting "mandatory to visit X", and the restrictions on visitor use resulting from some of them not implementing it. > + void (*type_null)(Visitor *v, const char *name, Error **errp); > > /* May be NULL; most useful for input visitors. */ > void (*optional)(Visitor *v, const char *name, bool *present); [...]