Re: [PATCH V12 5/6] virtio: introduce a mdev based transport

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 2019/11/18 下午6:44, Michael S. Tsirkin wrote:
+static const struct mdev_virtio_class_id virtio_id_table[] = {
+	{ MDEV_VIRTIO_CLASS_ID_VIRTIO },
+	{ 0 },
+};
+
Do we still need the class ID? It's a virtio mdev bus,
do we need a virtio class as well?


If we want to have auto match between vhost-mdev driver and vhost-mdev device, we need this.

Otherwise, user need to manually probe or bind driver to the device.

Thanks





[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux