Kconfig 41 KB

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