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

Jason Wang jasowang at redhat.com
Mon Nov 18 10:56:52 UTC 2019


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



More information about the dri-devel mailing list