diff options
author | Eric Blake <eblake@redhat.com> | 2016-04-28 15:45:23 -0600 |
---|---|---|
committer | Markus Armbruster <armbru@redhat.com> | 2016-05-12 09:47:54 +0200 |
commit | 3df016f185521f8dfa5bd89168722887156405c7 (patch) | |
tree | fe7cda79ac5c168a6da67d19fcf5095b2269ead1 /device_tree.c | |
parent | 3bc97fd5924561d92f32758c67eaffd2e4e25038 (diff) | |
download | qemu-3df016f185521f8dfa5bd89168722887156405c7.zip qemu-3df016f185521f8dfa5bd89168722887156405c7.tar.gz qemu-3df016f185521f8dfa5bd89168722887156405c7.tar.bz2 |
qmp: Support explicit null during visits
Implement the new type_null() callback for the qmp input and
output visitors. While we don't yet have a use for this in QAPI
input (the generator will need some tweaks first), some
potential usages have already been discussed on the list.
Meanwhile, the output visitor could already output explicit null
via type_any, but this gives us finer control.
At any rate, it's easy to test that we can round-trip an explicit
null through manual use of visit_type_null() wrapped by a virtual
visit_start_struct() walk, even if we can't do the visit in a
QAPI type. Repurpose the test_visitor_out_empty test,
particularly since a future patch will tighten semantics to
forbid use of qmp_output_get_qobject() without at least one
intervening visit_type_*.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <1461879932-9020-16-git-send-email-eblake@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Diffstat (limited to 'device_tree.c')
0 files changed, 0 insertions, 0 deletions