Kconfig 7.9 KB

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