5 # XXX: does UM have a mmu/swap?
10 mainmenu "Linux/Usermode Kernel Configuration"
25 config RWSEM_GENERIC_SPINLOCK
29 menu "UML-specific options"
32 bool "Tracing thread support"
35 This option controls whether tracing thread support is compiled
36 into UML. Normally, this should be set to Y. If you intend to
37 use only skas mode (and the host has the skas patch applied to it),
38 then it is OK to say N here.
41 bool "Force a static link"
45 If CONFIG_MODE_TT is disabled, then this option gives you the ability
46 to force a static link of UML. Normally, if only skas mode is built
47 in to UML, it will be linked as a shared binary. This is inconvenient
48 for use in a chroot jail. So, if you intend to run UML inside a
49 chroot, and you disable CONFIG_MODE_TT, you probably want to say Y
53 bool "Separate Kernel Address Space support"
56 This option controls whether skas (separate kernel address space)
57 support is compiled in. If you have applied the skas patch to the
58 host, then you certainly want to say Y here (and consider saying N
59 to CONFIG_MODE_TT). Otherwise, it is safe to say Y. Disabling this
60 option will shrink the UML binary slightly.
63 bool "Networking support"
65 Unless you really know what you are doing, you should say Y here.
66 The reason is that some programs need kernel networking support even
67 when running on a stand-alone machine that isn't connected to any
68 other computer. If you are upgrading from an older kernel, you
69 should consider updating your networking tools too because changes
70 in the kernel and the tools often go hand in hand. The tools are
71 contained in the package net-tools, the location and version number
72 of which are given in Documentation/Changes.
74 For a general introduction to Linux networking, it is highly
75 recommended to read the NET-HOWTO, available from
76 <http://www.tldp.org/docs.html#howto>.
79 source "fs/Kconfig.binfmt"
82 tristate "Host filesystem"
84 While the User-Mode Linux port uses its own root file system for
85 booting and normal file access, this module lets the UML user
86 access files stored on the host. It does not require any
87 network connection between the Host and UML. An example use of
90 mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
92 where /tmp/fromhost is an empty directory inside UML and
93 /tmp/umlshare is a directory on the host with files the UML user
96 For more information, see
97 <http://user-mode-linux.sourceforge.net/hostfs.html>.
99 If you'd like to be able to work with files stored on the host,
100 say Y or M here; otherwise say N.
103 tristate "HoneyPot ProcFS"
105 hppfs (HoneyPot ProcFS) is a filesystem which allows UML /proc
106 entries to be overridden, removed, or fabricated from the host.
107 Its purpose is to allow a UML to appear to be a physical machine
108 by removing or changing anything in /proc which gives away the
111 See http://user-mode-linux.sf.net/hppfs.html for more information.
113 You only need this if you are setting up a UML honeypot. Otherwise,
114 it is safe to say 'N' here.
117 bool "Management console"
119 The user mode linux management console is a low-level interface to
120 the kernel, somewhat like the i386 SysRq interface. Since there is
121 a full-blown operating system running under every user mode linux
122 instance, there is much greater flexibility possible than with the
125 If you answer 'Y' to this option, to use this feature, you need the
126 mconsole client (called uml_mconsole) which is present in CVS in
127 2.4.5-9um and later (path /tools/mconsole), and is also in the
128 distribution RPM package in 2.4.6 and later.
130 It is safe to say 'Y' here.
133 bool "2G/2G host address space split"
136 bool "Symmetric multi-processing support"
139 This option enables UML SMP support. UML implements virtual SMP by
140 allowing as many processes to run simultaneously on the host as
141 there are virtual processors configured. Obviously, if the host is
142 a uniprocessor, those processes will timeshare, but, inside UML,
143 will appear to be running simultaneously. If the host is a
144 multiprocessor, then UML processes may run simultaneously, depending
145 on the host scheduler.
146 It is safe to leave this unchanged.
149 int "Maximum number of CPUs (2-32)"
158 This is set to the number of layers of UMLs that this UML will be run
159 in. Normally, this is zero, meaning that it will run directly on the
160 host. Setting it to one will build a UML that can run inside a UML
161 that is running on the host. Generally, if you intend this UML to run
162 inside another UML, set CONFIG_NEST_LEVEL to one more than the host
165 Note that if the hosting UML has its CONFIG_KERNEL_HALF_GIGS set to
166 greater than one, then the guest UML should have its CONFIG_NEST_LEVEL
167 set to the host's CONFIG_NEST_LEVEL + CONFIG_KERNEL_HALF_GIGS.
168 Only change this if you are running nested UMLs.
170 config KERNEL_HALF_GIGS
171 int "Kernel address space size (in .5G units)"
174 This determines the amount of address space that UML will allocate for
175 its own, measured in half Gigabyte units. The default is 1.
176 Change this only if you need to boot UML with an unusually large amount
180 bool "Highmem support"
183 config KERNEL_STACK_ORDER
184 int "Kernel stack size order"
187 This option determines the size of UML kernel stacks. They will
188 be 1 << order pages. The default is OK unless you're running Valgrind
189 on UML, in which case, set this to 3.
191 config UML_REAL_TIME_CLOCK
192 bool "Real-time Clock"
195 This option makes UML time deltas match wall clock deltas. This should
196 normally be enabled. The exception would be if you are debugging with
197 UML and spend long times with UML stopped at a breakpoint. In this
198 case, when UML is restarted, it will call the timer enough times to make
199 up for the time spent at the breakpoint. This could result in a
200 noticable lag. If this is a problem, then disable this option.
204 source "init/Kconfig"
206 source "drivers/base/Kconfig"
208 source "arch/um/Kconfig_char"
210 source "arch/um/Kconfig_block"
216 source "arch/um/Kconfig_net"
222 source "kernel/vserver/Kconfig"
224 source "security/Kconfig"
226 source "crypto/Kconfig"
234 tristate "SCSI support"
236 # This gives us free_dma, which scsi.c wants.
237 config GENERIC_ISA_DMA
242 source "arch/um/Kconfig_scsi"
246 source "drivers/md/Kconfig"
249 source "drivers/mtd/Kconfig"
252 source "arch/um/Kconfig.debug"