Kconfig 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190
  1. # SPDX-License-Identifier: GPL-2.0
  2. menu "UML Character Devices"
  3. config STDERR_CONSOLE
  4. bool "stderr console"
  5. default y
  6. help
  7. console driver which dumps all printk messages to stderr.
  8. config SSL
  9. bool "Virtual serial line"
  10. help
  11. The User-Mode Linux environment allows you to create virtual serial
  12. lines on the UML that are usually made to show up on the host as
  13. ttys or ptys.
  14. See <http://user-mode-linux.sourceforge.net/old/input.html> for more
  15. information and command line examples of how to use this facility.
  16. Unless you have a specific reason for disabling this, say Y.
  17. config NULL_CHAN
  18. bool "null channel support"
  19. help
  20. This option enables support for attaching UML consoles and serial
  21. lines to a device similar to /dev/null. Data written to it disappears
  22. and there is never any data to be read.
  23. config PORT_CHAN
  24. bool "port channel support"
  25. help
  26. This option enables support for attaching UML consoles and serial
  27. lines to host portals. They may be accessed with 'telnet <host>
  28. <port number>'. Any number of consoles and serial lines may be
  29. attached to a single portal, although what UML device you get when
  30. you telnet to that portal will be unpredictable.
  31. It is safe to say 'Y' here.
  32. config PTY_CHAN
  33. bool "pty channel support"
  34. help
  35. This option enables support for attaching UML consoles and serial
  36. lines to host pseudo-terminals. Access to both traditional
  37. pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
  38. with this option. The assignment of UML devices to host devices
  39. will be announced in the kernel message log.
  40. It is safe to say 'Y' here.
  41. config TTY_CHAN
  42. bool "tty channel support"
  43. help
  44. This option enables support for attaching UML consoles and serial
  45. lines to host terminals. Access to both virtual consoles
  46. (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
  47. /dev/pts/*) are controlled by this option.
  48. It is safe to say 'Y' here.
  49. config XTERM_CHAN
  50. bool "xterm channel support"
  51. help
  52. This option enables support for attaching UML consoles and serial
  53. lines to xterms. Each UML device so assigned will be brought up in
  54. its own xterm.
  55. It is safe to say 'Y' here.
  56. config XTERM_CHAN_DEFAULT_EMULATOR
  57. string "xterm channel default terminal emulator"
  58. depends on XTERM_CHAN
  59. default "xterm"
  60. help
  61. This option allows changing the default terminal emulator.
  62. config NOCONFIG_CHAN
  63. bool
  64. default !(XTERM_CHAN && TTY_CHAN && PTY_CHAN && PORT_CHAN && NULL_CHAN)
  65. config CON_ZERO_CHAN
  66. string "Default main console channel initialization"
  67. default "fd:0,fd:1"
  68. help
  69. This is the string describing the channel to which the main console
  70. will be attached by default. This value can be overridden from the
  71. command line. The default value is "fd:0,fd:1", which attaches the
  72. main console to stdin and stdout.
  73. It is safe to leave this unchanged.
  74. config CON_CHAN
  75. string "Default console channel initialization"
  76. default "xterm"
  77. help
  78. This is the string describing the channel to which all consoles
  79. except the main console will be attached by default. This value can
  80. be overridden from the command line. The default value is "xterm",
  81. which brings them up in xterms.
  82. It is safe to leave this unchanged, although you may wish to change
  83. this if you expect the UML that you build to be run in environments
  84. which don't have X or xterm available.
  85. config SSL_CHAN
  86. string "Default serial line channel initialization"
  87. default "pty"
  88. help
  89. This is the string describing the channel to which the serial lines
  90. will be attached by default. This value can be overridden from the
  91. command line. The default value is "pty", which attaches them to
  92. traditional pseudo-terminals.
  93. It is safe to leave this unchanged, although you may wish to change
  94. this if you expect the UML that you build to be run in environments
  95. which don't have a set of /dev/pty* devices.
  96. config UML_SOUND
  97. tristate "Sound support"
  98. depends on SOUND
  99. select SOUND_OSS_CORE
  100. help
  101. This option enables UML sound support. If enabled, it will pull in
  102. the UML hostaudio relay, which acts as a intermediary
  103. between the host's dsp and mixer devices and the UML sound system.
  104. It is safe to say 'Y' here.
  105. endmenu
  106. menu "UML Network Devices"
  107. depends on NET
  108. config UML_NET_VECTOR
  109. bool "Vector I/O high performance network devices"
  110. select MAY_HAVE_RUNTIME_DEPS
  111. help
  112. This User-Mode Linux network driver uses multi-message send
  113. and receive functions. The host running the UML guest must have
  114. a linux kernel version above 3.0 and a libc version > 2.13.
  115. This driver provides tap, raw, gre and l2tpv3 network transports.
  116. For more information, including explanations of the networking
  117. and sample configurations, see
  118. <file:Documentation/virt/uml/user_mode_linux_howto_v2.rst>.
  119. endmenu
  120. config VIRTIO_UML
  121. bool "UML driver for virtio devices"
  122. select VIRTIO
  123. help
  124. This driver provides support for virtio based paravirtual device
  125. drivers over vhost-user sockets.
  126. config UML_RTC
  127. bool "UML RTC driver"
  128. depends on RTC_CLASS
  129. # there's no use in this if PM_SLEEP isn't enabled ...
  130. depends on PM_SLEEP
  131. help
  132. When PM_SLEEP is configured, it may be desirable to wake up using
  133. rtcwake, especially in time-travel mode. This driver enables that
  134. by providing a fake RTC clock that causes a wakeup at the right
  135. time.
  136. config UML_PCI
  137. bool
  138. select FORCE_PCI
  139. select IRQ_MSI_LIB
  140. select UML_IOMEM_EMULATION
  141. select UML_DMA_EMULATION
  142. select PCI_MSI
  143. select PCI_LOCKLESS_CONFIG
  144. config UML_PCI_OVER_VIRTIO
  145. bool "Enable PCI over VIRTIO device simulation"
  146. # in theory, just VIRTIO is enough, but that causes recursion
  147. depends on VIRTIO_UML
  148. select UML_PCI
  149. config UML_PCI_OVER_VIRTIO_DEVICE_ID
  150. int "set the virtio device ID for PCI emulation"
  151. default -1
  152. depends on UML_PCI_OVER_VIRTIO
  153. help
  154. There's no official device ID assigned (yet), set the one you
  155. wish to use for experimentation here. The default of -1 is
  156. not valid and will cause the driver to fail at probe.
  157. config UML_PCI_OVER_VFIO
  158. bool "Enable VFIO-based PCI passthrough"
  159. select UML_PCI
  160. help
  161. This driver provides support for VFIO-based PCI passthrough.
  162. Currently, only MSI-X capable devices are supported, and it
  163. is assumed that drivers will use MSI-X.