![Stefan Hajnoczi](/assets/img/avatar_default.png)
This reverts commit0d76d6e8b2
and merge commitc402293bd7
, reversing changes made toc89359a42e
. The virtio-vsock device specification is not finalized yet. Michael Tsirkin voiced concerned about merging this code when the hardware interface (and possibly the userspace interface) could still change. Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
29 lines
812 B
Plaintext
29 lines
812 B
Plaintext
#
|
|
# Vsock protocol
|
|
#
|
|
|
|
config VSOCKETS
|
|
tristate "Virtual Socket protocol"
|
|
help
|
|
Virtual Socket Protocol is a socket protocol similar to TCP/IP
|
|
allowing communication 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.
|