Kconfig 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191
  1. # SPDX-License-Identifier: GPL-2.0
  2. menu "UML-specific options"
  3. config UML
  4. bool
  5. default y
  6. select ARCH_HAS_KCOV
  7. select ARCH_NO_PREEMPT
  8. select HAVE_ARCH_AUDITSYSCALL
  9. select HAVE_ARCH_SECCOMP_FILTER
  10. select HAVE_UID16
  11. select HAVE_FUTEX_CMPXCHG if FUTEX
  12. select HAVE_DEBUG_KMEMLEAK
  13. select GENERIC_IRQ_SHOW
  14. select GENERIC_CPU_DEVICES
  15. select GENERIC_CLOCKEVENTS
  16. select HAVE_GCC_PLUGINS
  17. select TTY # Needed for line.c
  18. config MMU
  19. bool
  20. default y
  21. config NO_IOMEM
  22. def_bool y
  23. config ISA
  24. bool
  25. config SBUS
  26. bool
  27. config PCI
  28. bool
  29. config PCMCIA
  30. bool
  31. config TRACE_IRQFLAGS_SUPPORT
  32. bool
  33. default y
  34. config LOCKDEP_SUPPORT
  35. bool
  36. default y
  37. config STACKTRACE_SUPPORT
  38. bool
  39. default y
  40. select STACKTRACE
  41. config GENERIC_CALIBRATE_DELAY
  42. bool
  43. default y
  44. config HZ
  45. int
  46. default 100
  47. config NR_CPUS
  48. int
  49. range 1 1
  50. default 1
  51. source "arch/$(HEADER_ARCH)/um/Kconfig"
  52. config STATIC_LINK
  53. bool "Force a static link"
  54. default n
  55. help
  56. This option gives you the ability to force a static link of UML.
  57. Normally, UML is linked as a shared binary. This is inconvenient for
  58. use in a chroot jail. So, if you intend to run UML inside a chroot,
  59. you probably want to say Y here.
  60. Additionally, this option enables using higher memory spaces (up to
  61. 2.75G) for UML.
  62. config LD_SCRIPT_STATIC
  63. bool
  64. default y
  65. depends on STATIC_LINK
  66. config LD_SCRIPT_DYN
  67. bool
  68. default y
  69. depends on !LD_SCRIPT_STATIC
  70. select MODULE_REL_CRCS if MODVERSIONS
  71. config HOSTFS
  72. tristate "Host filesystem"
  73. help
  74. While the User-Mode Linux port uses its own root file system for
  75. booting and normal file access, this module lets the UML user
  76. access files stored on the host. It does not require any
  77. network connection between the Host and UML. An example use of
  78. this might be:
  79. mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
  80. where /tmp/fromhost is an empty directory inside UML and
  81. /tmp/umlshare is a directory on the host with files the UML user
  82. wishes to access.
  83. For more information, see
  84. <http://user-mode-linux.sourceforge.net/hostfs.html>.
  85. If you'd like to be able to work with files stored on the host,
  86. say Y or M here; otherwise say N.
  87. config MCONSOLE
  88. bool "Management console"
  89. depends on PROC_FS
  90. default y
  91. help
  92. The user mode linux management console is a low-level interface to
  93. the kernel, somewhat like the i386 SysRq interface. Since there is
  94. a full-blown operating system running under every user mode linux
  95. instance, there is much greater flexibility possible than with the
  96. SysRq mechanism.
  97. If you answer 'Y' to this option, to use this feature, you need the
  98. mconsole client (called uml_mconsole) which is present in CVS in
  99. 2.4.5-9um and later (path /tools/mconsole), and is also in the
  100. distribution RPM package in 2.4.6 and later.
  101. It is safe to say 'Y' here.
  102. config MAGIC_SYSRQ
  103. bool "Magic SysRq key"
  104. depends on MCONSOLE
  105. help
  106. If you say Y here, you will have some control over the system even
  107. if the system crashes for example during kernel debugging (e.g., you
  108. will be able to flush the buffer cache to disk, reboot the system
  109. immediately or dump some status information). A key for each of the
  110. possible requests is provided.
  111. This is the feature normally accomplished by pressing a key
  112. while holding SysRq (Alt+PrintScreen).
  113. On UML, this is accomplished by sending a "sysrq" command with
  114. mconsole, followed by the letter for the requested command.
  115. The keys are documented in <file:Documentation/admin-guide/sysrq.rst>. Don't say Y
  116. unless you really know what this hack does.
  117. config KERNEL_STACK_ORDER
  118. int "Kernel stack size order"
  119. default 1 if 64BIT
  120. range 1 10 if 64BIT
  121. default 0 if !64BIT
  122. help
  123. This option determines the size of UML kernel stacks. They will
  124. be 1 << order pages. The default is OK unless you're running Valgrind
  125. on UML, in which case, set this to 3.
  126. config MMAPPER
  127. tristate "iomem emulation driver"
  128. help
  129. This driver allows a host file to be used as emulated IO memory inside
  130. UML.
  131. config NO_DMA
  132. def_bool y
  133. config PGTABLE_LEVELS
  134. int
  135. default 3 if 3_LEVEL_PGTABLES
  136. default 2
  137. config SECCOMP
  138. def_bool y
  139. prompt "Enable seccomp to safely compute untrusted bytecode"
  140. ---help---
  141. This kernel feature is useful for number crunching applications
  142. that may need to compute untrusted bytecode during their
  143. execution. By using pipes or other transports made available to
  144. the process as file descriptors supporting the read/write
  145. syscalls, it's possible to isolate those applications in
  146. their own address space using seccomp. Once seccomp is
  147. enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
  148. and the task is only allowed to execute a few safe syscalls
  149. defined by each seccomp mode.
  150. If unsure, say Y.
  151. endmenu
  152. source "arch/um/drivers/Kconfig"