Home
last modified time | relevance | path

Searched full:composition (Results 1 – 10 of 10) sorted by relevance

/qemu/docs/devel/
H A Drust.rst256 objects are *shared*, for example because they are part of the QOM composition
263 3. the QOM object is placed in the composition tree
267 5. but the shared reference is still present in the composition tree
H A Dqom.rst24 The QOM tree is a composition tree which represents all of the objects
H A Dclocks.rst450 device. Typically, when doing device composition, a device might
/qemu/include/qom/
H A Dobject.h105 * @obj: the object that is being removed from the composition tree
107 * Called when an object is being removed from the QOM composition tree.
648 * child of @parent in the composition tree.
1513 * Returns: the root object of the composition tree
1555 * path is the path within the composition tree starting from the root.
1565 * the path within the composition tree starting from the root. Use
1585 * specifying objects easy. At each level of the composition tree, the partial
1660 * Child properties form the composition tree. All objects need to be a child
H A Dobject_interfaces.h81 * it in the object composition tree with name @id, initializing
/qemu/include/hw/
H A Dqdev-clock.h92 * typically be only only for device composition purpose.
/qemu/
H A Dhmp-commands-info.hx558 .help = "show QOM composition tree",
565 Show QOM composition tree.
/qemu/hw/ppc/
H A Dspapr_drc.c540 * existing in the composition tree in drc_realize()
870 * composition tree at DRC_CONTAINER_PATH in spapr_dt_drc()
/qemu/qapi/
H A Dqom.json30 # composition tree.
93 # the composition tree, the partial path is matched as an absolute
/qemu/hw/virtio/
H A Dvirtio-qmp.c711 /* Query the QOM composition tree recursively for virtio devices */ in qmp_x_query_virtio()