> 1-8 is fine, but I think 9-11 is too much complication (especially not
> really future-proof) for the benefit.
Isn't qdev considered an internal API for our object and device lifetime
handling (which should be shared) versus QAPI which only exists for
system emulation and tool integration?
qdev is nothing more than a bunch of QOM classes, and QAPI is an integral part of QOM (though properties, which are used when setting up CPUs in user more emulation)
Therefore, even though most of the QAPI schema is specific to system emulation and tools, a small part is used by common code.
Paolo