similar to: [PATCH net-next 5/6] vsock: use local transport when it is loaded

v2: - style fixes [Dave] - removed RCU sync and changed 'the_vsock_loopback' in a global static variable [Stefan] - use G2H transport when local transport is not loaded and remote cid is VMADDR_CID_LOCAL [Stefan] - rebased on net-next v1: https://patchwork.kernel.org/cover/11251735/ This series introduces a new transport (vsock_loopback) to handle local communication. This

On Wed, Oct 23, 2019 at 11:59 AM Stefano Garzarella <sgarzare at redhat.com> wrote: > > This patch adds the support of multiple transports in the > VSOCK core. > > 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. > > Major changes:

On Wed, Oct 23, 2019 at 11:59 AM Stefano Garzarella <sgarzare at redhat.com> wrote: > > This patch adds the support of multiple transports in the > VSOCK core. > > 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. > > Major changes:

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > Sent: Tuesday, November 19, 2019 12:01 PM > To: netdev at vger.kernel.org > > This patch allows to register a transport able to handle > local communication (loopback). > > Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> > --- > include/net/af_vsock.h | 2 ++ >

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > Sent: Tuesday, November 19, 2019 12:01 PM > To: netdev at vger.kernel.org > > This patch allows to register a transport able to handle > local communication (loopback). > > Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> > --- > include/net/af_vsock.h | 2 ++ >

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > Sent: Thursday, November 21, 2019 4:22 PM > > On Thu, Nov 21, 2019 at 03:04:18PM +0000, Jorgen Hansen wrote: > > > From: Stefano Garzarella [mailto:sgarzare at redhat.com] > > > Sent: Tuesday, November 19, 2019 12:01 PM > > > To: netdev at vger.kernel.org > > > > > > This patch

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > Sent: Thursday, November 21, 2019 4:22 PM > > On Thu, Nov 21, 2019 at 03:04:18PM +0000, Jorgen Hansen wrote: > > > From: Stefano Garzarella [mailto:sgarzare at redhat.com] > > > Sent: Tuesday, November 19, 2019 12:01 PM > > > To: netdev at vger.kernel.org > > > > > > This patch

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > Sent: Wednesday, October 23, 2019 11:56 AM Thanks a lot for working on this! > 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. > > Major changes: > - vsock core module can be

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > Sent: Wednesday, October 23, 2019 11:56 AM Thanks a lot for working on this! > 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. > > Major changes: > - vsock core module can be

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > Sent: Monday, November 11, 2019 6:18 PM > To: Jorgen Hansen <jhansen at vmware.com> > Subject: Re: [PATCH net-next 11/14] vsock: add multi-transports support > > On Mon, Nov 11, 2019 at 01:53:39PM +0000, Jorgen Hansen wrote: > > > From: Stefano Garzarella [mailto:sgarzare at redhat.com] > > >

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > Sent: Monday, November 11, 2019 6:18 PM > To: Jorgen Hansen <jhansen at vmware.com> > Subject: Re: [PATCH net-next 11/14] vsock: add multi-transports support > > On Mon, Nov 11, 2019 at 01:53:39PM +0000, Jorgen Hansen wrote: > > > From: Stefano Garzarella [mailto:sgarzare at redhat.com] > > >

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > > +/* Assign a transport to a socket and call the .init transport callback. > > + * > > + * Note: for stream socket this must be called when vsk->remote_addr > > +is set > > + * (e.g. during the connect() or when a connection request on a > > +listener > > + * socket is received). > >

On Thu, Nov 21, 2019 at 03:04:18PM +0000, Jorgen Hansen wrote: > > From: Stefano Garzarella [mailto:sgarzare at redhat.com] > > Sent: Tuesday, November 19, 2019 12:01 PM > > To: netdev at vger.kernel.org > > > > This patch allows to register a transport able to handle > > local communication (loopback). > > > > Signed-off-by: Stefano Garzarella

On Thu, Nov 21, 2019 at 03:53:47PM +0000, Jorgen Hansen wrote: > > From: Stefano Garzarella [mailto:sgarzare at redhat.com] > > Sent: Thursday, November 21, 2019 4:22 PM > > > > On Thu, Nov 21, 2019 at 03:04:18PM +0000, Jorgen Hansen wrote: > > > > From: Stefano Garzarella [mailto:sgarzare at redhat.com] > > > > Sent: Tuesday, November 19, 2019

On Thu, Aug 03, 2023 at 06:58:24PM +0000, Bobby Eshleman wrote: >On Thu, Aug 03, 2023 at 02:42:26PM +0200, Stefano Garzarella wrote: >> On Thu, Aug 03, 2023 at 12:53:22AM +0000, Bobby Eshleman wrote: >> > On Wed, Aug 02, 2023 at 10:24:44PM +0000, Bobby Eshleman wrote: >> > > On Sun, Jul 23, 2023 at 12:53:15AM +0300, Arseniy Krasnov wrote: >> > > >

On Mon, Nov 11, 2019 at 01:53:39PM +0000, Jorgen Hansen wrote: > > From: Stefano Garzarella [mailto:sgarzare at redhat.com] > > Sent: Wednesday, October 23, 2019 11:56 AM > > Thanks a lot for working on this! > Thanks to you for the reviews! > > With the multi-transports support, we can use vsock with nested VMs (using > > also different hypervisors) loading

This patch adds the support of multiple transports in the VSOCK core. 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. Major changes: - vsock core module can be loaded regardless of the transports - vsock_core_init() and vsock_core_exit() are renamed to

> From: Stefano Garzarella [mailto:sgarzare at redhat.com] > Sent: Tuesday, November 19, 2019 12:01 PM > > The VMADDR_CID_RESERVED (1) was used by VMCI, but now it is not > used anymore, so we can reuse it for local communication > (loopback) adding the new well-know CID: VMADDR_CID_LOCAL. > > Cc: Jorgen Hansen <jhansen at vmware.com> > Signed-off-by: Stefano

On Tue, Nov 12, 2019 at 09:59:12AM +0000, Jorgen Hansen wrote: > > From: Stefano Garzarella [mailto:sgarzare at redhat.com] > > Sent: Monday, November 11, 2019 6:18 PM > > To: Jorgen Hansen <jhansen at vmware.com> > > Subject: Re: [PATCH net-next 11/14] vsock: add multi-transports support > > > > On Mon, Nov 11, 2019 at 01:53:39PM +0000, Jorgen Hansen

Most of the patches are reviewed by Dexuan, Stefan, and Jorgen. The following patches need reviews: - [11/15] vsock: add multi-transports support - [12/15] vsock/vmci: register vmci_transport only when VMCI guest/host are active - [15/15] vhost/vsock: refuse CID assigned to the guest->host transport RFC: https://patchwork.ozlabs.org/cover/1168442/ v1: