[PATCH] swsusp: struct snapshot_handle cleanup
[GitHub/mt8127/android_kernel_alcatel_ttab.git] / arch / x86_64 / Kconfig
CommitLineData
1da177e4
LT
1#
2# For a description of the syntax of this configuration file,
3# see Documentation/kbuild/kconfig-language.txt.
4#
5# Note: ISA is disabled and will hopefully never be enabled.
6# If you managed to buy an ISA x86-64 box you'll have to fix all the
7# ISA drivers you need yourself.
8#
9
10mainmenu "Linux Kernel Configuration"
11
12config X86_64
13 bool
14 default y
15 help
16 Port to the x86-64 architecture. x86-64 is a 64-bit extension to the
17 classical 32-bit x86 architecture. For details see
18 <http://www.x86-64.org/>.
19
20config 64BIT
21 def_bool y
22
23config X86
24 bool
25 default y
26
fb0e7942
CL
27config ZONE_DMA32
28 bool
29 default y
30
1e950527
IM
31config LOCKDEP_SUPPORT
32 bool
33 default y
34
21b32bbf
IM
35config STACKTRACE_SUPPORT
36 bool
37 default y
38
52fdd089
BL
39config SEMAPHORE_SLEEPERS
40 bool
41 default y
42
1da177e4
LT
43config MMU
44 bool
45 default y
46
47config ISA
48 bool
49
50config SBUS
51 bool
52
53config RWSEM_GENERIC_SPINLOCK
54 bool
55 default y
56
57config RWSEM_XCHGADD_ALGORITHM
58 bool
59
f33e2fba
AM
60config GENERIC_HWEIGHT
61 bool
62 default y
63
1da177e4
LT
64config GENERIC_CALIBRATE_DELAY
65 bool
66 default y
67
68config X86_CMPXCHG
69 bool
70 default y
71
72config EARLY_PRINTK
73 bool
74 default y
75
76config GENERIC_ISA_DMA
77 bool
78 default y
79
80config GENERIC_IOMAP
81 bool
82 default y
83
a08b6b79
AV
84config ARCH_MAY_HAVE_PC_FDC
85 bool
86 default y
87
e9928674
AK
88config DMI
89 bool
90 default y
91
e65e1fc2
AV
92config AUDIT_ARCH
93 bool
94 default y
95
1da177e4
LT
96source "init/Kconfig"
97
98
99menu "Processor type and features"
100
79f12614
RT
101choice
102 prompt "Subarchitecture Type"
103 default X86_PC
104
105config X86_PC
106 bool "PC-compatible"
107 help
108 Choose this option if your computer is a standard PC or compatible.
109
110config X86_VSMP
111 bool "Support for ScaleMP vSMP"
112 help
113 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
114 supposed to run on these EM64T-based machines. Only choose this option
115 if you have one of these machines.
116
117endchoice
118
1da177e4
LT
119choice
120 prompt "Processor family"
121 default MK8
122
123config MK8
124 bool "AMD-Opteron/Athlon64"
125 help
126 Optimize for AMD Opteron/Athlon64/Hammer/K8 CPUs.
127
128config MPSC
129 bool "Intel EM64T"
130 help
131 Optimize for Intel Pentium 4 and Xeon CPUs with Intel
132 Extended Memory 64 Technology(EM64T). For details see
133 <http://www.intel.com/technology/64bitextensions/>.
134
135config GENERIC_CPU
136 bool "Generic-x86-64"
137 help
138 Generic x86-64 CPU.
139
140endchoice
141
142#
143# Define implied options from the CPU selection here
144#
145config X86_L1_CACHE_BYTES
146 int
147 default "128" if GENERIC_CPU || MPSC
148 default "64" if MK8
149
150config X86_L1_CACHE_SHIFT
151 int
152 default "7" if GENERIC_CPU || MPSC
153 default "6" if MK8
154
e405d067
RT
155config X86_INTERNODE_CACHE_BYTES
156 int
157 default "4096" if X86_VSMP
158 default X86_L1_CACHE_BYTES if !X86_VSMP
159
1da177e4
LT
160config X86_TSC
161 bool
162 default y
163
164config X86_GOOD_APIC
165 bool
166 default y
167
168config MICROCODE
169 tristate "/dev/cpu/microcode - Intel CPU microcode support"
170 ---help---
171 If you say Y here the 'File systems' section, you will be
172 able to update the microcode on Intel processors. You will
173 obviously need the actual microcode binary data itself which is
174 not shipped with the Linux kernel.
175
176 For latest news and information on obtaining all the required
177 ingredients for this driver, check:
178 <http://www.urbanmyth.org/microcode/>.
179
180 To compile this driver as a module, choose M here: the
181 module will be called microcode.
182 If you use modprobe or kmod you may also want to add the line
183 'alias char-major-10-184 microcode' to your /etc/modules.conf file.
184
185config X86_MSR
186 tristate "/dev/cpu/*/msr - Model-specific register support"
187 help
188 This device gives privileged processes access to the x86
189 Model-Specific Registers (MSRs). It is a character device with
190 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
191 MSR accesses are directed to a specific CPU on multi-processor
192 systems.
193
194config X86_CPUID
195 tristate "/dev/cpu/*/cpuid - CPU information support"
196 help
197 This device gives processes access to the x86 CPUID instruction to
198 be executed on a specific processor. It is a character device
199 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
200 /dev/cpu/31/cpuid.
201
1da177e4
LT
202config X86_HT
203 bool
204 depends on SMP && !MK8
205 default y
206
207config MATH_EMULATION
208 bool
209
210config MCA
211 bool
212
213config EISA
214 bool
215
216config X86_IO_APIC
217 bool
218 default y
219
220config X86_LOCAL_APIC
221 bool
222 default y
223
224config MTRR
225 bool "MTRR (Memory Type Range Register) support"
226 ---help---
227 On Intel P6 family processors (Pentium Pro, Pentium II and later)
228 the Memory Type Range Registers (MTRRs) may be used to control
229 processor access to memory ranges. This is most useful if you have
230 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
231 allows bus write transfers to be combined into a larger transfer
232 before bursting over the PCI/AGP bus. This can increase performance
233 of image write operations 2.5 times or more. Saying Y here creates a
234 /proc/mtrr file which may be used to manipulate your processor's
235 MTRRs. Typically the X server should use this.
236
237 This code has a reasonably generic interface so that similar
238 control registers on other processors can be easily supported
239 as well.
240
241 Saying Y here also fixes a problem with buggy SMP BIOSes which only
242 set the MTRRs for the boot CPU and not for the secondary CPUs. This
243 can lead to all sorts of problems, so it's good to say Y here.
244
245 Just say Y here, all x86-64 machines support MTRRs.
246
247 See <file:Documentation/mtrr.txt> for more information.
248
249config SMP
250 bool "Symmetric multi-processing support"
251 ---help---
252 This enables support for systems with more than one CPU. If you have
253 a system with only one CPU, like most personal computers, say N. If
254 you have a system with more than one CPU, say Y.
255
256 If you say N here, the kernel will run on single and multiprocessor
257 machines, but will use only one CPU of a multiprocessor machine. If
258 you say Y here, the kernel will run on many, but not all,
259 singleprocessor machines. On a singleprocessor machine, the kernel
260 will run faster if you say N here.
261
262 If you don't know what to do here, say N.
263
1da177e4
LT
264config SCHED_SMT
265 bool "SMT (Hyperthreading) scheduler support"
266 depends on SMP
267 default n
268 help
269 SMT scheduler support improves the CPU scheduler's decision making
270 when dealing with Intel Pentium 4 chips with HyperThreading at a
271 cost of slightly increased overhead in some places. If unsure say
272 N here.
273
1e9f28fa
SS
274config SCHED_MC
275 bool "Multi-core scheduler support"
276 depends on SMP
277 default y
278 help
279 Multi-core scheduler support improves the CPU scheduler's decision
280 making when dealing with multi-core CPU chips at a cost of slightly
281 increased overhead in some places. If unsure say N here.
282
cc19ca86
IM
283source "kernel/Kconfig.preempt"
284
b0bd35e6
RT
285config NUMA
286 bool "Non Uniform Memory Access (NUMA) Support"
1da177e4
LT
287 depends on SMP
288 help
b0bd35e6
RT
289 Enable NUMA (Non Uniform Memory Access) support. The kernel
290 will try to allocate memory used by a CPU on the local memory
291 controller of the CPU and add some more NUMA awareness to the kernel.
292 This code is recommended on all multiprocessor Opteron systems.
293 If the system is EM64T, you should say N unless your system is EM64T
294 NUMA.
295
296config K8_NUMA
297 bool "Old style AMD Opteron NUMA detection"
298 depends on NUMA
299 default y
300 help
301 Enable K8 NUMA node topology detection. You should say Y here if
302 you have a multi processor AMD K8 system. This uses an old
303 method to read the NUMA configurtion directly from the builtin
304 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
305 instead, which also takes priority if both are compiled in.
306
c80d79d7
YG
307config NODES_SHIFT
308 int
309 default "6"
310 depends on NEED_MULTIPLE_NODES
311
b0bd35e6
RT
312# Dummy CONFIG option to select ACPI_NUMA from drivers/acpi/Kconfig.
313
314config X86_64_ACPI_NUMA
315 bool "ACPI NUMA detection"
316 depends on NUMA
317 select ACPI
1300124f 318 select PCI
b0bd35e6
RT
319 select ACPI_NUMA
320 default y
321 help
322 Enable ACPI SRAT based node topology detection.
1da177e4
LT
323
324config NUMA_EMU
b0bd35e6
RT
325 bool "NUMA emulation"
326 depends on NUMA
1da177e4
LT
327 help
328 Enable NUMA emulation. A flat machine will be split
329 into virtual nodes when booted with "numa=fake=N", where N is the
330 number of nodes. This is only useful for debugging.
331
3f22ab27 332config ARCH_DISCONTIGMEM_ENABLE
1da177e4
LT
333 bool
334 depends on NUMA
335 default y
336
1da177e4 337
1035faf1
MT
338config ARCH_DISCONTIGMEM_ENABLE
339 def_bool y
340 depends on NUMA
341
342config ARCH_DISCONTIGMEM_DEFAULT
343 def_bool y
344 depends on NUMA
345
346config ARCH_SPARSEMEM_ENABLE
347 def_bool y
44df75e6
MT
348 depends on (NUMA || EXPERIMENTAL)
349
350config ARCH_MEMORY_PROBE
351 def_bool y
352 depends on MEMORY_HOTPLUG
1035faf1
MT
353
354config ARCH_FLATMEM_ENABLE
355 def_bool y
356 depends on !NUMA
357
3f22ab27
DH
358source "mm/Kconfig"
359
1035faf1
MT
360config HAVE_ARCH_EARLY_PFN_TO_NID
361 def_bool y
44df75e6 362 depends on NUMA
1035faf1 363
dc8ecb43
KH
364config OUT_OF_LINE_PFN_TO_PAGE
365 def_bool y
366 depends on DISCONTIGMEM
367
1da177e4
LT
368config NR_CPUS
369 int "Maximum number of CPUs (2-256)"
01d4bed4 370 range 2 255
1da177e4
LT
371 depends on SMP
372 default "8"
373 help
374 This allows you to specify the maximum number of CPUs which this
375 kernel will support. Current maximum is 256 CPUs due to
376 APIC addressing limits. Less depending on the hardware.
377
378 This is purely to save memory - each supported CPU requires
379 memory in the static kernel configuration.
380
76e4f660
AR
381config HOTPLUG_CPU
382 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
383 depends on SMP && HOTPLUG && EXPERIMENTAL
384 help
385 Say Y here to experiment with turning CPUs off and on. CPUs
386 can be controlled through /sys/devices/system/cpu/cpu#.
387 Say N if you want to disable CPU hotplug.
388
cc57637b
YG
389config ARCH_ENABLE_MEMORY_HOTPLUG
390 def_bool y
76e4f660 391
1da177e4
LT
392config HPET_TIMER
393 bool
394 default y
395 help
396 Use the IA-PC HPET (High Precision Event Timer) to manage
397 time in preference to the PIT and RTC, if a HPET is
398 present. The HPET provides a stable time base on SMP
399 systems, unlike the TSC, but it is more expensive to access,
400 as it is off-chip. You can find the HPET spec at
89d7cbf7 401 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
1da177e4
LT
402
403config HPET_EMULATE_RTC
404 bool "Provide RTC interrupt"
405 depends on HPET_TIMER && RTC=y
406
a813ce43
AK
407# Mark as embedded because too many people got it wrong.
408# The code disables itself when not needed.
409config IOMMU
410 bool "IOMMU support" if EMBEDDED
a54649b8 411 default y
17a941d8 412 select SWIOTLB
dcc1a66a 413 select AGP
1da177e4
LT
414 depends on PCI
415 help
a813ce43
AK
416 Support for full DMA access of devices with 32bit memory access only
417 on systems with more than 3GB. This is usually needed for USB,
418 sound, many IDE/SATA chipsets and some other devices.
419 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
420 based IOMMU and a software bounce buffer based IOMMU used on Intel
421 systems and as fallback.
422 The code is only active when needed (enough memory and limited
423 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
424 too.
425
e465058d
JM
426config CALGARY_IOMMU
427 bool "IBM Calgary IOMMU support"
428 default y
429 select SWIOTLB
430 depends on PCI && EXPERIMENTAL
431 help
432 Support for hardware IOMMUs in IBM's xSeries x366 and x460
433 systems. Needed to run systems with more than 3GB of memory
434 properly with 32-bit PCI devices that do not support DAC
435 (Double Address Cycle). Calgary also supports bus level
436 isolation, where all DMAs pass through the IOMMU. This
437 prevents them from going anywhere except their intended
438 destination. This catches hard-to-find kernel bugs and
439 mis-behaving drivers and devices that do not use the DMA-API
440 properly to set up their DMA buffers. The IOMMU can be
441 turned off at boot time with the iommu=off parameter.
442 Normally the kernel will make the right choice by itself.
443 If unsure, say Y.
444
a813ce43 445# need this always selected by IOMMU for the VIA workaround
1da177e4 446config SWIOTLB
1da177e4 447 bool
1da177e4
LT
448
449config X86_MCE
450 bool "Machine check support" if EMBEDDED
451 default y
452 help
453 Include a machine check error handler to report hardware errors.
454 This version will require the mcelog utility to decode some
455 machine check error logs. See
456 ftp://ftp.x86-64.org/pub/linux/tools/mcelog
457
458config X86_MCE_INTEL
459 bool "Intel MCE features"
460 depends on X86_MCE && X86_LOCAL_APIC
461 default y
462 help
463 Additional support for intel specific MCE features such as
464 the thermal monitor.
465
89b831ef
JS
466config X86_MCE_AMD
467 bool "AMD MCE features"
468 depends on X86_MCE && X86_LOCAL_APIC
469 default y
470 help
471 Additional support for AMD specific MCE features such as
472 the DRAM Error Threshold.
473
5234f5eb
EB
474config KEXEC
475 bool "kexec system call (EXPERIMENTAL)"
476 depends on EXPERIMENTAL
477 help
478 kexec is a system call that implements the ability to shutdown your
479 current kernel, and to start another kernel. It is like a reboot
1f1332f7 480 but it is independent of the system firmware. And like a reboot
5234f5eb
EB
481 you can start any kernel with it, not just Linux.
482
1f1332f7 483 The name comes from the similarity to the exec system call.
5234f5eb
EB
484
485 It is an ongoing process to be certain the hardware in a machine
486 is properly shutdown, so do not be surprised if this code does not
487 initially work for you. It may help to enable device hotplugging
488 support. As of this writing the exact hardware interface is
489 strongly in flux, so no good recommendation can be made.
490
ec9ce0db
VG
491config CRASH_DUMP
492 bool "kernel crash dumps (EXPERIMENTAL)"
ec9ce0db
VG
493 depends on EXPERIMENTAL
494 help
495 Generate crash dump after being started by kexec.
496
05970d47
MS
497config PHYSICAL_START
498 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
499 default "0x1000000" if CRASH_DUMP
04103609 500 default "0x200000"
05970d47
MS
501 help
502 This gives the physical address where the kernel is loaded. Normally
04103609 503 for regular kernels this value is 0x200000 (2MB). But in the case
05970d47
MS
504 of kexec on panic the fail safe kernel needs to run at a different
505 address than the panic-ed kernel. This option is used to set the load
506 address for kernels used to capture crash dump on being kexec'ed
507 after panic. The default value for crash dump kernels is
508 0x1000000 (16MB). This can also be set based on the "X" value as
509 specified in the "crashkernel=YM@XM" command line boot parameter
510 passed to the panic-ed kernel. Typically this parameter is set as
511 crashkernel=64M@16M. Please take a look at
512 Documentation/kdump/kdump.txt for more details about crash dumps.
513
514 Don't change this unless you know what you are doing.
515
1da177e4
LT
516config SECCOMP
517 bool "Enable seccomp to safely compute untrusted bytecode"
518 depends on PROC_FS
519 default y
520 help
521 This kernel feature is useful for number crunching applications
522 that may need to compute untrusted bytecode during their
523 execution. By using pipes or other transports made available to
524 the process as file descriptors supporting the read/write
525 syscalls, it's possible to isolate those applications in
526 their own address space using seccomp. Once seccomp is
527 enabled via /proc/<pid>/seccomp, it cannot be disabled
528 and the task is only allowed to execute a few safe syscalls
529 defined by each seccomp mode.
530
531 If unsure, say Y. Only embedded should say N here.
532
59121003
CL
533source kernel/Kconfig.hz
534
4bdc3b7f
AV
535config REORDER
536 bool "Function reordering"
537 default n
538 help
539 This option enables the toolchain to reorder functions for a more
540 optimal TLB usage. If you have pretty much any version of binutils,
541 this can increase your kernel build time by roughly one minute.
542
a32073bf
AK
543config K8_NB
544 def_bool y
a813ce43 545 depends on AGP_AMD64 || IOMMU || (PCI && NUMA)
a32073bf 546
1da177e4
LT
547endmenu
548
549#
550# Use the generic interrupt handling code in kernel/irq/:
551#
552config GENERIC_HARDIRQS
553 bool
554 default y
555
556config GENERIC_IRQ_PROBE
557 bool
558 default y
559
5cae841b
AV
560# we have no ISA slots, but we do have ISA-style DMA.
561config ISA_DMA_API
562 bool
563 default y
564
54d5d424
AR
565config GENERIC_PENDING_IRQ
566 bool
567 depends on GENERIC_HARDIRQS && SMP
568 default y
569
1da177e4
LT
570menu "Power management options"
571
572source kernel/power/Kconfig
573
574source "drivers/acpi/Kconfig"
575
576source "arch/x86_64/kernel/cpufreq/Kconfig"
577
578endmenu
579
580menu "Bus options (PCI etc.)"
581
582config PCI
583 bool "PCI support"
584
585# x86-64 doesn't support PCI BIOS access from long mode so always go direct.
586config PCI_DIRECT
587 bool
588 depends on PCI
589 default y
590
591config PCI_MMCONFIG
592 bool "Support mmconfig PCI config space access"
8aadff7d 593 depends on PCI && ACPI
1da177e4 594
1da177e4
LT
595source "drivers/pci/pcie/Kconfig"
596
597source "drivers/pci/Kconfig"
598
599source "drivers/pcmcia/Kconfig"
600
601source "drivers/pci/hotplug/Kconfig"
602
603endmenu
604
605
606menu "Executable file formats / Emulations"
607
608source "fs/Kconfig.binfmt"
609
610config IA32_EMULATION
611 bool "IA32 Emulation"
612 help
613 Include code to run 32-bit programs under a 64-bit kernel. You should likely
614 turn this on, unless you're 100% sure that you don't have any 32-bit programs
615 left.
616
617config IA32_AOUT
ea0be473 618 tristate "IA32 a.out support"
1da177e4
LT
619 depends on IA32_EMULATION
620 help
621 Support old a.out binaries in the 32bit emulation.
622
623config COMPAT
624 bool
625 depends on IA32_EMULATION
626 default y
627
628config SYSVIPC_COMPAT
629 bool
630 depends on COMPAT && SYSVIPC
631 default y
632
1da177e4
LT
633endmenu
634
d5950b43
SR
635source "net/Kconfig"
636
1da177e4
LT
637source drivers/Kconfig
638
639source "drivers/firmware/Kconfig"
640
641source fs/Kconfig
642
cd6b0762
PP
643menu "Instrumentation Support"
644 depends on EXPERIMENTAL
645
1da177e4
LT
646source "arch/x86_64/oprofile/Kconfig"
647
cd6b0762
PP
648config KPROBES
649 bool "Kprobes (EXPERIMENTAL)"
add2b6fd 650 depends on EXPERIMENTAL && MODULES
cd6b0762
PP
651 help
652 Kprobes allows you to trap at almost any kernel address and
653 execute a callback function. register_kprobe() establishes
654 a probepoint and specifies the callback. Kprobes is useful
655 for kernel debugging, non-intrusive instrumentation and testing.
656 If in doubt, say "N".
657endmenu
658
1da177e4
LT
659source "arch/x86_64/Kconfig.debug"
660
661source "security/Kconfig"
662
663source "crypto/Kconfig"
664
665source "lib/Kconfig"