在 2021/6/30 上午4:01, Michael S. Tsirkin 写道:

On Tue, Jun 29, 2021 at 11:41:54AM +0800, Jason Wang wrote:

quoted

在 2021/6/29 上午6:39, Michael S. Tsirkin 写道:

quoted

On Mon, Jun 28, 2021 at 01:03:20PM +0800, Jason Wang wrote:

quoted

So I think we need solve them all, but netlink is probably the wrong layer,
we need to solve them at virtio level and let netlink a transport for them
virtio uAPI/ABI.

I'm not sure I follow. virtio defines VF to driver communication.
This is PF to hypervisor. virtio simply does not cover it ATM.

Note that this is not PF to hypervisor but the uAPI from userspace (vDPA
tool) to vDPA core.

We had two choices.

1) tweak virtio uAPIs
2) invent virtio specific uAPI in netlink

1) seems better.

Thanks

Well things like setting mac aren't virtio specific.
What are the virtio specific things you have in mind?

E.g max_virtqueue_pairs? Even if mac aren't virtio specific, the idea is 
to build the device config which is virtio specific.

And we may have other devices like virtio-blk.

Thanks

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization