Hi Gerd,
> From my side the minimum requirement is to have
> vsock_(un)register_transport calls available, so it is possible to
> write a virtio transport module without having to patch vsock code
> to hook it up.
We've done exactly that. It's now split into two separate modules,
with the core module offering precisely the calls you've requested.
All transport code is now its own module. So now you should be
able to add a vsock_transport_virtio module, which can register
with the core.
> >>> + struct {
> >>> + /* For DGRAMs. */
> >>> + struct vmci_handle dg_handle;
> >>
> >> Yep, should be a pointer where transports can hook in their
> >> private
> >> data.
> >
> > I'm fixing this.
>
> Yes, please, that is needed too to get started with virtio support.
Fixed: it's now a void * in the core socket structure.
I believe it's now at the point where you can start working on the
virtio transport, and we'll address API issues as they arise and
refine it as necessary. So please take one last look and let us
know what you think; hopefully we can make the current merge window :)
Thanks!
- Andy
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
