docs/devel/qom.rst

13 - System for dynamically registering types
14 - Support for single-inheritance of types
15 - Multiple inheritance of stateless interfaces
16 - Mapping internal members to publicly exposed properties
26 ``info qom-tree`` in the :ref:`QEMU monitor`. It will contain both
35 .. code-block:: c
40    #define TYPE_MY_DEVICE "my-device"
78 .. code-block:: c
101 cast an #Object to a subclass (or base-class) type using
106 .. code-block:: c
120 .. code-block:: c
125 --------------------
145 .. code-block:: c
153        dc->reset = my_device_reset;
167 .. code-block:: c
191        klass->frobnicate(obj);
195 ----------
209 -------
213 strongly-typed first argument.
234 .. code-block:: c
256        mc->do_something = my_do_something;
278        dc->parent_do_something(obj);
287        dc->parent_do_something = mc->do_something;
288        mc->do_something = derived_do_something;
299 its non-overridden methods for a specific type. This would correspond to
302 One example of such methods is ``DeviceClass.reset``. More examples
303 can be found at :ref:`device-life-cycle`.
318 .. code-block:: c
325 .. code-block:: c
355 .. code-block:: c
362 .. code-block:: c
390 per-class state it needs to store in its own class struct,
395 .. code-block:: c
403 These accept an array of interface type names. The difference between
408 .. code-block:: c
416 .. code-block:: c
427 .. code-block:: c
433 .. _device-life-cycle:
435 Device Life-cycle
445 The reverse function is ``unrealize`` and should be were clean-up
460 See the :ref:`QOM API<qom-api>` and :ref:`QDEV API<qdev-api>`