2016-09-30 16:45:27 +02:00
|
|
|
util-obj-y = qapi-visit-core.o qapi-dealloc-visitor.o qobject-input-visitor.o
|
|
|
|
|
util-obj-y += qobject-output-visitor.o qmp-registry.o qmp-dispatch.o
|
2012-12-20 15:27:51 +01:00
|
|
|
util-obj-y += string-input-visitor.o string-output-visitor.o
|
qapi: Add new clone visitor
We have a couple places in the code base that want to deep-clone
one QAPI object into another, and they were resorting to serializing
the struct out to QObject then reparsing it. A much more efficient
version can be done by adding a new clone visitor.
Since cloning is still relatively uncommon, expose the use of the
new visitor via a QAPI_CLONE() macro that takes care of type-punning
the underlying function pointer, rather than generating lots of
unused functions for types that won't be cloned. And yes, we're
relying on the compiler treating all pointers equally, even though
a strict C program cannot portably do so - but we're not the first
one in the qemu code base to expect it to work (hello, glib!).
The choice of adding a fourth visitor type deserves some explanation.
On the surface, the clone visitor is mostly an input visitor (it
takes arbitrary input - in this case, another QAPI object - and
creates a new QAPI object during the course of the visit). But
ever since commit da72ab0 consolidated enum visits based on the
visitor type, using VISITOR_INPUT would cause us to run
visit_type_str(), even though for cloning there is nothing to do
(we just copy the enum value across, without regards to its mapping
to strings). Also, since our input happens to be a QAPI object,
we can also satisfy the internal checks for VISITOR_OUTPUT. So in
the end, I settled with a new VISITOR_CLONE, and chose its value
such that many internal checks can use 'v->type & mask', sticking
to 'v->type == value' where the difference matters.
Note that we can only clone objects (including alternates) and lists,
not built-ins or enums. The visitor core hides integer width from
the actual visitor (since commit 04e070d), and as long as that's the
case, we can't clone top-level integers. Then again, those can
always be cloned by direct copy, since they are not objects with
deep pointers, so it's no real loss. And restricting cloning to
just objects and lists is cleaner than restricting it to non-integers.
As such, I documented that the clone visitor is for direct use only
by code internal to QAPI, and should not be used on incomplete objects
(other than a hack to work around the fact that we allow NULL in place
of "" in visit_type_str() in other output visitors). Note that as
written, the clone visitor will never fail on a complete object.
Scalars (including enums) not at the root of the clone copy just fine
with no additional effort while visiting the scalar, by virtue of a
g_memdup() each time we push another struct onto the stack. Cloning
a string requires deduplication of a pointer, which means it can also
provide the guarantee of an input visitor of never producing NULL
even when still accepting NULL in place of "" the way the QMP output
visitor does.
Cloning an 'any' type could be possible by incrementing the QObject
refcnt, but it's not obvious whether that is better than implementing
a QObject deep clone. So for now, we document it as unsupported,
and intentionally omit the .type_any() callback to let a developer
know their usage needs implementation.
Add testsuite coverage for several different clone situations, to
ensure that the code is working. I also tested that valgrind was
happy with the test.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <1465490926-28625-14-git-send-email-eblake@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
2016-06-09 18:48:44 +02:00
|
|
|
util-obj-y += opts-visitor.o qapi-clone-visitor.o
|
2014-06-18 08:43:27 +02:00
|
|
|
util-obj-y += qmp-event.o
|
2014-08-13 19:20:17 +02:00
|
|
|
util-obj-y += qapi-util.o
|
2019-02-14 16:22:40 +01:00
|
|
|
|
2020-01-29 11:22:37 +01:00
|
|
|
QAPI_COMMON_MODULES = audio authz block-core block char common control crypto
|
|
|
|
|
QAPI_COMMON_MODULES += dump error introspect job machine migration misc
|
2020-02-24 15:30:03 +01:00
|
|
|
QAPI_COMMON_MODULES += net pragma qdev qom rdma rocker run-state sockets tpm
|
2019-06-19 22:10:37 +02:00
|
|
|
QAPI_COMMON_MODULES += trace transaction ui
|
2019-06-19 22:10:46 +02:00
|
|
|
QAPI_TARGET_MODULES = machine-target misc-target
|
2019-02-14 16:22:41 +01:00
|
|
|
QAPI_MODULES = $(QAPI_COMMON_MODULES) $(QAPI_TARGET_MODULES)
|
2019-02-14 16:22:40 +01:00
|
|
|
|
|
|
|
|
util-obj-y += qapi-builtin-types.o
|
2019-02-14 16:22:41 +01:00
|
|
|
util-obj-y += $(QAPI_COMMON_MODULES:%=qapi-types-%.o)
|
2019-02-14 16:22:40 +01:00
|
|
|
util-obj-y += qapi-builtin-visit.o
|
2019-02-14 16:22:41 +01:00
|
|
|
util-obj-y += $(QAPI_COMMON_MODULES:%=qapi-visit-%.o)
|
2019-02-14 16:22:40 +01:00
|
|
|
util-obj-y += qapi-emit-events.o
|
2019-02-14 16:22:41 +01:00
|
|
|
util-obj-y += $(QAPI_COMMON_MODULES:%=qapi-events-%.o)
|
2019-02-14 16:22:40 +01:00
|
|
|
|
2019-02-14 16:22:41 +01:00
|
|
|
common-obj-y = $(QAPI_COMMON_MODULES:%=qapi-commands-%.o)
|
2019-02-14 16:22:40 +01:00
|
|
|
|
|
|
|
|
obj-y = qapi-introspect.o
|
2019-02-14 16:22:41 +01:00
|
|
|
obj-y += $(QAPI_TARGET_MODULES:%=qapi-types-%.o)
|
|
|
|
|
obj-y += qapi-types.o
|
|
|
|
|
obj-y += $(QAPI_TARGET_MODULES:%=qapi-visit-%.o)
|
|
|
|
|
obj-y += qapi-visit.o
|
|
|
|
|
obj-y += $(QAPI_TARGET_MODULES:%=qapi-events-%.o)
|
|
|
|
|
obj-y += qapi-events.o
|
|
|
|
|
obj-y += $(QAPI_TARGET_MODULES:%=qapi-commands-%.o)
|
|
|
|
|
obj-y += qapi-commands.o
|
2019-11-20 19:25:48 +01:00
|
|
|
obj-y += qapi-init-commands.o
|
2020-02-24 15:30:08 +01:00
|
|
|
|
|
|
|
|
QAPI_MODULES_STORAGE_DAEMON = block-core char common control crypto
|
|
|
|
|
QAPI_MODULES_STORAGE_DAEMON += introspect job qom sockets pragma transaction
|
|
|
|
|
|
|
|
|
|
storage-daemon-obj-y += $(QAPI_MODULES_STORAGE_DAEMON:%=qapi-commands-%.o)
|