arch/um/Kconfig

   1 config DEFCONFIG_LIST
   2         string
   3         option defconfig_list
   4         default "arch/$ARCH/defconfig"
   5
   6 # UML uses the generic IRQ subsystem
   7 config GENERIC_HARDIRQS
   8         bool
   9         default y
  10
  11 config UML
  12         bool
  13         default y
  14
  15 config MMU
  16         bool
  17         default y
  18
  19 config NO_IOMEM
  20         def_bool y
  21
  22 mainmenu "Linux/Usermode Kernel Configuration"
  23
  24 config ISA
  25         bool
  26
  27 config SBUS
  28         bool
  29
  30 config PCI
  31         bool
  32
  33 config PCMCIA
  34         bool
  35
  36 # Yet to do!
  37 config TRACE_IRQFLAGS_SUPPORT
  38         bool
  39         default n
  40
  41 config LOCKDEP_SUPPORT
  42         bool
  43         default y
  44
  45 config STACKTRACE_SUPPORT
  46         bool
  47         default n
  48
  49 config GENERIC_CALIBRATE_DELAY
  50         bool
  51         default y
  52
  53 config GENERIC_BUG
  54         bool
  55         default y
  56         depends on BUG
  57
  58 config GENERIC_TIME
  59         bool
  60         default y
  61
  62 config GENERIC_CLOCKEVENTS
  63         bool
  64         default y
  65
  66 # Used in kernel/irq/manage.c and include/linux/irq.h
  67 config IRQ_RELEASE_METHOD
  68         bool
  69         default y
  70
  71 config HZ
  72         int
  73         default 100
  74
  75 menu "UML-specific options"
  76
  77 config STATIC_LINK
  78         bool "Force a static link"
  79         default n
  80         help
  81           This option gives you the ability to force a static link of UML.
  82           Normally, UML is linked as a shared binary.  This is inconvenient for
  83           use in a chroot jail.  So, if you intend to run UML inside a chroot,
  84           you probably want to say Y here.
  85           Additionally, this option enables using higher memory spaces (up to
  86           2.75G) for UML.
  87
  88 source "arch/um/Kconfig.arch"
  89 source "mm/Kconfig"
  90 source "kernel/time/Kconfig"
  91
  92 config LD_SCRIPT_STATIC
  93         bool
  94         default y
  95         depends on STATIC_LINK
  96
  97 config LD_SCRIPT_DYN
  98         bool
  99         default y
 100         depends on !LD_SCRIPT_STATIC
 101
 102 source "fs/Kconfig.binfmt"
 103
 104 config HOSTFS
 105         tristate "Host filesystem"
 106         help
 107           While the User-Mode Linux port uses its own root file system for
 108           booting and normal file access, this module lets the UML user
 109           access files stored on the host.  It does not require any
 110           network connection between the Host and UML.  An example use of
 111           this might be:
 112
 113           mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
 114
 115           where /tmp/fromhost is an empty directory inside UML and
 116           /tmp/umlshare is a directory on the host with files the UML user
 117           wishes to access.
 118
 119           For more information, see
 120           <http://user-mode-linux.sourceforge.net/hostfs.html>.
 121
 122           If you'd like to be able to work with files stored on the host,
 123           say Y or M here; otherwise say N.
 124
 125 config HPPFS
 126         tristate "HoneyPot ProcFS (EXPERIMENTAL)"
 127         depends on EXPERIMENTAL
 128         help
 129           hppfs (HoneyPot ProcFS) is a filesystem which allows UML /proc
 130           entries to be overridden, removed, or fabricated from the host.
 131           Its purpose is to allow a UML to appear to be a physical machine
 132           by removing or changing anything in /proc which gives away the
 133           identity of a UML.
 134
 135           See <http://user-mode-linux.sf.net/old/hppfs.html> for more information.
 136
 137           You only need this if you are setting up a UML honeypot.  Otherwise,
 138           it is safe to say 'N' here.
 139
 140 config MCONSOLE
 141         bool "Management console"
 142         default y
 143         help
 144           The user mode linux management console is a low-level interface to
 145           the kernel, somewhat like the i386 SysRq interface.  Since there is
 146           a full-blown operating system running under every user mode linux
 147           instance, there is much greater flexibility possible than with the
 148           SysRq mechanism.
 149
 150           If you answer 'Y' to this option, to use this feature, you need the
 151           mconsole client (called uml_mconsole) which is present in CVS in
 152           2.4.5-9um and later (path /tools/mconsole), and is also in the
 153           distribution RPM package in 2.4.6 and later.
 154
 155           It is safe to say 'Y' here.
 156
 157 config MAGIC_SYSRQ
 158         bool "Magic SysRq key"
 159         depends on MCONSOLE
 160         help
 161           If you say Y here, you will have some control over the system even
 162           if the system crashes for example during kernel debugging (e.g., you
 163           will be able to flush the buffer cache to disk, reboot the system
 164           immediately or dump some status information). A key for each of the
 165           possible requests is provided.
 166
 167           This is the feature normally accomplished by pressing a key
 168           while holding SysRq (Alt+PrintScreen).
 169
 170           On UML, this is accomplished by sending a "sysrq" command with
 171           mconsole, followed by the letter for the requested command.
 172
 173           The keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
 174           unless you really know what this hack does.
 175
 176 config SMP
 177         bool "Symmetric multi-processing support (EXPERIMENTAL)"
 178         default n
 179         depends on BROKEN
 180         help
 181           This option enables UML SMP support.
 182           It is NOT related to having a real SMP box. Not directly, at least.
 183
 184           UML implements virtual SMP by allowing as many processes to run
 185           simultaneously on the host as there are virtual processors configured.
 186
 187           Obviously, if the host is a uniprocessor, those processes will
 188           timeshare, but, inside UML, will appear to be running simultaneously.
 189           If the host is a multiprocessor, then UML processes may run
 190           simultaneously, depending on the host scheduler.
 191
 192           This, however, is supported only in TT mode. So, if you use the SKAS
 193           patch on your host, switching to TT mode and enabling SMP usually
 194           gives you worse performances.
 195           Also, since the support for SMP has been under-developed, there could
 196           be some bugs being exposed by enabling SMP.
 197
 198           If you don't know what to do, say N.
 199
 200 config NR_CPUS
 201         int "Maximum number of CPUs (2-32)"
 202         range 2 32
 203         depends on SMP
 204         default "32"
 205
 206 config NEST_LEVEL
 207         int "Nesting level"
 208         default "0"
 209         help
 210           This is set to the number of layers of UMLs that this UML will be run
 211           in.  Normally, this is zero, meaning that it will run directly on the
 212           host.  Setting it to one will build a UML that can run inside a UML
 213           that is running on the host.  Generally, if you intend this UML to run
 214           inside another UML, set CONFIG_NEST_LEVEL to one more than the host
 215           UML.
 216
 217 config HIGHMEM
 218         bool "Highmem support (EXPERIMENTAL)"
 219         depends on !64BIT && EXPERIMENTAL
 220         default n
 221         help
 222           This was used to allow UML to run with big amounts of memory.
 223           Currently it is unstable, so if unsure say N.
 224
 225           To use big amounts of memory, it is recommended enable static
 226           linking (i.e. CONFIG_STATIC_LINK) - this should allow the
 227           guest to use up to 2.75G of memory.
 228
 229 config KERNEL_STACK_ORDER
 230         int "Kernel stack size order"
 231         default 1 if 64BIT
 232         range 1 10 if 64BIT
 233         default 0 if !64BIT
 234         help
 235           This option determines the size of UML kernel stacks.  They will
 236           be 1 << order pages.  The default is OK unless you're running Valgrind
 237           on UML, in which case, set this to 3.
 238
 239 endmenu
 240
 241 source "init/Kconfig"
 242
 243 source "drivers/block/Kconfig"
 244
 245 source "arch/um/Kconfig.char"
 246
 247 source "drivers/base/Kconfig"
 248
 249 source "net/Kconfig"
 250
 251 source "arch/um/Kconfig.net"
 252
 253 source "drivers/net/Kconfig"
 254
 255 source "drivers/connector/Kconfig"
 256
 257 source "fs/Kconfig"
 258
 259 source "security/Kconfig"
 260
 261 source "crypto/Kconfig"
 262
 263 source "lib/Kconfig"
 264
 265 source "drivers/scsi/Kconfig"
 266
 267 source "drivers/md/Kconfig"
 268
 269 if BROKEN
 270         source "drivers/mtd/Kconfig"
 271 endif
 272
 273 #This is just to shut up some Kconfig warnings, so no prompt.
 274 config INPUT
 275         bool
 276         default n
 277
 278 source "arch/um/Kconfig.debug"