> From: Xie Yongji <xieyongji@xxxxxxxxxxxxx> > Sent: Monday, May 16, 2022 2:04 AM > > Introduce a device object for vdpa management device to control its > lifecycle. Why is this needed? What is the limitation of current approach that requires new device for mgmtdev? The primary motivation is missing in the commit log here. > And the device name will be used to match > VDPA_ATTR_MGMTDEV_DEV_NAME field of netlink message rather than > using parent device name. > > With this patch applied, drivers should use vdpa_mgmtdev_alloc() or > _vdpa_mgmtdev_alloc() to allocate a vDPA management device before > calling vdpa_mgmtdev_register(). And some buggy empty release function > can also be removed from the driver codes. What is the bug, can you please explain? _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
