Kconfig 6.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269
  1. config DEFCONFIG_LIST
  2. string
  3. option defconfig_list
  4. default "arch/$ARCH/defconfig"
  5. # UML uses the generic IRQ subsystem
  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. config GENERIC_TIME
  44. bool
  45. default y
  46. config GENERIC_CLOCKEVENTS
  47. bool
  48. default y
  49. # Used in kernel/irq/manage.c and include/linux/irq.h
  50. config IRQ_RELEASE_METHOD
  51. bool
  52. default y
  53. config HZ
  54. int
  55. default 100
  56. menu "UML-specific options"
  57. config STATIC_LINK
  58. bool "Force a static link"
  59. default n
  60. help
  61. This option gives you the ability to force a static link of UML.
  62. Normally, UML is linked as a shared binary. This is inconvenient for
  63. use in a chroot jail. So, if you intend to run UML inside a chroot,
  64. you probably want to say Y here.
  65. Additionally, this option enables using higher memory spaces (up to
  66. 2.75G) for UML.
  67. source "arch/um/Kconfig.arch"
  68. source "mm/Kconfig"
  69. source "kernel/time/Kconfig"
  70. config LD_SCRIPT_STATIC
  71. bool
  72. default y
  73. depends on STATIC_LINK
  74. config LD_SCRIPT_DYN
  75. bool
  76. default y
  77. depends on !LD_SCRIPT_STATIC
  78. source "fs/Kconfig.binfmt"
  79. config HOSTFS
  80. tristate "Host filesystem"
  81. help
  82. While the User-Mode Linux port uses its own root file system for
  83. booting and normal file access, this module lets the UML user
  84. access files stored on the host. It does not require any
  85. network connection between the Host and UML. An example use of
  86. this might be:
  87. mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
  88. where /tmp/fromhost is an empty directory inside UML and
  89. /tmp/umlshare is a directory on the host with files the UML user
  90. wishes to access.
  91. For more information, see
  92. <http://user-mode-linux.sourceforge.net/hostfs.html>.
  93. If you'd like to be able to work with files stored on the host,
  94. say Y or M here; otherwise say N.
  95. config HPPFS
  96. tristate "HoneyPot ProcFS (EXPERIMENTAL)"
  97. depends on EXPERIMENTAL
  98. help
  99. hppfs (HoneyPot ProcFS) is a filesystem which allows UML /proc
  100. entries to be overridden, removed, or fabricated from the host.
  101. Its purpose is to allow a UML to appear to be a physical machine
  102. by removing or changing anything in /proc which gives away the
  103. identity of a UML.
  104. See <http://user-mode-linux.sf.net/old/hppfs.html> for more information.
  105. You only need this if you are setting up a UML honeypot. Otherwise,
  106. it is safe to say 'N' here.
  107. config MCONSOLE
  108. bool "Management console"
  109. default y
  110. help
  111. The user mode linux management console is a low-level interface to
  112. the kernel, somewhat like the i386 SysRq interface. Since there is
  113. a full-blown operating system running under every user mode linux
  114. instance, there is much greater flexibility possible than with the
  115. SysRq mechanism.
  116. If you answer 'Y' to this option, to use this feature, you need the
  117. mconsole client (called uml_mconsole) which is present in CVS in
  118. 2.4.5-9um and later (path /tools/mconsole), and is also in the
  119. distribution RPM package in 2.4.6 and later.
  120. It is safe to say 'Y' here.
  121. config MAGIC_SYSRQ
  122. bool "Magic SysRq key"
  123. depends on MCONSOLE
  124. help
  125. If you say Y here, you will have some control over the system even
  126. if the system crashes for example during kernel debugging (e.g., you
  127. will be able to flush the buffer cache to disk, reboot the system
  128. immediately or dump some status information). A key for each of the
  129. possible requests is provided.
  130. This is the feature normally accomplished by pressing a key
  131. while holding SysRq (Alt+PrintScreen).
  132. On UML, this is accomplished by sending a "sysrq" command with
  133. mconsole, followed by the letter for the requested command.
  134. The keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
  135. unless you really know what this hack does.
  136. config SMP
  137. bool "Symmetric multi-processing support (EXPERIMENTAL)"
  138. default n
  139. depends on BROKEN
  140. help
  141. This option enables UML SMP support.
  142. It is NOT related to having a real SMP box. Not directly, at least.
  143. UML implements virtual SMP by allowing as many processes to run
  144. simultaneously on the host as there are virtual processors configured.
  145. Obviously, if the host is a uniprocessor, those processes will
  146. timeshare, but, inside UML, will appear to be running simultaneously.
  147. If the host is a multiprocessor, then UML processes may run
  148. simultaneously, depending on the host scheduler.
  149. This, however, is supported only in TT mode. So, if you use the SKAS
  150. patch on your host, switching to TT mode and enabling SMP usually
  151. gives you worse performances.
  152. Also, since the support for SMP has been under-developed, there could
  153. be some bugs being exposed by enabling SMP.
  154. If you don't know what to do, say N.
  155. config NR_CPUS
  156. int "Maximum number of CPUs (2-32)"
  157. range 2 32
  158. depends on SMP
  159. default "32"
  160. config HIGHMEM
  161. bool "Highmem support (EXPERIMENTAL)"
  162. depends on !64BIT && EXPERIMENTAL
  163. default n
  164. help
  165. This was used to allow UML to run with big amounts of memory.
  166. Currently it is unstable, so if unsure say N.
  167. To use big amounts of memory, it is recommended enable static
  168. linking (i.e. CONFIG_STATIC_LINK) - this should allow the
  169. guest to use up to 2.75G of memory.
  170. config KERNEL_STACK_ORDER
  171. int "Kernel stack size order"
  172. default 1 if 64BIT
  173. range 1 10 if 64BIT
  174. default 0 if !64BIT
  175. help
  176. This option determines the size of UML kernel stacks. They will
  177. be 1 << order pages. The default is OK unless you're running Valgrind
  178. on UML, in which case, set this to 3.
  179. endmenu
  180. source "init/Kconfig"
  181. source "drivers/block/Kconfig"
  182. source "arch/um/Kconfig.char"
  183. source "drivers/base/Kconfig"
  184. source "net/Kconfig"
  185. source "arch/um/Kconfig.net"
  186. source "drivers/net/Kconfig"
  187. source "drivers/connector/Kconfig"
  188. source "fs/Kconfig"
  189. source "security/Kconfig"
  190. source "crypto/Kconfig"
  191. source "lib/Kconfig"
  192. source "drivers/scsi/Kconfig"
  193. source "drivers/md/Kconfig"
  194. if BROKEN
  195. source "drivers/mtd/Kconfig"
  196. endif
  197. source "drivers/leds/Kconfig"
  198. #This is just to shut up some Kconfig warnings, so no prompt.
  199. config INPUT
  200. bool
  201. default n
  202. source "arch/um/Kconfig.debug"