Kconfig 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416
  1. # For a description of the syntax of this configuration file,
  2. # see Documentation/kbuild/kconfig-language.txt.
  3. config TILE
  4. def_bool y
  5. select HAVE_KVM if !TILEGX
  6. select GENERIC_FIND_FIRST_BIT
  7. select USE_GENERIC_SMP_HELPERS
  8. select CC_OPTIMIZE_FOR_SIZE
  9. select HAVE_GENERIC_HARDIRQS
  10. select GENERIC_IRQ_PROBE
  11. select GENERIC_PENDING_IRQ if SMP
  12. select GENERIC_IRQ_SHOW
  13. select HAVE_SYSCALL_WRAPPERS if TILEGX
  14. select SYS_HYPERVISOR
  15. select ARCH_HAVE_NMI_SAFE_CMPXCHG
  16. # FIXME: investigate whether we need/want these options.
  17. # select HAVE_IOREMAP_PROT
  18. # select HAVE_OPTPROBES
  19. # select HAVE_REGS_AND_STACK_ACCESS_API
  20. # select HAVE_HW_BREAKPOINT
  21. # select PERF_EVENTS
  22. # select HAVE_USER_RETURN_NOTIFIER
  23. # config NO_BOOTMEM
  24. # config ARCH_SUPPORTS_DEBUG_PAGEALLOC
  25. # config HUGETLB_PAGE_SIZE_VARIABLE
  26. config MMU
  27. def_bool y
  28. config GENERIC_CSUM
  29. def_bool y
  30. config SEMAPHORE_SLEEPERS
  31. def_bool y
  32. config HAVE_ARCH_ALLOC_REMAP
  33. def_bool y
  34. config HAVE_SETUP_PER_CPU_AREA
  35. def_bool y
  36. config NEED_PER_CPU_PAGE_FIRST_CHUNK
  37. def_bool y
  38. config SYS_SUPPORTS_HUGETLBFS
  39. def_bool y
  40. # Support for additional huge page sizes besides HPAGE_SIZE.
  41. # The software support is currently only present in the TILE-Gx
  42. # hypervisor. TILEPro in any case does not support page sizes
  43. # larger than the default HPAGE_SIZE.
  44. config HUGETLB_SUPER_PAGES
  45. depends on HUGETLB_PAGE && TILEGX
  46. def_bool y
  47. config GENERIC_CLOCKEVENTS
  48. def_bool y
  49. # FIXME: tilegx can implement a more efficient rwsem.
  50. config RWSEM_GENERIC_SPINLOCK
  51. def_bool y
  52. # We have a very flat architecture from a migration point of view,
  53. # so save boot time by presetting this (particularly useful on tile-sim).
  54. config DEFAULT_MIGRATION_COST
  55. int
  56. default "10000000"
  57. # We only support gcc 4.4 and above, so this should work.
  58. config ARCH_SUPPORTS_OPTIMIZED_INLINING
  59. def_bool y
  60. config ARCH_PHYS_ADDR_T_64BIT
  61. def_bool y
  62. config ARCH_DMA_ADDR_T_64BIT
  63. def_bool y
  64. config NEED_DMA_MAP_STATE
  65. def_bool y
  66. config LOCKDEP_SUPPORT
  67. def_bool y
  68. config STACKTRACE_SUPPORT
  69. def_bool y
  70. select STACKTRACE
  71. # We use discontigmem for now; at some point we may want to switch
  72. # to sparsemem (Tilera bug 7996).
  73. config ARCH_DISCONTIGMEM_ENABLE
  74. def_bool y
  75. config ARCH_DISCONTIGMEM_DEFAULT
  76. def_bool y
  77. config TRACE_IRQFLAGS_SUPPORT
  78. def_bool y
  79. config STRICT_DEVMEM
  80. def_bool y
  81. # SMP is required for Tilera Linux.
  82. config SMP
  83. def_bool y
  84. # Allow checking for compile-time determined overflow errors in
  85. # copy_from_user(). There are still unprovable places in the
  86. # generic code as of 2.6.34, so this option is not really compatible
  87. # with -Werror, which is more useful in general.
  88. config DEBUG_COPY_FROM_USER
  89. def_bool n
  90. config HVC_TILE
  91. select HVC_DRIVER
  92. def_bool y
  93. # Please note: TILE-Gx support is not yet finalized; this is
  94. # the preliminary support. TILE-Gx drivers are only provided
  95. # with the alpha or beta test versions for Tilera customers.
  96. config TILEGX
  97. depends on EXPERIMENTAL
  98. bool "Building with TILE-Gx (64-bit) compiler and toolchain"
  99. config 64BIT
  100. depends on TILEGX
  101. def_bool y
  102. config ARCH_DEFCONFIG
  103. string
  104. default "arch/tile/configs/tilepro_defconfig" if !TILEGX
  105. default "arch/tile/configs/tilegx_defconfig" if TILEGX
  106. source "init/Kconfig"
  107. menu "Tilera-specific configuration"
  108. config NR_CPUS
  109. int "Maximum number of tiles (2-255)"
  110. range 2 255
  111. depends on SMP
  112. default "64"
  113. ---help---
  114. Building with 64 is the recommended value, but a slightly
  115. smaller kernel memory footprint results from using a smaller
  116. value on chips with fewer tiles.
  117. if TILEGX
  118. choice
  119. prompt "Kernel page size"
  120. default PAGE_SIZE_64KB
  121. help
  122. This lets you select the page size of the kernel. For best
  123. performance on memory-intensive applications, a page size of 64KB
  124. is recommended. For workloads involving many small files, many
  125. connections, etc., it may be better to select 16KB, which uses
  126. memory more efficiently at some cost in TLB performance.
  127. Note that this option is TILE-Gx specific; currently
  128. TILEPro page size is set by rebuilding the hypervisor.
  129. config PAGE_SIZE_16KB
  130. bool "16KB"
  131. config PAGE_SIZE_64KB
  132. bool "64KB"
  133. endchoice
  134. endif
  135. source "kernel/time/Kconfig"
  136. source "kernel/Kconfig.hz"
  137. config KEXEC
  138. bool "kexec system call"
  139. ---help---
  140. kexec is a system call that implements the ability to shutdown your
  141. current kernel, and to start another kernel. It is like a reboot
  142. but it is independent of the system firmware. It is used
  143. to implement the "mboot" Tilera booter.
  144. The name comes from the similarity to the exec system call.
  145. config COMPAT
  146. bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
  147. depends on TILEGX
  148. select COMPAT_BINFMT_ELF
  149. default y
  150. ---help---
  151. If enabled, the kernel will support running TILE-Gx binaries
  152. that were built with the -m32 option.
  153. config SYSVIPC_COMPAT
  154. def_bool y
  155. depends on COMPAT && SYSVIPC
  156. # We do not currently support disabling HIGHMEM on tile64 and tilepro.
  157. config HIGHMEM
  158. bool # "Support for more than 512 MB of RAM"
  159. default !TILEGX
  160. ---help---
  161. Linux can use the full amount of RAM in the system by
  162. default. However, the address space of TILE processors is
  163. only 4 Gigabytes large. That means that, if you have a large
  164. amount of physical memory, not all of it can be "permanently
  165. mapped" by the kernel. The physical memory that's not
  166. permanently mapped is called "high memory".
  167. If you are compiling a kernel which will never run on a
  168. machine with more than 512 MB total physical RAM, answer
  169. "false" here. This will result in the kernel mapping all of
  170. physical memory into the top 1 GB of virtual memory space.
  171. If unsure, say "true".
  172. # We do not currently support disabling NUMA.
  173. config NUMA
  174. bool # "NUMA Memory Allocation and Scheduler Support"
  175. depends on SMP && DISCONTIGMEM
  176. default y
  177. ---help---
  178. NUMA memory allocation is required for TILE processors
  179. unless booting with memory striping enabled in the
  180. hypervisor, or with only a single memory controller.
  181. It is recommended that this option always be enabled.
  182. config NODES_SHIFT
  183. int "Log base 2 of the max number of memory controllers"
  184. default 2
  185. depends on NEED_MULTIPLE_NODES
  186. ---help---
  187. By default, 2, i.e. 2^2 == 4 DDR2 controllers.
  188. In a system with more controllers, this value should be raised.
  189. choice
  190. depends on !TILEGX
  191. prompt "Memory split" if EXPERT
  192. default VMSPLIT_3G
  193. ---help---
  194. Select the desired split between kernel and user memory.
  195. If the address range available to the kernel is less than the
  196. physical memory installed, the remaining memory will be available
  197. as "high memory". Accessing high memory is a little more costly
  198. than low memory, as it needs to be mapped into the kernel first.
  199. Note that increasing the kernel address space limits the range
  200. available to user programs, making the address space there
  201. tighter. Selecting anything other than the default 3G/1G split
  202. will also likely make your kernel incompatible with binary-only
  203. kernel modules.
  204. If you are not absolutely sure what you are doing, leave this
  205. option alone!
  206. config VMSPLIT_3_75G
  207. bool "3.75G/0.25G user/kernel split (no kernel networking)"
  208. config VMSPLIT_3_5G
  209. bool "3.5G/0.5G user/kernel split"
  210. config VMSPLIT_3G
  211. bool "3G/1G user/kernel split"
  212. config VMSPLIT_2_75G
  213. bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
  214. config VMSPLIT_2_5G
  215. bool "2.5G/1.5G user/kernel split"
  216. config VMSPLIT_2_25G
  217. bool "2.25G/1.75G user/kernel split"
  218. config VMSPLIT_2G
  219. bool "2G/2G user/kernel split"
  220. config VMSPLIT_1G
  221. bool "1G/3G user/kernel split"
  222. endchoice
  223. config PAGE_OFFSET
  224. hex
  225. depends on !64BIT
  226. default 0xF0000000 if VMSPLIT_3_75G
  227. default 0xE0000000 if VMSPLIT_3_5G
  228. default 0xB0000000 if VMSPLIT_2_75G
  229. default 0xA0000000 if VMSPLIT_2_5G
  230. default 0x90000000 if VMSPLIT_2_25G
  231. default 0x80000000 if VMSPLIT_2G
  232. default 0x40000000 if VMSPLIT_1G
  233. default 0xC0000000
  234. source "mm/Kconfig"
  235. config CMDLINE_BOOL
  236. bool "Built-in kernel command line"
  237. default n
  238. ---help---
  239. Allow for specifying boot arguments to the kernel at
  240. build time. On some systems (e.g. embedded ones), it is
  241. necessary or convenient to provide some or all of the
  242. kernel boot arguments with the kernel itself (that is,
  243. to not rely on the boot loader to provide them.)
  244. To compile command line arguments into the kernel,
  245. set this option to 'Y', then fill in the
  246. the boot arguments in CONFIG_CMDLINE.
  247. Systems with fully functional boot loaders (e.g. mboot, or
  248. if booting over PCI) should leave this option set to 'N'.
  249. config CMDLINE
  250. string "Built-in kernel command string"
  251. depends on CMDLINE_BOOL
  252. default ""
  253. ---help---
  254. Enter arguments here that should be compiled into the kernel
  255. image and used at boot time. If the boot loader provides a
  256. command line at boot time, it is appended to this string to
  257. form the full kernel command line, when the system boots.
  258. However, you can use the CONFIG_CMDLINE_OVERRIDE option to
  259. change this behavior.
  260. In most cases, the command line (whether built-in or provided
  261. by the boot loader) should specify the device for the root
  262. file system.
  263. config CMDLINE_OVERRIDE
  264. bool "Built-in command line overrides boot loader arguments"
  265. default n
  266. depends on CMDLINE_BOOL
  267. ---help---
  268. Set this option to 'Y' to have the kernel ignore the boot loader
  269. command line, and use ONLY the built-in command line.
  270. This is used to work around broken boot loaders. This should
  271. be set to 'N' under normal conditions.
  272. config VMALLOC_RESERVE
  273. hex
  274. default 0x1000000
  275. config HARDWALL
  276. bool "Hardwall support to allow access to user dynamic network"
  277. default y
  278. config KERNEL_PL
  279. int "Processor protection level for kernel"
  280. range 1 2
  281. default "1"
  282. ---help---
  283. This setting determines the processor protection level the
  284. kernel will be built to run at. Generally you should use
  285. the default value here.
  286. endmenu # Tilera-specific configuration
  287. menu "Bus options"
  288. config PCI
  289. bool "PCI support"
  290. default y
  291. select PCI_DOMAINS
  292. select GENERIC_PCI_IOMAP
  293. ---help---
  294. Enable PCI root complex support, so PCIe endpoint devices can
  295. be attached to the Tile chip. Many, but not all, PCI devices
  296. are supported under Tilera's root complex driver.
  297. config PCI_DOMAINS
  298. bool
  299. config NO_IOMEM
  300. def_bool !PCI
  301. config NO_IOPORT
  302. def_bool !PCI
  303. source "drivers/pci/Kconfig"
  304. config HOTPLUG
  305. bool "Support for hot-pluggable devices"
  306. ---help---
  307. Say Y here if you want to plug devices into your computer while
  308. the system is running, and be able to use them quickly. In many
  309. cases, the devices can likewise be unplugged at any time too.
  310. One well-known example of this is USB.
  311. source "drivers/pci/hotplug/Kconfig"
  312. endmenu
  313. menu "Executable file formats"
  314. # only elf supported
  315. config KCORE_ELF
  316. def_bool y
  317. depends on PROC_FS
  318. source "fs/Kconfig.binfmt"
  319. endmenu
  320. source "net/Kconfig"
  321. source "drivers/Kconfig"
  322. source "fs/Kconfig"
  323. source "arch/tile/Kconfig.debug"
  324. source "security/Kconfig"
  325. source "crypto/Kconfig"
  326. source "lib/Kconfig"
  327. source "arch/tile/kvm/Kconfig"