believe.
[LC] Agreed, so it reuses CMD defined by vhost-kernel ioctl. But VFIO provides
device specific things (e.g. DMAR, INTR and etc.) which is the extra APIs being
introduced by this transport.
I'm not quite sure I understand here. I think having vhost-kernel
compatible ioctl does not conflict of using VFIO ioctl like DMA or INTR?
Btw, VFIO DMA ioctl is even not a must from my point of view, vhost-mdev
can forward the mem table information to device driver and let it call
DMA API to map/umap pages.
[LC] If not regarding vhost-mdev as a device, then forward mem table won't be a
concern.
If introducing a new mdev bus driver (vhost-mdev) which allows mdev instance to
be a new type of provider for vhost-kernel. It becomes a pretty good
alternative to fully leverage vhost-kernel ioctl.
I'm not sure it's the same view as yours when you says reusing vhost-kernel
ioctl.