From: Stefan Hajnoczi <stefa...@redhat.com> Date: Mon, 21 Nov 2016 13:56:31 +0000
> The VMware VMCI transport supports loopback inside virtual machines. > This patch implements loopback for virtio-vsock. > > Flow control is handled by the virtio-vsock protocol as usual. The > sending process stops transmitting on a connection when the peer's > receive buffer space is exhausted. > > Cathy Avery <cav...@redhat.com> noticed this difference between VMCI and > virtio-vsock when a test case using loopback failed. Although loopback > isn't the main point of AF_VSOCK, it is useful for testing and > virtio-vsock must match VMCI semantics so that userspace programs run > regardless of the underlying transport. > > My understanding is that loopback is not supported on the host side with > VMCI. Follow that by implementing it only in the guest driver, not the > vhost host driver. > > Cc: Jorgen Hansen <jhan...@vmware.com> > Reported-by: Cathy Avery <cav...@redhat.com> > Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com> > --- > v2: > * Fixed checkpatch.pl warnings [DaveM] Applied to net-next, thanks.
