Kconfig

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