On Sun, Oct 27, 2019 at 09:01:46AM +0100, Stefan Hajnoczi wrote: > On Wed, Oct 23, 2019 at 11:55:40AM +0200, Stefano Garzarella wrote: > > This series adds the multi-transports support to vsock, following > > this proposal: https://www.spinics.net/lists/netdev/msg575792.html > > > > With the multi-transports support, we can use VSOCK with nested VMs > > (using also different hypervisors) loading both guest->host and > > host->guest transports at the same time. > > Before this series, vmci-transport supported this behavior but only > > using VMware hypervisor on L0, L1, etc. > > > > RFC: https://patchwork.ozlabs.org/cover/1168442/ > > RFC -> v1: > > - Added R-b/A-b from Dexuan and Stefan > > - Fixed comments and typos in several patches (Stefan) > > - Patch 7: changed .notify_buffer_size return to void (Stefan) > > - Added patch 8 to simplify the API exposed to the transports (Stefan) > > - Patch 11: > > + documented VSOCK_TRANSPORT_F_* flags (Stefan) > > + fixed vsock_assign_transport() when the socket is already assigned > > + moved features outside of struct vsock_transport, and used as > > parameter of vsock_core_register() as a preparation of Patch 12 > > - Removed "vsock: add 'transport_hg' to handle g2h\h2g transports" patch > > - Added patch 12 to register vmci_transport only when VMCI guest/host > > are active > > Has there been feedback from Jorgen or someone else from VMware? A > Reviewed-by or Acked-by would be nice since this patch series affects > VMCI AF_VSOCK. > Unfortunately not for now, I'm adding to this thread some VMware guys that reviewed latest vmci patches. Would be nice to have your feedback for these changes. Thanks in advance, Stefano
