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





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Kernel Development]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Info]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Linux Media]     [Device Mapper]

  Powered by Linux