VSOCK: Introduce VM Sockets

VM Sockets allows communication between virtual machines and the hypervisor.
User level applications both in a virtual machine and on the host can use the
VM Sockets API, which facilitates fast and efficient communication between
guest virtual machines and their host.  A socket address family, designed to be
compatible with UDP and TCP at the interface level, is provided.

Today, VM Sockets is used by various VMware Tools components inside the guest
for zero-config, network-less access to VMware host services.  In addition to
this, VMware's users are using VM Sockets for various applications, where
network access of the virtual machine is restricted or non-existent.  Examples
of this are VMs communicating with device proxies for proprietary hardware
running as host applications and automated testing of applications running
within virtual machines.

The VMware VM Sockets are similar to other socket types, like Berkeley UNIX
socket interface.  The VM Sockets module supports both connection-oriented
stream sockets like TCP, and connectionless datagram sockets like UDP. The VM
Sockets protocol family is defined as "AF_VSOCK" and the socket operations
split for SOCK_DGRAM and SOCK_STREAM.

For additional information about the use of VM Sockets, please refer to the
VM Sockets Programming Guide available at:

https://www.vmware.com/support/developer/vmci-sdk/

Signed-off-by: George Zhang <georgezhang@vmware.com>
Signed-off-by: Dmitry Torokhov <dtor@vmware.com>
Signed-off-by: Andy king <acking@vmware.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

1 files changed, 28 insertions, 0 deletions

diff --git a/net/vmw_vsock/Kconfig b/net/vmw_vsock/Kconfig
new file mode 100644
index 000000000000..b5fa7e40cdcb
--- /dev/null
+++ b/net/vmw_vsock/Kconfig
@@ -0,0 +1,28 @@
+#
+# Vsock protocol
+#
+
+config VSOCKETS
+        tristate "Virtual Socket protocol"
+        help
+          Virtual Socket Protocol is a socket protocol similar to TCP/IP
+          allowing comunication between Virtual Machines and hypervisor
+          or host.
+
+          You should also select one or more hypervisor-specific transports
+          below.
+
+          To compile this driver as a module, choose M here: the module
+          will be called vsock. If unsure, say N.
+
+config VMWARE_VMCI_VSOCKETS
+        tristate "VMware VMCI transport for Virtual Sockets"
+        depends on VSOCKETS && VMWARE_VMCI
+        help
+          This module implements a VMCI transport for Virtual Sockets.
+
+          Enable this transport if your Virtual Machine runs on a VMware
+          hypervisor.
+
+          To compile this driver as a module, choose M here: the module
+          will be called vmw_vsock_vmci_transport. If unsure, say N.