Kconfig 6.6 KB

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