xref: /openbmc/linux/net/vmw_vsock/Kconfig (revision d021c344)
1d021c344SAndy King#
2d021c344SAndy King# Vsock protocol
3d021c344SAndy King#
4d021c344SAndy King
5d021c344SAndy Kingconfig VSOCKETS
6d021c344SAndy King	tristate "Virtual Socket protocol"
7d021c344SAndy King	help
8d021c344SAndy King	  Virtual Socket Protocol is a socket protocol similar to TCP/IP
9d021c344SAndy King	  allowing comunication between Virtual Machines and hypervisor
10d021c344SAndy King	  or host.
11d021c344SAndy King
12d021c344SAndy King	  You should also select one or more hypervisor-specific transports
13d021c344SAndy King	  below.
14d021c344SAndy King
15d021c344SAndy King	  To compile this driver as a module, choose M here: the module
16d021c344SAndy King	  will be called vsock. If unsure, say N.
17d021c344SAndy King
18d021c344SAndy Kingconfig VMWARE_VMCI_VSOCKETS
19d021c344SAndy King	tristate "VMware VMCI transport for Virtual Sockets"
20d021c344SAndy King	depends on VSOCKETS && VMWARE_VMCI
21d021c344SAndy King	help
22d021c344SAndy King	  This module implements a VMCI transport for Virtual Sockets.
23d021c344SAndy King
24d021c344SAndy King	  Enable this transport if your Virtual Machine runs on a VMware
25d021c344SAndy King	  hypervisor.
26d021c344SAndy King
27d021c344SAndy King	  To compile this driver as a module, choose M here: the module
28d021c344SAndy King	  will be called vmw_vsock_vmci_transport. If unsure, say N.
29