Gerd Hoffmann <kra...@redhat.com> writes: > Hi, > >> > Hmm, I think the xen core needs better QOM support ... >> > >> > struct XenDevice should have a DeviceState element, so it can be used as >> > device object directly instead of attaching a device object like >> > this ... >> >> Hmm, interesting idea. The device object could even be added in >> Xen common code if the backend is indicating the need for it via a >> special flag/field. I'll have a try. > > No, not optional. Just turn *all* xen devices into QOM objects.
Yes, please. > XenDevice should probably a subclass of the base device object > (DeviceState), and all Xen backends (block, net, fb, pvusb, ...) > should be subclasses of XenDevice. > > The latter is probably how things are modeled already, just the QOM > object stuff is missing (register classes, macros to cast objects, ...) > because qdev (the QOM predecessor) didn't have that. > > Once this is in place you can simply use DEVICE(xendevice) to get the > DeviceState pointer. Related thread: qdevification of xen_disk _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
