Kconfig 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. config VHOST_IOTLB
  3. tristate
  4. help
  5. Generic IOTLB implementation for vhost and vringh.
  6. This option is selected by any driver which needs to support
  7. an IOMMU in software.
  8. config VHOST_RING
  9. tristate
  10. select VHOST_IOTLB
  11. help
  12. This option is selected by any driver which needs to access
  13. the host side of a virtio ring.
  14. config VHOST_TASK
  15. bool
  16. default n
  17. config VHOST
  18. tristate
  19. select VHOST_IOTLB
  20. select VHOST_TASK
  21. help
  22. This option is selected by any driver which needs to access
  23. the core of vhost.
  24. menuconfig VHOST_MENU
  25. bool "VHOST drivers"
  26. default y
  27. if VHOST_MENU
  28. config VHOST_NET
  29. tristate "Host kernel accelerator for virtio net"
  30. depends on NET && EVENTFD && (TUN || !TUN) && (TAP || !TAP)
  31. select VHOST
  32. help
  33. This kernel module can be loaded in host kernel to accelerate
  34. guest networking with virtio_net. Not to be confused with virtio_net
  35. module itself which needs to be loaded in guest kernel.
  36. To compile this driver as a module, choose M here: the module will
  37. be called vhost_net.
  38. config VHOST_SCSI
  39. tristate "VHOST_SCSI TCM fabric driver"
  40. depends on TARGET_CORE && EVENTFD
  41. select VHOST
  42. default n
  43. help
  44. Say M here to enable the vhost_scsi TCM fabric module
  45. for use with virtio-scsi guests
  46. config VHOST_VSOCK
  47. tristate "vhost virtio-vsock driver"
  48. depends on VSOCKETS && EVENTFD
  49. select VHOST
  50. select VIRTIO_VSOCKETS_COMMON
  51. default n
  52. help
  53. This kernel module can be loaded in the host kernel to provide AF_VSOCK
  54. sockets for communicating with guests. The guests must have the
  55. virtio_transport.ko driver loaded to use the virtio-vsock device.
  56. To compile this driver as a module, choose M here: the module will be called
  57. vhost_vsock.
  58. config VHOST_VDPA
  59. tristate "Vhost driver for vDPA-based backend"
  60. depends on EVENTFD
  61. select VHOST
  62. select IRQ_BYPASS_MANAGER
  63. depends on VDPA
  64. help
  65. This kernel module can be loaded in host kernel to accelerate
  66. guest virtio devices with the vDPA-based backends.
  67. To compile this driver as a module, choose M here: the module
  68. will be called vhost_vdpa.
  69. config VHOST_CROSS_ENDIAN_LEGACY
  70. bool "Cross-endian support for vhost"
  71. default n
  72. help
  73. This option allows vhost to support guests with a different byte
  74. ordering from host while using legacy virtio.
  75. Userspace programs can control the feature using the
  76. VHOST_SET_VRING_ENDIAN and VHOST_GET_VRING_ENDIAN ioctls.
  77. This is only useful on a few platforms (ppc64 and arm64). Since it
  78. adds some overhead, it is disabled by default.
  79. If unsure, say "N".
  80. config VHOST_ENABLE_FORK_OWNER_CONTROL
  81. bool "Enable VHOST_ENABLE_FORK_OWNER_CONTROL"
  82. default y
  83. help
  84. This option enables two IOCTLs: VHOST_SET_FORK_FROM_OWNER and
  85. VHOST_GET_FORK_FROM_OWNER. These allow userspace applications
  86. to modify the vhost worker mode for vhost devices.
  87. Also expose module parameter 'fork_from_owner_default' to allow users
  88. to configure the default mode for vhost workers.
  89. By default, `VHOST_ENABLE_FORK_OWNER_CONTROL` is set to `y`,
  90. users can change the worker thread mode as needed.
  91. If this config is disabled (n),the related IOCTLs and parameters will
  92. be unavailable.
  93. If unsure, say "Y".
  94. endif