Directory Files
.. 6
File Size
.iotlb.o.cmd 50 kB
.modules.order.cmd 314 B
.net.o.cmd 78 kB
.scsi.o.cmd 59 kB
.vdpa.o.cmd 78 kB
.vhost.ko.cmd 267 B
.vhost.mod.cmd 135 B
.vhost.mod.o.cmd 50 kB
.vhost.o.cmd 60 kB
.vhost_iotlb.ko.cmd 291 B
.vhost_iotlb.mod.cmd 147 B
.vhost_iotlb.mod.o.cmd 50 kB
.vhost_iotlb.o.cmd 462 B
.vhost_net.ko.cmd 283 B
.vhost_net.mod.cmd 141 B
.vhost_net.mod.o.cmd 50 kB
.vhost_net.o.cmd 452 B
.vhost_scsi.ko.cmd 287 B
.vhost_scsi.mod.cmd 144 B
.vhost_scsi.mod.o.cmd 50 kB
.vhost_scsi.o.cmd 457 B
.vhost_vdpa.ko.cmd 287 B
.vhost_vdpa.mod.cmd 144 B
.vhost_vdpa.mod.o.cmd 50 kB
.vhost_vdpa.o.cmd 457 B
.vhost_vsock.ko.cmd 291 B
.vhost_vsock.mod.cmd 147 B
.vhost_vsock.mod.o.cmd 50 kB
.vhost_vsock.o.cmd 462 B
.vringh.ko.cmd 271 B
.vringh.mod.cmd 138 B
.vringh.mod.o.cmd 50 kB
.vringh.o.cmd 57 kB
.vsock.o.cmd 74 kB
Kconfig 3.2 kB
Makefile 433 B
iotlb.c 5.8 kB
iotlb.o 38 kB
modules.order 181 B
net.c 48 kB
net.o 159 kB
scsi.c 80 kB
scsi.o 286 kB
test.c 8.5 kB
test.h 287 B
vdpa.c 43 kB
vdpa.o 128 kB
vhost.c 85 kB
vhost.h 12 kB
vhost.ko 447 kB
vhost.mod 22 B
vhost.mod.c 3.8 kB
vhost.mod.o 29 kB
vhost.o 458 kB
vhost_iotlb.ko 58 kB
vhost_iotlb.mod 22 B
vhost_iotlb.mod.c 1.2 kB
vhost_iotlb.mod.o 9.4 kB
vhost_iotlb.o 55 kB
vhost_net.ko 227 kB
vhost_net.mod 20 B
vhost_net.mod.c 466 B
vhost_net.mod.o 3.3 kB
vhost_net.o 229 kB
vhost_scsi.ko 383 kB
vhost_scsi.mod 21 B
vhost_scsi.mod.c 486 B
vhost_scsi.mod.o 3.3 kB
vhost_scsi.o 389 kB
vhost_vdpa.ko 180 kB
vhost_vdpa.mod 21 B
vhost_vdpa.mod.c 485 B
vhost_vdpa.mod.o 3.3 kB
vhost_vdpa.o 181 kB
vhost_vsock.ko 142 kB
vhost_vsock.mod 22 B
vhost_vsock.mod.c 498 B
vhost_vsock.mod.o 3.4 kB
vhost_vsock.o 145 kB
vringh.c 40 kB
vringh.ko 180 kB
vringh.mod 23 B
vringh.mod.c 1.1 kB
vringh.mod.o 8.8 kB
vringh.o 186 kB
vsock.c 28 kB
vsock.o 104 kB

Linux v7.4-rc3 - vhost

# SPDX-License-Identifier: GPL-2.0-only
config VHOST_IOTLB
	tristate
	help
	  Generic IOTLB implementation for vhost and vringh.
	  This option is selected by any driver which needs to support
	  an IOMMU in software.

config VHOST_RING
	tristate
	select VHOST_IOTLB
	help
	  This option is selected by any driver which needs to access
	  the host side of a virtio ring.

config VHOST_TASK
	bool
	default n

config VHOST
	tristate
	select VHOST_IOTLB
	select VHOST_TASK
	help
	  This option is selected by any driver which needs to access
	  the core of vhost.

menuconfig VHOST_MENU
	bool "VHOST drivers"
	default y

if VHOST_MENU

config VHOST_NET
	tristate "Host kernel accelerator for virtio net"
	depends on NET && EVENTFD && (TUN || !TUN) && (TAP || !TAP)
	select VHOST
	help
	  This kernel module can be loaded in host kernel to accelerate
	  guest networking with virtio_net. Not to be confused with virtio_net
	  module itself which needs to be loaded in guest kernel.

	  To compile this driver as a module, choose M here: the module will
	  be called vhost_net.

config VHOST_SCSI
	tristate "VHOST_SCSI TCM fabric driver"
	depends on TARGET_CORE && EVENTFD
	select VHOST
	select SG_POOL
	default n
	help
	Say M here to enable the vhost_scsi TCM fabric module
	for use with virtio-scsi guests

config VHOST_VSOCK
	tristate "vhost virtio-vsock driver"
	depends on VSOCKETS && EVENTFD
	select VHOST
	select VIRTIO_VSOCKETS_COMMON
	default n
	help
	This kernel module can be loaded in the host kernel to provide AF_VSOCK
	sockets for communicating with guests.  The guests must have the
	virtio_transport.ko driver loaded to use the virtio-vsock device.

	To compile this driver as a module, choose M here: the module will be called
	vhost_vsock.

config VHOST_VDPA
	tristate "Vhost driver for vDPA-based backend"
	depends on EVENTFD
	select VHOST
	select IRQ_BYPASS_MANAGER
	depends on VDPA
	help
	  This kernel module can be loaded in host kernel to accelerate
	  guest virtio devices with the vDPA-based backends.

	  To compile this driver as a module, choose M here: the module
	  will be called vhost_vdpa.

config VHOST_CROSS_ENDIAN_LEGACY
	bool "Cross-endian support for vhost"
	default n
	help
	  This option allows vhost to support guests with a different byte
	  ordering from host while using legacy virtio.

	  Userspace programs can control the feature using the
	  VHOST_SET_VRING_ENDIAN and VHOST_GET_VRING_ENDIAN ioctls.

	  This is only useful on a few platforms (ppc64 and arm64). Since it
	  adds some overhead, it is disabled by default.

	  If unsure, say "N".

config VHOST_ENABLE_FORK_OWNER_CONTROL
	bool "Enable VHOST_ENABLE_FORK_OWNER_CONTROL"
	default y
	help
	  This option enables two IOCTLs: VHOST_SET_FORK_FROM_OWNER and
	  VHOST_GET_FORK_FROM_OWNER. These allow userspace applications
	  to modify the vhost worker mode for vhost devices.

	  Also expose module parameter 'fork_from_owner_default' to allow users
	  to configure the default mode for vhost workers.

	  By default, `VHOST_ENABLE_FORK_OWNER_CONTROL` is set to `y`,
	  users can change the worker thread mode as needed.
	  If this config is disabled (n),the related IOCTLs and parameters will
	  be unavailable.

	  If unsure, say "Y".

endif