Kconfig - OpenGrok cross reference for /linux-5.10/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.
75 	  This is the string describing the channel to which the main console
78 	  main console to stdin and stdout.
79 	  It is safe to leave this unchanged.
85 	  This is the string describing the channel to which all consoles
89 	  It is safe to leave this unchanged, although you may wish to change
90 	  this if you expect the UML that you build to be run in environments
97 	  This is the string describing the channel to which the serial lines
99 	  command line.  The default value is "pty", which attaches them to
101 	  It is safe to leave this unchanged, although you may wish to change
102 	  this if you expect the UML that you build to be run in environments
111 	  It is safe to say 'Y' here.
134 	  While the User-Mode port cannot directly talk to any physical
137 	  kernels can talk to each other, the host, and with the host's help,
144 	  If you'd like to be able to enable networking in the User-Mode
146 	  enable at least one of the following transport options to actually
154 	  running UML to exchange packets with its host over one of the
158 	  Ethernet network, it's in fact communicating over a point-to-point
161 	  To use this, your host kernel must have support for Ethertap
167 	  has examples of the UML command line to use to enable Ethertap
171 	  migrate to UML_NET_VECTOR.
179 	  The UML TUN/TAP network transport allows a UML instance to exchange
181 	  work with a 2.4 host, unless you've applied the TUN/TAP patch to
184 	  To use this transport, your host kernel must have support for TUN/TAP
188 	  migrate to UML_NET_VECTOR.
196 	  The slip User-Mode Linux network transport allows a running UML to
197 	  network with its host over a point-to-point link.  Unlike Ethertap,
201 	  To use this, your host must support slip devices.
205 	  has examples of the UML command line to use to enable slip
209 	  migrate to UML_NET_VECTOR.
218 	  UMLs on a single host to communicate with each other, but not to
221 	  To use this form of networking, you'll need to run the UML
226 	  has examples of the UML command line to use to enable Daemon
230 	  migrate to UML_NET_VECTOR.
243 	with up to 4 times higher network throughput than the UML network
252 	UMLs on a single host to communicate with each other and also
256 	You must have libvdeplug installed in order to build the vde
259 	To use this form of networking, you will need to run vde_switch
264 	of the UML command line to use to enable VDE networking.
267 	migrate to UML_NET_VECTOR.
276 	  UMLs (even ones running on different host machines!) to talk to
278 	  at least one UML with one of the other transports to act as a
279 	  bridge if any of them need to be able to talk to their hosts or any
282 	  To use this, your host kernel(s) must support IP Multicasting.
286 	  has examples of the UML command line to use to enable Multicast
290 	  migrate to UML_NET_VECTOR.
302 	installed in order to build the pcap transport into UML.
306 	  has examples of the UML command line to use to enable this option.
309 	migrate to UML_NET_VECTOR.
318 	  to network by invoking a program that can handle SLIP encapsulated
319 	  packets.  This is commonly (but not limited to) the application
324 	  to the outside world that the host user is permitted, and unlike
335 	  migrate to UML_NET_VECTOR.