Kconfig 39 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108110911101111111211131114111511161117111811191120112111221123112411251126112711281129113011311132113311341135113611371138113911401141114211431144114511461147114811491150115111521153115411551156115711581159116011611162116311641165116611671168116911701171117211731174117511761177117811791180118111821183118411851186118711881189119011911192119311941195119611971198119912001201120212031204120512061207120812091210121112121213
  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see Documentation/kbuild/kconfig-language.txt.
  4. #
  5. mainmenu "Linux Kernel Configuration"
  6. config X86_32
  7. bool
  8. default y
  9. help
  10. This is Linux's home port. Linux was originally native to the Intel
  11. 386, and runs on all the later x86 processors including the Intel
  12. 486, 586, Pentiums, and various instruction-set-compatible chips by
  13. AMD, Cyrix, and others.
  14. config GENERIC_TIME
  15. bool
  16. default y
  17. config LOCKDEP_SUPPORT
  18. bool
  19. default y
  20. config STACKTRACE_SUPPORT
  21. bool
  22. default y
  23. config SEMAPHORE_SLEEPERS
  24. bool
  25. default y
  26. config X86
  27. bool
  28. default y
  29. config MMU
  30. bool
  31. default y
  32. config SBUS
  33. bool
  34. config GENERIC_ISA_DMA
  35. bool
  36. default y
  37. config GENERIC_IOMAP
  38. bool
  39. default y
  40. config GENERIC_HWEIGHT
  41. bool
  42. default y
  43. config ARCH_MAY_HAVE_PC_FDC
  44. bool
  45. default y
  46. config DMI
  47. bool
  48. default y
  49. source "init/Kconfig"
  50. menu "Processor type and features"
  51. config SMP
  52. bool "Symmetric multi-processing support"
  53. ---help---
  54. This enables support for systems with more than one CPU. If you have
  55. a system with only one CPU, like most personal computers, say N. If
  56. you have a system with more than one CPU, say Y.
  57. If you say N here, the kernel will run on single and multiprocessor
  58. machines, but will use only one CPU of a multiprocessor machine. If
  59. you say Y here, the kernel will run on many, but not all,
  60. singleprocessor machines. On a singleprocessor machine, the kernel
  61. will run faster if you say N here.
  62. Note that if you say Y here and choose architecture "586" or
  63. "Pentium" under "Processor family", the kernel will not work on 486
  64. architectures. Similarly, multiprocessor kernels for the "PPro"
  65. architecture may not work on all Pentium based boards.
  66. People using multiprocessor machines who say Y here should also say
  67. Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
  68. Management" code will be disabled if you say Y here.
  69. See also the <file:Documentation/smp.txt>,
  70. <file:Documentation/i386/IO-APIC.txt>,
  71. <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
  72. <http://www.tldp.org/docs.html#howto>.
  73. If you don't know what to do here, say N.
  74. choice
  75. prompt "Subarchitecture Type"
  76. default X86_PC
  77. config X86_PC
  78. bool "PC-compatible"
  79. help
  80. Choose this option if your computer is a standard PC or compatible.
  81. config X86_ELAN
  82. bool "AMD Elan"
  83. help
  84. Select this for an AMD Elan processor.
  85. Do not use this option for K6/Athlon/Opteron processors!
  86. If unsure, choose "PC-compatible" instead.
  87. config X86_VOYAGER
  88. bool "Voyager (NCR)"
  89. help
  90. Voyager is an MCA-based 32-way capable SMP architecture proprietary
  91. to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
  92. *** WARNING ***
  93. If you do not specifically know you have a Voyager based machine,
  94. say N here, otherwise the kernel you build will not be bootable.
  95. config X86_NUMAQ
  96. bool "NUMAQ (IBM/Sequent)"
  97. select SMP
  98. select NUMA
  99. help
  100. This option is used for getting Linux to run on a (IBM/Sequent) NUMA
  101. multiquad box. This changes the way that processors are bootstrapped,
  102. and uses Clustered Logical APIC addressing mode instead of Flat Logical.
  103. You will need a new lynxer.elf file to flash your firmware with - send
  104. email to <Martin.Bligh@us.ibm.com>.
  105. config X86_SUMMIT
  106. bool "Summit/EXA (IBM x440)"
  107. depends on SMP
  108. help
  109. This option is needed for IBM systems that use the Summit/EXA chipset.
  110. In particular, it is needed for the x440.
  111. If you don't have one of these computers, you should say N here.
  112. If you want to build a NUMA kernel, you must select ACPI.
  113. config X86_BIGSMP
  114. bool "Support for other sub-arch SMP systems with more than 8 CPUs"
  115. depends on SMP
  116. help
  117. This option is needed for the systems that have more than 8 CPUs
  118. and if the system is not of any sub-arch type above.
  119. If you don't have such a system, you should say N here.
  120. config X86_VISWS
  121. bool "SGI 320/540 (Visual Workstation)"
  122. help
  123. The SGI Visual Workstation series is an IA32-based workstation
  124. based on SGI systems chips with some legacy PC hardware attached.
  125. Say Y here to create a kernel to run on the SGI 320 or 540.
  126. A kernel compiled for the Visual Workstation will not run on PCs
  127. and vice versa. See <file:Documentation/sgi-visws.txt> for details.
  128. config X86_GENERICARCH
  129. bool "Generic architecture (Summit, bigsmp, ES7000, default)"
  130. help
  131. This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
  132. It is intended for a generic binary kernel.
  133. If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
  134. config X86_ES7000
  135. bool "Support for Unisys ES7000 IA32 series"
  136. depends on SMP
  137. help
  138. Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
  139. supposed to run on an IA32-based Unisys ES7000 system.
  140. Only choose this option if you have such a system, otherwise you
  141. should say N here.
  142. endchoice
  143. config PARAVIRT
  144. bool "Paravirtualization support (EXPERIMENTAL)"
  145. depends on EXPERIMENTAL
  146. help
  147. Paravirtualization is a way of running multiple instances of
  148. Linux on the same machine, under a hypervisor. This option
  149. changes the kernel so it can modify itself when it is run
  150. under a hypervisor, improving performance significantly.
  151. However, when run without a hypervisor the kernel is
  152. theoretically slower. If in doubt, say N.
  153. config ACPI_SRAT
  154. bool
  155. default y
  156. depends on ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
  157. select ACPI_NUMA
  158. config HAVE_ARCH_PARSE_SRAT
  159. bool
  160. default y
  161. depends on ACPI_SRAT
  162. config X86_SUMMIT_NUMA
  163. bool
  164. default y
  165. depends on NUMA && (X86_SUMMIT || X86_GENERICARCH)
  166. config X86_CYCLONE_TIMER
  167. bool
  168. default y
  169. depends on X86_SUMMIT || X86_GENERICARCH
  170. config ES7000_CLUSTERED_APIC
  171. bool
  172. default y
  173. depends on SMP && X86_ES7000 && MPENTIUMIII
  174. source "arch/i386/Kconfig.cpu"
  175. config HPET_TIMER
  176. bool "HPET Timer Support"
  177. help
  178. This enables the use of the HPET for the kernel's internal timer.
  179. HPET is the next generation timer replacing legacy 8254s.
  180. You can safely choose Y here. However, HPET will only be
  181. activated if the platform and the BIOS support this feature.
  182. Otherwise the 8254 will be used for timing services.
  183. Choose N to continue using the legacy 8254 timer.
  184. config HPET_EMULATE_RTC
  185. bool
  186. depends on HPET_TIMER && RTC=y
  187. default y
  188. config NR_CPUS
  189. int "Maximum number of CPUs (2-255)"
  190. range 2 255
  191. depends on SMP
  192. default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
  193. default "8"
  194. help
  195. This allows you to specify the maximum number of CPUs which this
  196. kernel will support. The maximum supported value is 255 and the
  197. minimum value which makes sense is 2.
  198. This is purely to save memory - each supported CPU adds
  199. approximately eight kilobytes to the kernel image.
  200. config SCHED_SMT
  201. bool "SMT (Hyperthreading) scheduler support"
  202. depends on X86_HT
  203. help
  204. SMT scheduler support improves the CPU scheduler's decision making
  205. when dealing with Intel Pentium 4 chips with HyperThreading at a
  206. cost of slightly increased overhead in some places. If unsure say
  207. N here.
  208. config SCHED_MC
  209. bool "Multi-core scheduler support"
  210. depends on X86_HT
  211. default y
  212. help
  213. Multi-core scheduler support improves the CPU scheduler's decision
  214. making when dealing with multi-core CPU chips at a cost of slightly
  215. increased overhead in some places. If unsure say N here.
  216. source "kernel/Kconfig.preempt"
  217. config X86_UP_APIC
  218. bool "Local APIC support on uniprocessors"
  219. depends on !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
  220. help
  221. A local APIC (Advanced Programmable Interrupt Controller) is an
  222. integrated interrupt controller in the CPU. If you have a single-CPU
  223. system which has a processor with a local APIC, you can say Y here to
  224. enable and use it. If you say Y here even though your machine doesn't
  225. have a local APIC, then the kernel will still run with no slowdown at
  226. all. The local APIC supports CPU-generated self-interrupts (timer,
  227. performance counters), and the NMI watchdog which detects hard
  228. lockups.
  229. config X86_UP_IOAPIC
  230. bool "IO-APIC support on uniprocessors"
  231. depends on X86_UP_APIC
  232. help
  233. An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
  234. SMP-capable replacement for PC-style interrupt controllers. Most
  235. SMP systems and many recent uniprocessor systems have one.
  236. If you have a single-CPU system with an IO-APIC, you can say Y here
  237. to use it. If you say Y here even though your machine doesn't have
  238. an IO-APIC, then the kernel will still run with no slowdown at all.
  239. config X86_LOCAL_APIC
  240. bool
  241. depends on X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH
  242. default y
  243. config X86_IO_APIC
  244. bool
  245. depends on X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH
  246. default y
  247. config X86_VISWS_APIC
  248. bool
  249. depends on X86_VISWS
  250. default y
  251. config X86_MCE
  252. bool "Machine Check Exception"
  253. depends on !X86_VOYAGER
  254. ---help---
  255. Machine Check Exception support allows the processor to notify the
  256. kernel if it detects a problem (e.g. overheating, component failure).
  257. The action the kernel takes depends on the severity of the problem,
  258. ranging from a warning message on the console, to halting the machine.
  259. Your processor must be a Pentium or newer to support this - check the
  260. flags in /proc/cpuinfo for mce. Note that some older Pentium systems
  261. have a design flaw which leads to false MCE events - hence MCE is
  262. disabled on all P5 processors, unless explicitly enabled with "mce"
  263. as a boot argument. Similarly, if MCE is built in and creates a
  264. problem on some new non-standard machine, you can boot with "nomce"
  265. to disable it. MCE support simply ignores non-MCE processors like
  266. the 386 and 486, so nearly everyone can say Y here.
  267. config X86_MCE_NONFATAL
  268. tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
  269. depends on X86_MCE
  270. help
  271. Enabling this feature starts a timer that triggers every 5 seconds which
  272. will look at the machine check registers to see if anything happened.
  273. Non-fatal problems automatically get corrected (but still logged).
  274. Disable this if you don't want to see these messages.
  275. Seeing the messages this option prints out may be indicative of dying hardware,
  276. or out-of-spec (ie, overclocked) hardware.
  277. This option only does something on certain CPUs.
  278. (AMD Athlon/Duron and Intel Pentium 4)
  279. config X86_MCE_P4THERMAL
  280. bool "check for P4 thermal throttling interrupt."
  281. depends on X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
  282. help
  283. Enabling this feature will cause a message to be printed when the P4
  284. enters thermal throttling.
  285. config VM86
  286. default y
  287. bool "Enable VM86 support" if EMBEDDED
  288. help
  289. This option is required by programs like DOSEMU to run 16-bit legacy
  290. code on X86 processors. It also may be needed by software like
  291. XFree86 to initialize some video cards via BIOS. Disabling this
  292. option saves about 6k.
  293. config TOSHIBA
  294. tristate "Toshiba Laptop support"
  295. ---help---
  296. This adds a driver to safely access the System Management Mode of
  297. the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
  298. not work on models with a Phoenix BIOS. The System Management Mode
  299. is used to set the BIOS and power saving options on Toshiba portables.
  300. For information on utilities to make use of this driver see the
  301. Toshiba Linux utilities web site at:
  302. <http://www.buzzard.org.uk/toshiba/>.
  303. Say Y if you intend to run this kernel on a Toshiba portable.
  304. Say N otherwise.
  305. config I8K
  306. tristate "Dell laptop support"
  307. ---help---
  308. This adds a driver to safely access the System Management Mode
  309. of the CPU on the Dell Inspiron 8000. The System Management Mode
  310. is used to read cpu temperature and cooling fan status and to
  311. control the fans on the I8K portables.
  312. This driver has been tested only on the Inspiron 8000 but it may
  313. also work with other Dell laptops. You can force loading on other
  314. models by passing the parameter `force=1' to the module. Use at
  315. your own risk.
  316. For information on utilities to make use of this driver see the
  317. I8K Linux utilities web site at:
  318. <http://people.debian.org/~dz/i8k/>
  319. Say Y if you intend to run this kernel on a Dell Inspiron 8000.
  320. Say N otherwise.
  321. config X86_REBOOTFIXUPS
  322. bool "Enable X86 board specific fixups for reboot"
  323. depends on X86
  324. default n
  325. ---help---
  326. This enables chipset and/or board specific fixups to be done
  327. in order to get reboot to work correctly. This is only needed on
  328. some combinations of hardware and BIOS. The symptom, for which
  329. this config is intended, is when reboot ends with a stalled/hung
  330. system.
  331. Currently, the only fixup is for the Geode GX1/CS5530A/TROM2.1.
  332. combination.
  333. Say Y if you want to enable the fixup. Currently, it's safe to
  334. enable this option even if you don't need it.
  335. Say N otherwise.
  336. config MICROCODE
  337. tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
  338. select FW_LOADER
  339. ---help---
  340. If you say Y here and also to "/dev file system support" in the
  341. 'File systems' section, you will be able to update the microcode on
  342. Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
  343. Pentium III, Pentium 4, Xeon etc. You will obviously need the
  344. actual microcode binary data itself which is not shipped with the
  345. Linux kernel.
  346. For latest news and information on obtaining all the required
  347. ingredients for this driver, check:
  348. <http://www.urbanmyth.org/microcode/>.
  349. To compile this driver as a module, choose M here: the
  350. module will be called microcode.
  351. config MICROCODE_OLD_INTERFACE
  352. bool
  353. depends on MICROCODE
  354. default y
  355. config X86_MSR
  356. tristate "/dev/cpu/*/msr - Model-specific register support"
  357. help
  358. This device gives privileged processes access to the x86
  359. Model-Specific Registers (MSRs). It is a character device with
  360. major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
  361. MSR accesses are directed to a specific CPU on multi-processor
  362. systems.
  363. config X86_CPUID
  364. tristate "/dev/cpu/*/cpuid - CPU information support"
  365. help
  366. This device gives processes access to the x86 CPUID instruction to
  367. be executed on a specific processor. It is a character device
  368. with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
  369. /dev/cpu/31/cpuid.
  370. source "drivers/firmware/Kconfig"
  371. choice
  372. prompt "High Memory Support"
  373. default NOHIGHMEM
  374. config NOHIGHMEM
  375. bool "off"
  376. depends on !X86_NUMAQ
  377. ---help---
  378. Linux can use up to 64 Gigabytes of physical memory on x86 systems.
  379. However, the address space of 32-bit x86 processors is only 4
  380. Gigabytes large. That means that, if you have a large amount of
  381. physical memory, not all of it can be "permanently mapped" by the
  382. kernel. The physical memory that's not permanently mapped is called
  383. "high memory".
  384. If you are compiling a kernel which will never run on a machine with
  385. more than 1 Gigabyte total physical RAM, answer "off" here (default
  386. choice and suitable for most users). This will result in a "3GB/1GB"
  387. split: 3GB are mapped so that each process sees a 3GB virtual memory
  388. space and the remaining part of the 4GB virtual memory space is used
  389. by the kernel to permanently map as much physical memory as
  390. possible.
  391. If the machine has between 1 and 4 Gigabytes physical RAM, then
  392. answer "4GB" here.
  393. If more than 4 Gigabytes is used then answer "64GB" here. This
  394. selection turns Intel PAE (Physical Address Extension) mode on.
  395. PAE implements 3-level paging on IA32 processors. PAE is fully
  396. supported by Linux, PAE mode is implemented on all recent Intel
  397. processors (Pentium Pro and better). NOTE: If you say "64GB" here,
  398. then the kernel will not boot on CPUs that don't support PAE!
  399. The actual amount of total physical memory will either be
  400. auto detected or can be forced by using a kernel command line option
  401. such as "mem=256M". (Try "man bootparam" or see the documentation of
  402. your boot loader (lilo or loadlin) about how to pass options to the
  403. kernel at boot time.)
  404. If unsure, say "off".
  405. config HIGHMEM4G
  406. bool "4GB"
  407. depends on !X86_NUMAQ
  408. help
  409. Select this if you have a 32-bit processor and between 1 and 4
  410. gigabytes of physical RAM.
  411. config HIGHMEM64G
  412. bool "64GB"
  413. depends on X86_CMPXCHG64
  414. help
  415. Select this if you have a 32-bit processor and more than 4
  416. gigabytes of physical RAM.
  417. endchoice
  418. choice
  419. depends on EXPERIMENTAL
  420. prompt "Memory split" if EMBEDDED
  421. default VMSPLIT_3G
  422. help
  423. Select the desired split between kernel and user memory.
  424. If the address range available to the kernel is less than the
  425. physical memory installed, the remaining memory will be available
  426. as "high memory". Accessing high memory is a little more costly
  427. than low memory, as it needs to be mapped into the kernel first.
  428. Note that increasing the kernel address space limits the range
  429. available to user programs, making the address space there
  430. tighter. Selecting anything other than the default 3G/1G split
  431. will also likely make your kernel incompatible with binary-only
  432. kernel modules.
  433. If you are not absolutely sure what you are doing, leave this
  434. option alone!
  435. config VMSPLIT_3G
  436. bool "3G/1G user/kernel split"
  437. config VMSPLIT_3G_OPT
  438. depends on !HIGHMEM
  439. bool "3G/1G user/kernel split (for full 1G low memory)"
  440. config VMSPLIT_2G
  441. bool "2G/2G user/kernel split"
  442. config VMSPLIT_1G
  443. bool "1G/3G user/kernel split"
  444. endchoice
  445. config PAGE_OFFSET
  446. hex
  447. default 0xB0000000 if VMSPLIT_3G_OPT
  448. default 0x78000000 if VMSPLIT_2G
  449. default 0x40000000 if VMSPLIT_1G
  450. default 0xC0000000
  451. config HIGHMEM
  452. bool
  453. depends on HIGHMEM64G || HIGHMEM4G
  454. default y
  455. config X86_PAE
  456. bool
  457. depends on HIGHMEM64G
  458. default y
  459. select RESOURCES_64BIT
  460. # Common NUMA Features
  461. config NUMA
  462. bool "Numa Memory Allocation and Scheduler Support"
  463. depends on SMP && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI)
  464. default n if X86_PC
  465. default y if (X86_NUMAQ || X86_SUMMIT)
  466. comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
  467. depends on X86_SUMMIT && (!HIGHMEM64G || !ACPI)
  468. config NODES_SHIFT
  469. int
  470. default "4" if X86_NUMAQ
  471. default "3"
  472. depends on NEED_MULTIPLE_NODES
  473. config HAVE_ARCH_BOOTMEM_NODE
  474. bool
  475. depends on NUMA
  476. default y
  477. config ARCH_HAVE_MEMORY_PRESENT
  478. bool
  479. depends on DISCONTIGMEM
  480. default y
  481. config NEED_NODE_MEMMAP_SIZE
  482. bool
  483. depends on DISCONTIGMEM || SPARSEMEM
  484. default y
  485. config HAVE_ARCH_ALLOC_REMAP
  486. bool
  487. depends on NUMA
  488. default y
  489. config ARCH_FLATMEM_ENABLE
  490. def_bool y
  491. depends on (ARCH_SELECT_MEMORY_MODEL && X86_PC)
  492. config ARCH_DISCONTIGMEM_ENABLE
  493. def_bool y
  494. depends on NUMA
  495. config ARCH_DISCONTIGMEM_DEFAULT
  496. def_bool y
  497. depends on NUMA
  498. config ARCH_SPARSEMEM_ENABLE
  499. def_bool y
  500. depends on (NUMA || (X86_PC && EXPERIMENTAL))
  501. select SPARSEMEM_STATIC
  502. config ARCH_SELECT_MEMORY_MODEL
  503. def_bool y
  504. depends on ARCH_SPARSEMEM_ENABLE
  505. config ARCH_POPULATES_NODE_MAP
  506. def_bool y
  507. source "mm/Kconfig"
  508. config HIGHPTE
  509. bool "Allocate 3rd-level pagetables from highmem"
  510. depends on HIGHMEM4G || HIGHMEM64G
  511. help
  512. The VM uses one page table entry for each page of physical memory.
  513. For systems with a lot of RAM, this can be wasteful of precious
  514. low memory. Setting this option will put user-space page table
  515. entries in high memory.
  516. config MATH_EMULATION
  517. bool "Math emulation"
  518. ---help---
  519. Linux can emulate a math coprocessor (used for floating point
  520. operations) if you don't have one. 486DX and Pentium processors have
  521. a math coprocessor built in, 486SX and 386 do not, unless you added
  522. a 487DX or 387, respectively. (The messages during boot time can
  523. give you some hints here ["man dmesg"].) Everyone needs either a
  524. coprocessor or this emulation.
  525. If you don't have a math coprocessor, you need to say Y here; if you
  526. say Y here even though you have a coprocessor, the coprocessor will
  527. be used nevertheless. (This behavior can be changed with the kernel
  528. command line option "no387", which comes handy if your coprocessor
  529. is broken. Try "man bootparam" or see the documentation of your boot
  530. loader (lilo or loadlin) about how to pass options to the kernel at
  531. boot time.) This means that it is a good idea to say Y here if you
  532. intend to use this kernel on different machines.
  533. More information about the internals of the Linux math coprocessor
  534. emulation can be found in <file:arch/i386/math-emu/README>.
  535. If you are not sure, say Y; apart from resulting in a 66 KB bigger
  536. kernel, it won't hurt.
  537. config MTRR
  538. bool "MTRR (Memory Type Range Register) support"
  539. ---help---
  540. On Intel P6 family processors (Pentium Pro, Pentium II and later)
  541. the Memory Type Range Registers (MTRRs) may be used to control
  542. processor access to memory ranges. This is most useful if you have
  543. a video (VGA) card on a PCI or AGP bus. Enabling write-combining
  544. allows bus write transfers to be combined into a larger transfer
  545. before bursting over the PCI/AGP bus. This can increase performance
  546. of image write operations 2.5 times or more. Saying Y here creates a
  547. /proc/mtrr file which may be used to manipulate your processor's
  548. MTRRs. Typically the X server should use this.
  549. This code has a reasonably generic interface so that similar
  550. control registers on other processors can be easily supported
  551. as well:
  552. The Cyrix 6x86, 6x86MX and M II processors have Address Range
  553. Registers (ARRs) which provide a similar functionality to MTRRs. For
  554. these, the ARRs are used to emulate the MTRRs.
  555. The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
  556. MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
  557. write-combining. All of these processors are supported by this code
  558. and it makes sense to say Y here if you have one of them.
  559. Saying Y here also fixes a problem with buggy SMP BIOSes which only
  560. set the MTRRs for the boot CPU and not for the secondary CPUs. This
  561. can lead to all sorts of problems, so it's good to say Y here.
  562. You can safely say Y even if your machine doesn't have MTRRs, you'll
  563. just add about 9 KB to your kernel.
  564. See <file:Documentation/mtrr.txt> for more information.
  565. config EFI
  566. bool "Boot from EFI support"
  567. depends on ACPI
  568. default n
  569. ---help---
  570. This enables the kernel to boot on EFI platforms using
  571. system configuration information passed to it from the firmware.
  572. This also enables the kernel to use any EFI runtime services that are
  573. available (such as the EFI variable services).
  574. This option is only useful on systems that have EFI firmware
  575. and will result in a kernel image that is ~8k larger. In addition,
  576. you must use the latest ELILO loader available at
  577. <http://elilo.sourceforge.net> in order to take advantage of
  578. kernel initialization using EFI information (neither GRUB nor LILO know
  579. anything about EFI). However, even with this option, the resultant
  580. kernel should continue to boot on existing non-EFI platforms.
  581. config IRQBALANCE
  582. bool "Enable kernel irq balancing"
  583. depends on SMP && X86_IO_APIC
  584. default y
  585. help
  586. The default yes will allow the kernel to do irq load balancing.
  587. Saying no will keep the kernel from doing irq load balancing.
  588. # turning this on wastes a bunch of space.
  589. # Summit needs it only when NUMA is on
  590. config BOOT_IOREMAP
  591. bool
  592. depends on (((X86_SUMMIT || X86_GENERICARCH) && NUMA) || (X86 && EFI))
  593. default y
  594. config SECCOMP
  595. bool "Enable seccomp to safely compute untrusted bytecode"
  596. depends on PROC_FS
  597. default y
  598. help
  599. This kernel feature is useful for number crunching applications
  600. that may need to compute untrusted bytecode during their
  601. execution. By using pipes or other transports made available to
  602. the process as file descriptors supporting the read/write
  603. syscalls, it's possible to isolate those applications in
  604. their own address space using seccomp. Once seccomp is
  605. enabled via /proc/<pid>/seccomp, it cannot be disabled
  606. and the task is only allowed to execute a few safe syscalls
  607. defined by each seccomp mode.
  608. If unsure, say Y. Only embedded should say N here.
  609. source kernel/Kconfig.hz
  610. config KEXEC
  611. bool "kexec system call"
  612. help
  613. kexec is a system call that implements the ability to shutdown your
  614. current kernel, and to start another kernel. It is like a reboot
  615. but it is independent of the system firmware. And like a reboot
  616. you can start any kernel with it, not just Linux.
  617. The name comes from the similarity to the exec system call.
  618. It is an ongoing process to be certain the hardware in a machine
  619. is properly shutdown, so do not be surprised if this code does not
  620. initially work for you. It may help to enable device hotplugging
  621. support. As of this writing the exact hardware interface is
  622. strongly in flux, so no good recommendation can be made.
  623. config CRASH_DUMP
  624. bool "kernel crash dumps (EXPERIMENTAL)"
  625. depends on EXPERIMENTAL
  626. depends on HIGHMEM
  627. help
  628. Generate crash dump after being started by kexec.
  629. This should be normally only set in special crash dump kernels
  630. which are loaded in the main kernel with kexec-tools into
  631. a specially reserved region and then later executed after
  632. a crash by kdump/kexec. The crash dump kernel must be compiled
  633. to a memory address not used by the main kernel or BIOS using
  634. PHYSICAL_START.
  635. For more details see Documentation/kdump/kdump.txt
  636. config RELOCATABLE
  637. bool "Build a relocatable kernel(EXPERIMENTAL)"
  638. depends on EXPERIMENTAL
  639. help
  640. This build a kernel image that retains relocation information
  641. so it can be loaded someplace besides the default 1MB.
  642. The relocations tend to the kernel binary about 10% larger,
  643. but are discarded at runtime.
  644. One use is for the kexec on panic case where the recovery kernel
  645. must live at a different physical address than the primary
  646. kernel.
  647. config PHYSICAL_ALIGN
  648. hex "Alignment value to which kernel should be aligned"
  649. default "0x100000"
  650. range 0x2000 0x400000
  651. help
  652. This value puts the alignment restrictions on physical address
  653. where kernel is loaded and run from. Kernel is compiled for an
  654. address which meets above alignment restriction.
  655. If bootloader loads the kernel at a non-aligned address and
  656. CONFIG_RELOCATABLE is set, kernel will move itself to nearest
  657. address aligned to above value and run from there.
  658. If bootloader loads the kernel at a non-aligned address and
  659. CONFIG_RELOCATABLE is not set, kernel will ignore the run time
  660. load address and decompress itself to the address it has been
  661. compiled for and run from there. The address for which kernel is
  662. compiled already meets above alignment restrictions. Hence the
  663. end result is that kernel runs from a physical address meeting
  664. above alignment restrictions.
  665. Don't change this unless you know what you are doing.
  666. config HOTPLUG_CPU
  667. bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
  668. depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
  669. ---help---
  670. Say Y here to experiment with turning CPUs off and on, and to
  671. enable suspend on SMP systems. CPUs can be controlled through
  672. /sys/devices/system/cpu.
  673. config COMPAT_VDSO
  674. bool "Compat VDSO support"
  675. default y
  676. depends on !PARAVIRT
  677. help
  678. Map the VDSO to the predictable old-style address too.
  679. ---help---
  680. Say N here if you are running a sufficiently recent glibc
  681. version (2.3.3 or later), to remove the high-mapped
  682. VDSO mapping and to exclusively use the randomized VDSO.
  683. If unsure, say Y.
  684. endmenu
  685. config ARCH_ENABLE_MEMORY_HOTPLUG
  686. def_bool y
  687. depends on HIGHMEM
  688. menu "Power management options (ACPI, APM)"
  689. depends on !X86_VOYAGER
  690. source kernel/power/Kconfig
  691. source "drivers/acpi/Kconfig"
  692. menu "APM (Advanced Power Management) BIOS Support"
  693. depends on PM && !X86_VISWS
  694. config APM
  695. tristate "APM (Advanced Power Management) BIOS support"
  696. depends on PM
  697. ---help---
  698. APM is a BIOS specification for saving power using several different
  699. techniques. This is mostly useful for battery powered laptops with
  700. APM compliant BIOSes. If you say Y here, the system time will be
  701. reset after a RESUME operation, the /proc/apm device will provide
  702. battery status information, and user-space programs will receive
  703. notification of APM "events" (e.g. battery status change).
  704. If you select "Y" here, you can disable actual use of the APM
  705. BIOS by passing the "apm=off" option to the kernel at boot time.
  706. Note that the APM support is almost completely disabled for
  707. machines with more than one CPU.
  708. In order to use APM, you will need supporting software. For location
  709. and more information, read <file:Documentation/pm.txt> and the
  710. Battery Powered Linux mini-HOWTO, available from
  711. <http://www.tldp.org/docs.html#howto>.
  712. This driver does not spin down disk drives (see the hdparm(8)
  713. manpage ("man 8 hdparm") for that), and it doesn't turn off
  714. VESA-compliant "green" monitors.
  715. This driver does not support the TI 4000M TravelMate and the ACER
  716. 486/DX4/75 because they don't have compliant BIOSes. Many "green"
  717. desktop machines also don't have compliant BIOSes, and this driver
  718. may cause those machines to panic during the boot phase.
  719. Generally, if you don't have a battery in your machine, there isn't
  720. much point in using this driver and you should say N. If you get
  721. random kernel OOPSes or reboots that don't seem to be related to
  722. anything, try disabling/enabling this option (or disabling/enabling
  723. APM in your BIOS).
  724. Some other things you should try when experiencing seemingly random,
  725. "weird" problems:
  726. 1) make sure that you have enough swap space and that it is
  727. enabled.
  728. 2) pass the "no-hlt" option to the kernel
  729. 3) switch on floating point emulation in the kernel and pass
  730. the "no387" option to the kernel
  731. 4) pass the "floppy=nodma" option to the kernel
  732. 5) pass the "mem=4M" option to the kernel (thereby disabling
  733. all but the first 4 MB of RAM)
  734. 6) make sure that the CPU is not over clocked.
  735. 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
  736. 8) disable the cache from your BIOS settings
  737. 9) install a fan for the video card or exchange video RAM
  738. 10) install a better fan for the CPU
  739. 11) exchange RAM chips
  740. 12) exchange the motherboard.
  741. To compile this driver as a module, choose M here: the
  742. module will be called apm.
  743. config APM_IGNORE_USER_SUSPEND
  744. bool "Ignore USER SUSPEND"
  745. depends on APM
  746. help
  747. This option will ignore USER SUSPEND requests. On machines with a
  748. compliant APM BIOS, you want to say N. However, on the NEC Versa M
  749. series notebooks, it is necessary to say Y because of a BIOS bug.
  750. config APM_DO_ENABLE
  751. bool "Enable PM at boot time"
  752. depends on APM
  753. ---help---
  754. Enable APM features at boot time. From page 36 of the APM BIOS
  755. specification: "When disabled, the APM BIOS does not automatically
  756. power manage devices, enter the Standby State, enter the Suspend
  757. State, or take power saving steps in response to CPU Idle calls."
  758. This driver will make CPU Idle calls when Linux is idle (unless this
  759. feature is turned off -- see "Do CPU IDLE calls", below). This
  760. should always save battery power, but more complicated APM features
  761. will be dependent on your BIOS implementation. You may need to turn
  762. this option off if your computer hangs at boot time when using APM
  763. support, or if it beeps continuously instead of suspending. Turn
  764. this off if you have a NEC UltraLite Versa 33/C or a Toshiba
  765. T400CDT. This is off by default since most machines do fine without
  766. this feature.
  767. config APM_CPU_IDLE
  768. bool "Make CPU Idle calls when idle"
  769. depends on APM
  770. help
  771. Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
  772. On some machines, this can activate improved power savings, such as
  773. a slowed CPU clock rate, when the machine is idle. These idle calls
  774. are made after the idle loop has run for some length of time (e.g.,
  775. 333 mS). On some machines, this will cause a hang at boot time or
  776. whenever the CPU becomes idle. (On machines with more than one CPU,
  777. this option does nothing.)
  778. config APM_DISPLAY_BLANK
  779. bool "Enable console blanking using APM"
  780. depends on APM
  781. help
  782. Enable console blanking using the APM. Some laptops can use this to
  783. turn off the LCD backlight when the screen blanker of the Linux
  784. virtual console blanks the screen. Note that this is only used by
  785. the virtual console screen blanker, and won't turn off the backlight
  786. when using the X Window system. This also doesn't have anything to
  787. do with your VESA-compliant power-saving monitor. Further, this
  788. option doesn't work for all laptops -- it might not turn off your
  789. backlight at all, or it might print a lot of errors to the console,
  790. especially if you are using gpm.
  791. config APM_RTC_IS_GMT
  792. bool "RTC stores time in GMT"
  793. depends on APM
  794. help
  795. Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
  796. stores the time in GMT (Greenwich Mean Time). Say N if your RTC
  797. stores localtime.
  798. It is in fact recommended to store GMT in your RTC, because then you
  799. don't have to worry about daylight savings time changes. The only
  800. reason not to use GMT in your RTC is if you also run a broken OS
  801. that doesn't understand GMT.
  802. config APM_ALLOW_INTS
  803. bool "Allow interrupts during APM BIOS calls"
  804. depends on APM
  805. help
  806. Normally we disable external interrupts while we are making calls to
  807. the APM BIOS as a measure to lessen the effects of a badly behaving
  808. BIOS implementation. The BIOS should reenable interrupts if it
  809. needs to. Unfortunately, some BIOSes do not -- especially those in
  810. many of the newer IBM Thinkpads. If you experience hangs when you
  811. suspend, try setting this to Y. Otherwise, say N.
  812. config APM_REAL_MODE_POWER_OFF
  813. bool "Use real mode APM BIOS call to power off"
  814. depends on APM
  815. help
  816. Use real mode APM BIOS calls to switch off the computer. This is
  817. a work-around for a number of buggy BIOSes. Switch this option on if
  818. your computer crashes instead of powering off properly.
  819. endmenu
  820. source "arch/i386/kernel/cpu/cpufreq/Kconfig"
  821. endmenu
  822. menu "Bus options (PCI, PCMCIA, EISA, MCA, ISA)"
  823. config PCI
  824. bool "PCI support" if !X86_VISWS
  825. depends on !X86_VOYAGER
  826. default y if X86_VISWS
  827. help
  828. Find out whether you have a PCI motherboard. PCI is the name of a
  829. bus system, i.e. the way the CPU talks to the other stuff inside
  830. your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  831. VESA. If you have PCI, say Y, otherwise N.
  832. The PCI-HOWTO, available from
  833. <http://www.tldp.org/docs.html#howto>, contains valuable
  834. information about which PCI hardware does work under Linux and which
  835. doesn't.
  836. choice
  837. prompt "PCI access mode"
  838. depends on PCI && !X86_VISWS
  839. default PCI_GOANY
  840. ---help---
  841. On PCI systems, the BIOS can be used to detect the PCI devices and
  842. determine their configuration. However, some old PCI motherboards
  843. have BIOS bugs and may crash if this is done. Also, some embedded
  844. PCI-based systems don't have any BIOS at all. Linux can also try to
  845. detect the PCI hardware directly without using the BIOS.
  846. With this option, you can specify how Linux should detect the
  847. PCI devices. If you choose "BIOS", the BIOS will be used,
  848. if you choose "Direct", the BIOS won't be used, and if you
  849. choose "MMConfig", then PCI Express MMCONFIG will be used.
  850. If you choose "Any", the kernel will try MMCONFIG, then the
  851. direct access method and falls back to the BIOS if that doesn't
  852. work. If unsure, go with the default, which is "Any".
  853. config PCI_GOBIOS
  854. bool "BIOS"
  855. config PCI_GOMMCONFIG
  856. bool "MMConfig"
  857. config PCI_GODIRECT
  858. bool "Direct"
  859. config PCI_GOANY
  860. bool "Any"
  861. endchoice
  862. config PCI_BIOS
  863. bool
  864. depends on !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
  865. default y
  866. config PCI_DIRECT
  867. bool
  868. depends on PCI && ((PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
  869. default y
  870. config PCI_MMCONFIG
  871. bool
  872. depends on PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
  873. default y
  874. source "drivers/pci/pcie/Kconfig"
  875. source "drivers/pci/Kconfig"
  876. config ISA_DMA_API
  877. bool
  878. default y
  879. config ISA
  880. bool "ISA support"
  881. depends on !(X86_VOYAGER || X86_VISWS)
  882. help
  883. Find out whether you have ISA slots on your motherboard. ISA is the
  884. name of a bus system, i.e. the way the CPU talks to the other stuff
  885. inside your box. Other bus systems are PCI, EISA, MicroChannel
  886. (MCA) or VESA. ISA is an older system, now being displaced by PCI;
  887. newer boards don't support it. If you have ISA, say Y, otherwise N.
  888. config EISA
  889. bool "EISA support"
  890. depends on ISA
  891. ---help---
  892. The Extended Industry Standard Architecture (EISA) bus was
  893. developed as an open alternative to the IBM MicroChannel bus.
  894. The EISA bus provided some of the features of the IBM MicroChannel
  895. bus while maintaining backward compatibility with cards made for
  896. the older ISA bus. The EISA bus saw limited use between 1988 and
  897. 1995 when it was made obsolete by the PCI bus.
  898. Say Y here if you are building a kernel for an EISA-based machine.
  899. Otherwise, say N.
  900. source "drivers/eisa/Kconfig"
  901. config MCA
  902. bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
  903. default y if X86_VOYAGER
  904. help
  905. MicroChannel Architecture is found in some IBM PS/2 machines and
  906. laptops. It is a bus system similar to PCI or ISA. See
  907. <file:Documentation/mca.txt> (and especially the web page given
  908. there) before attempting to build an MCA bus kernel.
  909. source "drivers/mca/Kconfig"
  910. config SCx200
  911. tristate "NatSemi SCx200 support"
  912. depends on !X86_VOYAGER
  913. help
  914. This provides basic support for National Semiconductor's
  915. (now AMD's) Geode processors. The driver probes for the
  916. PCI-IDs of several on-chip devices, so its a good dependency
  917. for other scx200_* drivers.
  918. If compiled as a module, the driver is named scx200.
  919. config SCx200HR_TIMER
  920. tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
  921. depends on SCx200 && GENERIC_TIME
  922. default y
  923. help
  924. This driver provides a clocksource built upon the on-chip
  925. 27MHz high-resolution timer. Its also a workaround for
  926. NSC Geode SC-1100's buggy TSC, which loses time when the
  927. processor goes idle (as is done by the scheduler). The
  928. other workaround is idle=poll boot option.
  929. config K8_NB
  930. def_bool y
  931. depends on AGP_AMD64
  932. source "drivers/pcmcia/Kconfig"
  933. source "drivers/pci/hotplug/Kconfig"
  934. endmenu
  935. menu "Executable file formats"
  936. source "fs/Kconfig.binfmt"
  937. endmenu
  938. source "net/Kconfig"
  939. source "drivers/Kconfig"
  940. source "fs/Kconfig"
  941. menu "Instrumentation Support"
  942. depends on EXPERIMENTAL
  943. source "arch/i386/oprofile/Kconfig"
  944. config KPROBES
  945. bool "Kprobes (EXPERIMENTAL)"
  946. depends on KALLSYMS && EXPERIMENTAL && MODULES
  947. help
  948. Kprobes allows you to trap at almost any kernel address and
  949. execute a callback function. register_kprobe() establishes
  950. a probepoint and specifies the callback. Kprobes is useful
  951. for kernel debugging, non-intrusive instrumentation and testing.
  952. If in doubt, say "N".
  953. endmenu
  954. source "arch/i386/Kconfig.debug"
  955. source "security/Kconfig"
  956. source "crypto/Kconfig"
  957. source "lib/Kconfig"
  958. #
  959. # Use the generic interrupt handling code in kernel/irq/:
  960. #
  961. config GENERIC_HARDIRQS
  962. bool
  963. default y
  964. config GENERIC_IRQ_PROBE
  965. bool
  966. default y
  967. config GENERIC_PENDING_IRQ
  968. bool
  969. depends on GENERIC_HARDIRQS && SMP
  970. default y
  971. config X86_SMP
  972. bool
  973. depends on SMP && !X86_VOYAGER
  974. default y
  975. config X86_HT
  976. bool
  977. depends on SMP && !(X86_VISWS || X86_VOYAGER)
  978. default y
  979. config X86_BIOS_REBOOT
  980. bool
  981. depends on !(X86_VISWS || X86_VOYAGER)
  982. default y
  983. config X86_TRAMPOLINE
  984. bool
  985. depends on X86_SMP || (X86_VOYAGER && SMP)
  986. default y
  987. config KTIME_SCALAR
  988. bool
  989. default y