Kconfig - OpenGrok cross reference for /linux-6.8/arch/um/drivers/Kconfig

9 	  console driver which dumps all printk messages to stderr.
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
19 	  information and command line examples of how to use this facility.
27 	  lines to a device similar to /dev/null.  Data written to it disappears
28 	  and there is never any data to be read.
34 	  lines to host portals.  They may be accessed with 'telnet <host>
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.
44 	  lines to host pseudo-terminals.  Access to both traditional
46 	  with this option.  The assignment of UML devices to host devices
48 	  It is safe to say 'Y' here.
54 	  lines to host terminals.  Access to both virtual consoles
57 	  It is safe to say 'Y' here.
63 	  lines to xterms.  Each UML device so assigned will be brought up in
65 	  It is safe to say 'Y' here.
82 	  This is the string describing the channel to which the main console
85 	  main console to stdin and stdout.
86 	  It is safe to leave this unchanged.
92 	  This is the string describing the channel to which all consoles
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
104 	  This is the string describing the channel to which the serial lines
106 	  command line.  The default value is "pty", which attaches them to
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
120 	  It is safe to say 'Y' here.
131 	  While the User-Mode port cannot directly talk to any physical
134 	  kernels can talk to each other, the host, and with the host's help,
141 	  If you'd like to be able to enable networking in the User-Mode
143 	  enable at least one of the following transport options to actually
151 	  running UML to exchange packets with its host over one of the
155 	  Ethernet network, it's in fact communicating over a point-to-point
158 	  To use this, your host kernel must have support for Ethertap
164 	  has examples of the UML command line to use to enable Ethertap
168 	  migrate to UML_NET_VECTOR.
176 	  The UML TUN/TAP network transport allows a UML instance to exchange
178 	  work with a 2.4 host, unless you've applied the TUN/TAP patch to
181 	  To use this transport, your host kernel must have support for TUN/TAP
185 	  migrate to UML_NET_VECTOR.
193 	  The slip User-Mode Linux network transport allows a running UML to
194 	  network with its host over a point-to-point link.  Unlike Ethertap,
198 	  To use this, your host must support slip devices.
202 	  has examples of the UML command line to use to enable slip
206 	  migrate to UML_NET_VECTOR.
215 	  UMLs on a single host to communicate with each other, but not to
218 	  To use this form of networking, you'll need to run the UML
223 	  has examples of the UML command line to use to enable Daemon
227 	  migrate to UML_NET_VECTOR.
237 	  transport, normally it defaults to /tmp/uml.ctl.
248 	  with up to 4 times higher network throughput than the UML network
258 	  UMLs on a single host to communicate with each other and also
262 	  You must have libvdeplug installed in order to build the vde
265 	  To use this form of networking, you will need to run vde_switch
270 	  of the UML command line to use to enable VDE networking.
273 	  migrate to UML_NET_VECTOR.
282 	  UMLs (even ones running on different host machines!) to talk to
284 	  at least one UML with one of the other transports to act as a
285 	  bridge if any of them need to be able to talk to their hosts or any
288 	  To use this, your host kernel(s) must support IP Multicasting.
292 	  has examples of the UML command line to use to enable Multicast
296 	  migrate to UML_NET_VECTOR.
309 	  installed in order to build the pcap transport into UML.
313 	  has examples of the UML command line to use to enable this option.
316 	  migrate to UML_NET_VECTOR.
325 	  to network by invoking a program that can handle SLIP encapsulated
326 	  packets.  This is commonly (but not limited to) the application
331 	  to the outside world that the host user is permitted, and unlike
342 	  migrate to UML_NET_VECTOR.
363 	  When PM_SLEEP is configured, it may be desirable to wake up using
384 	  wish to use for experimentation here. The default of -1 is
385 	  not valid and will cause the driver to fail at probe.