qemu/qom
Daniel P. Berrangé 6134d7522e qom: don't require user creatable objects to be registered
When an object is in turn owned by another user object, it is not
desirable to expose this in the QOM object hierarchy. It is just an
internal implementation detail, we should be free to change without
exposure to apps managing QEMU.

Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2019-02-26 15:25:58 +00:00
..
container.c container: don't leak container reference 2017-05-04 15:34:41 +04:00
cpu.c qom/cpu: Add cluster_index to CPUState 2019-01-29 11:46:05 +00:00
Makefile.objs qom: allow QOM to be linked into tools binaries 2015-09-15 14:35:39 +01:00
object.c qom: don't require user creatable objects to be registered 2019-02-26 15:25:58 +00:00
object_interfaces.c qom: don't require user creatable objects to be registered 2019-02-26 15:25:58 +00:00
qom-qobject.c qapi: Drop unused non-strict qobject input visitor 2017-03-05 09:14:19 +01:00
trace-events docs: fix broken paths to docs/devel/tracing.txt 2017-07-31 13:12:53 +03:00