aboutsummaryrefslogtreecommitdiffstats
path: root/arch/x86_64/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'arch/x86_64/Kconfig')
-rw-r--r--arch/x86_64/Kconfig844
1 files changed, 0 insertions, 844 deletions
diff --git a/arch/x86_64/Kconfig b/arch/x86_64/Kconfig
deleted file mode 100644
index e2542e5b536c..000000000000
--- a/arch/x86_64/Kconfig
+++ /dev/null
@@ -1,844 +0,0 @@
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
27config GENERIC_TIME
28 bool
29 default y
30
31config GENERIC_TIME_VSYSCALL
32 bool
33 default y
34
35config GENERIC_CMOS_UPDATE
36 bool
37 default y
38
39config CLOCKSOURCE_WATCHDOG
40 bool
41 default y
42
43config GENERIC_CLOCKEVENTS
44 bool
45 default y
46
47config GENERIC_CLOCKEVENTS_BROADCAST
48 bool
49 default y
50
51config ZONE_DMA32
52 bool
53 default y
54
55config LOCKDEP_SUPPORT
56 bool
57 default y
58
59config STACKTRACE_SUPPORT
60 bool
61 default y
62
63config SEMAPHORE_SLEEPERS
64 bool
65 default y
66
67config MMU
68 bool
69 default y
70
71config ZONE_DMA
72 bool
73 default y
74
75config ISA
76 bool
77
78config SBUS
79 bool
80
81config RWSEM_GENERIC_SPINLOCK
82 bool
83 default y
84
85config RWSEM_XCHGADD_ALGORITHM
86 bool
87
88config GENERIC_HWEIGHT
89 bool
90 default y
91
92config GENERIC_CALIBRATE_DELAY
93 bool
94 default y
95
96config X86_CMPXCHG
97 bool
98 default y
99
100config EARLY_PRINTK
101 bool
102 default y
103
104config GENERIC_ISA_DMA
105 bool
106 default y
107
108config GENERIC_IOMAP
109 bool
110 default y
111
112config ARCH_MAY_HAVE_PC_FDC
113 bool
114 default y
115
116config ARCH_POPULATES_NODE_MAP
117 def_bool y
118
119config DMI
120 bool
121 default y
122
123config AUDIT_ARCH
124 bool
125 default y
126
127config GENERIC_BUG
128 bool
129 default y
130 depends on BUG
131
132config ARCH_HAS_ILOG2_U32
133 bool
134 default n
135
136config ARCH_HAS_ILOG2_U64
137 bool
138 default n
139
140source "init/Kconfig"
141
142
143menu "Processor type and features"
144
145source "kernel/time/Kconfig"
146
147choice
148 prompt "Subarchitecture Type"
149 default X86_PC
150
151config X86_PC
152 bool "PC-compatible"
153 help
154 Choose this option if your computer is a standard PC or compatible.
155
156config X86_VSMP
157 bool "Support for ScaleMP vSMP"
158 depends on PCI
159 help
160 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
161 supposed to run on these EM64T-based machines. Only choose this option
162 if you have one of these machines.
163
164endchoice
165
166choice
167 prompt "Processor family"
168 default GENERIC_CPU
169
170config MK8
171 bool "AMD-Opteron/Athlon64"
172 help
173 Optimize for AMD Opteron/Athlon64/Hammer/K8 CPUs.
174
175config MPSC
176 bool "Intel P4 / older Netburst based Xeon"
177 help
178 Optimize for Intel Pentium 4, Pentium D and older Nocona/Dempsey
179 Xeon CPUs with Intel 64bit which is compatible with x86-64.
180 Note that the latest Xeons (Xeon 51xx and 53xx) are not based on the
181 Netburst core and shouldn't use this option. You can distinguish them
182 using the cpu family field
183 in /proc/cpuinfo. Family 15 is an older Xeon, Family 6 a newer one.
184
185config MCORE2
186 bool "Intel Core2 / newer Xeon"
187 help
188 Optimize for Intel Core2 and newer Xeons (51xx)
189 You can distinguish the newer Xeons from the older ones using
190 the cpu family field in /proc/cpuinfo. 15 is an older Xeon
191 (use CONFIG_MPSC then), 6 is a newer one.
192
193config GENERIC_CPU
194 bool "Generic-x86-64"
195 help
196 Generic x86-64 CPU.
197 Run equally well on all x86-64 CPUs.
198
199endchoice
200
201#
202# Define implied options from the CPU selection here
203#
204config X86_L1_CACHE_BYTES
205 int
206 default "128" if GENERIC_CPU || MPSC
207 default "64" if MK8 || MCORE2
208
209config X86_L1_CACHE_SHIFT
210 int
211 default "7" if GENERIC_CPU || MPSC
212 default "6" if MK8 || MCORE2
213
214config X86_INTERNODE_CACHE_BYTES
215 int
216 default "4096" if X86_VSMP
217 default X86_L1_CACHE_BYTES if !X86_VSMP
218
219config X86_TSC
220 bool
221 default y
222
223config X86_GOOD_APIC
224 bool
225 default y
226
227config MICROCODE
228 tristate "/dev/cpu/microcode - Intel CPU microcode support"
229 select FW_LOADER
230 ---help---
231 If you say Y here the 'File systems' section, you will be
232 able to update the microcode on Intel processors. You will
233 obviously need the actual microcode binary data itself which is
234 not shipped with the Linux kernel.
235
236 For latest news and information on obtaining all the required
237 ingredients for this driver, check:
238 <http://www.urbanmyth.org/microcode/>.
239
240 To compile this driver as a module, choose M here: the
241 module will be called microcode.
242 If you use modprobe or kmod you may also want to add the line
243 'alias char-major-10-184 microcode' to your /etc/modules.conf file.
244
245config MICROCODE_OLD_INTERFACE
246 bool
247 depends on MICROCODE
248 default y
249
250config X86_MSR
251 tristate "/dev/cpu/*/msr - Model-specific register support"
252 help
253 This device gives privileged processes access to the x86
254 Model-Specific Registers (MSRs). It is a character device with
255 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
256 MSR accesses are directed to a specific CPU on multi-processor
257 systems.
258
259config X86_CPUID
260 tristate "/dev/cpu/*/cpuid - CPU information support"
261 help
262 This device gives processes access to the x86 CPUID instruction to
263 be executed on a specific processor. It is a character device
264 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
265 /dev/cpu/31/cpuid.
266
267config X86_HT
268 bool
269 depends on SMP && !MK8
270 default y
271
272config MATH_EMULATION
273 bool
274
275config MCA
276 bool
277
278config EISA
279 bool
280
281config X86_IO_APIC
282 bool
283 default y
284
285config X86_LOCAL_APIC
286 bool
287 default y
288
289config MTRR
290 bool "MTRR (Memory Type Range Register) support"
291 ---help---
292 On Intel P6 family processors (Pentium Pro, Pentium II and later)
293 the Memory Type Range Registers (MTRRs) may be used to control
294 processor access to memory ranges. This is most useful if you have
295 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
296 allows bus write transfers to be combined into a larger transfer
297 before bursting over the PCI/AGP bus. This can increase performance
298 of image write operations 2.5 times or more. Saying Y here creates a
299 /proc/mtrr file which may be used to manipulate your processor's
300 MTRRs. Typically the X server should use this.
301
302 This code has a reasonably generic interface so that similar
303 control registers on other processors can be easily supported
304 as well.
305
306 Saying Y here also fixes a problem with buggy SMP BIOSes which only
307 set the MTRRs for the boot CPU and not for the secondary CPUs. This
308 can lead to all sorts of problems, so it's good to say Y here.
309
310 Just say Y here, all x86-64 machines support MTRRs.
311
312 See <file:Documentation/mtrr.txt> for more information.
313
314config SMP
315 bool "Symmetric multi-processing support"
316 ---help---
317 This enables support for systems with more than one CPU. If you have
318 a system with only one CPU, like most personal computers, say N. If
319 you have a system with more than one CPU, say Y.
320
321 If you say N here, the kernel will run on single and multiprocessor
322 machines, but will use only one CPU of a multiprocessor machine. If
323 you say Y here, the kernel will run on many, but not all,
324 singleprocessor machines. On a singleprocessor machine, the kernel
325 will run faster if you say N here.
326
327 If you don't know what to do here, say N.
328
329config SCHED_SMT
330 bool "SMT (Hyperthreading) scheduler support"
331 depends on SMP
332 default n
333 help
334 SMT scheduler support improves the CPU scheduler's decision making
335 when dealing with Intel Pentium 4 chips with HyperThreading at a
336 cost of slightly increased overhead in some places. If unsure say
337 N here.
338
339config SCHED_MC
340 bool "Multi-core scheduler support"
341 depends on SMP
342 default y
343 help
344 Multi-core scheduler support improves the CPU scheduler's decision
345 making when dealing with multi-core CPU chips at a cost of slightly
346 increased overhead in some places. If unsure say N here.
347
348source "kernel/Kconfig.preempt"
349
350config NUMA
351 bool "Non Uniform Memory Access (NUMA) Support"
352 depends on SMP
353 help
354 Enable NUMA (Non Uniform Memory Access) support. The kernel
355 will try to allocate memory used by a CPU on the local memory
356 controller of the CPU and add some more NUMA awareness to the kernel.
357 This code is recommended on all multiprocessor Opteron systems.
358 If the system is EM64T, you should say N unless your system is EM64T
359 NUMA.
360
361config K8_NUMA
362 bool "Old style AMD Opteron NUMA detection"
363 depends on NUMA && PCI
364 default y
365 help
366 Enable K8 NUMA node topology detection. You should say Y here if
367 you have a multi processor AMD K8 system. This uses an old
368 method to read the NUMA configuration directly from the builtin
369 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
370 instead, which also takes priority if both are compiled in.
371
372config NODES_SHIFT
373 int
374 default "6"
375 depends on NEED_MULTIPLE_NODES
376
377# Dummy CONFIG option to select ACPI_NUMA from drivers/acpi/Kconfig.
378
379config X86_64_ACPI_NUMA
380 bool "ACPI NUMA detection"
381 depends on NUMA
382 select ACPI
383 select PCI
384 select ACPI_NUMA
385 default y
386 help
387 Enable ACPI SRAT based node topology detection.
388
389config NUMA_EMU
390 bool "NUMA emulation"
391 depends on NUMA
392 help
393 Enable NUMA emulation. A flat machine will be split
394 into virtual nodes when booted with "numa=fake=N", where N is the
395 number of nodes. This is only useful for debugging.
396
397config ARCH_DISCONTIGMEM_ENABLE
398 bool
399 depends on NUMA
400 default y
401
402config ARCH_DISCONTIGMEM_DEFAULT
403 def_bool y
404 depends on NUMA
405
406config ARCH_SPARSEMEM_ENABLE
407 def_bool y
408 depends on (NUMA || EXPERIMENTAL)
409 select SPARSEMEM_VMEMMAP_ENABLE
410
411config ARCH_MEMORY_PROBE
412 def_bool y
413 depends on MEMORY_HOTPLUG
414
415config ARCH_FLATMEM_ENABLE
416 def_bool y
417 depends on !NUMA
418
419source "mm/Kconfig"
420
421config MEMORY_HOTPLUG_RESERVE
422 def_bool y
423 depends on (MEMORY_HOTPLUG && DISCONTIGMEM)
424
425config HAVE_ARCH_EARLY_PFN_TO_NID
426 def_bool y
427 depends on NUMA
428
429config OUT_OF_LINE_PFN_TO_PAGE
430 def_bool y
431 depends on DISCONTIGMEM
432
433config NR_CPUS
434 int "Maximum number of CPUs (2-255)"
435 range 2 255
436 depends on SMP
437 default "8"
438 help
439 This allows you to specify the maximum number of CPUs which this
440 kernel will support. Current maximum is 255 CPUs due to
441 APIC addressing limits. Less depending on the hardware.
442
443 This is purely to save memory - each supported CPU requires
444 memory in the static kernel configuration.
445
446config PHYSICAL_ALIGN
447 hex
448 default "0x200000"
449
450config HOTPLUG_CPU
451 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
452 depends on SMP && HOTPLUG && EXPERIMENTAL
453 help
454 Say Y here to experiment with turning CPUs off and on. CPUs
455 can be controlled through /sys/devices/system/cpu/cpu#.
456 This is also required for suspend/hibernation on SMP systems.
457
458 Say N if you want to disable CPU hotplug and don't need to
459 suspend.
460
461config ARCH_ENABLE_MEMORY_HOTPLUG
462 def_bool y
463
464config HPET_TIMER
465 bool
466 default y
467 help
468 Use the IA-PC HPET (High Precision Event Timer) to manage
469 time in preference to the PIT and RTC, if a HPET is
470 present. The HPET provides a stable time base on SMP
471 systems, unlike the TSC, but it is more expensive to access,
472 as it is off-chip. You can find the HPET spec at
473 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
474
475config HPET_EMULATE_RTC
476 bool
477 depends on HPET_TIMER && RTC=y
478 default y
479
480# Mark as embedded because too many people got it wrong.
481# The code disables itself when not needed.
482config IOMMU
483 bool "IOMMU support" if EMBEDDED
484 default y
485 select SWIOTLB
486 select AGP
487 depends on PCI
488 help
489 Support for full DMA access of devices with 32bit memory access only
490 on systems with more than 3GB. This is usually needed for USB,
491 sound, many IDE/SATA chipsets and some other devices.
492 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
493 based hardware IOMMU and a software bounce buffer based IOMMU used
494 on Intel systems and as fallback.
495 The code is only active when needed (enough memory and limited
496 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
497 too.
498
499config CALGARY_IOMMU
500 bool "IBM Calgary IOMMU support"
501 select SWIOTLB
502 depends on PCI && EXPERIMENTAL
503 help
504 Support for hardware IOMMUs in IBM's xSeries x366 and x460
505 systems. Needed to run systems with more than 3GB of memory
506 properly with 32-bit PCI devices that do not support DAC
507 (Double Address Cycle). Calgary also supports bus level
508 isolation, where all DMAs pass through the IOMMU. This
509 prevents them from going anywhere except their intended
510 destination. This catches hard-to-find kernel bugs and
511 mis-behaving drivers and devices that do not use the DMA-API
512 properly to set up their DMA buffers. The IOMMU can be
513 turned off at boot time with the iommu=off parameter.
514 Normally the kernel will make the right choice by itself.
515 If unsure, say Y.
516
517config CALGARY_IOMMU_ENABLED_BY_DEFAULT
518 bool "Should Calgary be enabled by default?"
519 default y
520 depends on CALGARY_IOMMU
521 help
522 Should Calgary be enabled by default? if you choose 'y', Calgary
523 will be used (if it exists). If you choose 'n', Calgary will not be
524 used even if it exists. If you choose 'n' and would like to use
525 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
526 If unsure, say Y.
527
528# need this always selected by IOMMU for the VIA workaround
529config SWIOTLB
530 bool
531 help
532 Support for software bounce buffers used on x86-64 systems
533 which don't have a hardware IOMMU (e.g. the current generation
534 of Intel's x86-64 CPUs). Using this PCI devices which can only
535 access 32-bits of memory can be used on systems with more than
536 3 GB of memory. If unsure, say Y.
537
538config X86_MCE
539 bool "Machine check support" if EMBEDDED
540 default y
541 help
542 Include a machine check error handler to report hardware errors.
543 This version will require the mcelog utility to decode some
544 machine check error logs. See
545 ftp://ftp.x86-64.org/pub/linux/tools/mcelog
546
547config X86_MCE_INTEL
548 bool "Intel MCE features"
549 depends on X86_MCE && X86_LOCAL_APIC
550 default y
551 help
552 Additional support for intel specific MCE features such as
553 the thermal monitor.
554
555config X86_MCE_AMD
556 bool "AMD MCE features"
557 depends on X86_MCE && X86_LOCAL_APIC
558 default y
559 help
560 Additional support for AMD specific MCE features such as
561 the DRAM Error Threshold.
562
563config KEXEC
564 bool "kexec system call"
565 help
566 kexec is a system call that implements the ability to shutdown your
567 current kernel, and to start another kernel. It is like a reboot
568 but it is independent of the system firmware. And like a reboot
569 you can start any kernel with it, not just Linux.
570
571 The name comes from the similarity to the exec system call.
572
573 It is an ongoing process to be certain the hardware in a machine
574 is properly shutdown, so do not be surprised if this code does not
575 initially work for you. It may help to enable device hotplugging
576 support. As of this writing the exact hardware interface is
577 strongly in flux, so no good recommendation can be made.
578
579config CRASH_DUMP
580 bool "kernel crash dumps (EXPERIMENTAL)"
581 depends on EXPERIMENTAL
582 help
583 Generate crash dump after being started by kexec.
584 This should be normally only set in special crash dump kernels
585 which are loaded in the main kernel with kexec-tools into
586 a specially reserved region and then later executed after
587 a crash by kdump/kexec. The crash dump kernel must be compiled
588 to a memory address not used by the main kernel or BIOS using
589 PHYSICAL_START, or it must be built as a relocatable image
590 (CONFIG_RELOCATABLE=y).
591 For more details see Documentation/kdump/kdump.txt
592
593config RELOCATABLE
594 bool "Build a relocatable kernel (EXPERIMENTAL)"
595 depends on EXPERIMENTAL
596 help
597 Builds a relocatable kernel. This enables loading and running
598 a kernel binary from a different physical address than it has
599 been compiled for.
600
601 One use is for the kexec on panic case where the recovery kernel
602 must live at a different physical address than the primary
603 kernel.
604
605 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
606 it has been loaded at and the compile time physical address
607 (CONFIG_PHYSICAL_START) is ignored.
608
609config PHYSICAL_START
610 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
611 default "0x200000"
612 help
613 This gives the physical address where the kernel is loaded. It
614 should be aligned to 2MB boundary.
615
616 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
617 bzImage will decompress itself to above physical address and
618 run from there. Otherwise, bzImage will run from the address where
619 it has been loaded by the boot loader and will ignore above physical
620 address.
621
622 In normal kdump cases one does not have to set/change this option
623 as now bzImage can be compiled as a completely relocatable image
624 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
625 address. This option is mainly useful for the folks who don't want
626 to use a bzImage for capturing the crash dump and want to use a
627 vmlinux instead.
628
629 So if you are using bzImage for capturing the crash dump, leave
630 the value here unchanged to 0x200000 and set CONFIG_RELOCATABLE=y.
631 Otherwise if you plan to use vmlinux for capturing the crash dump
632 change this value to start of the reserved region (Typically 16MB
633 0x1000000). In other words, it can be set based on the "X" value as
634 specified in the "crashkernel=YM@XM" command line boot parameter
635 passed to the panic-ed kernel. Typically this parameter is set as
636 crashkernel=64M@16M. Please take a look at
637 Documentation/kdump/kdump.txt for more details about crash dumps.
638
639 Usage of bzImage for capturing the crash dump is advantageous as
640 one does not have to build two kernels. Same kernel can be used
641 as production kernel and capture kernel.
642
643 Don't change this unless you know what you are doing.
644
645config SECCOMP
646 bool "Enable seccomp to safely compute untrusted bytecode"
647 depends on PROC_FS
648 default y
649 help
650 This kernel feature is useful for number crunching applications
651 that may need to compute untrusted bytecode during their
652 execution. By using pipes or other transports made available to
653 the process as file descriptors supporting the read/write
654 syscalls, it's possible to isolate those applications in
655 their own address space using seccomp. Once seccomp is
656 enabled via /proc/<pid>/seccomp, it cannot be disabled
657 and the task is only allowed to execute a few safe syscalls
658 defined by each seccomp mode.
659
660 If unsure, say Y. Only embedded should say N here.
661
662config CC_STACKPROTECTOR
663 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
664 depends on EXPERIMENTAL
665 help
666 This option turns on the -fstack-protector GCC feature. This
667 feature puts, at the beginning of critical functions, a canary
668 value on the stack just before the return address, and validates
669 the value just before actually returning. Stack based buffer
670 overflows (that need to overwrite this return address) now also
671 overwrite the canary, which gets detected and the attack is then
672 neutralized via a kernel panic.
673
674 This feature requires gcc version 4.2 or above, or a distribution
675 gcc with the feature backported. Older versions are automatically
676 detected and for those versions, this configuration option is ignored.
677
678config CC_STACKPROTECTOR_ALL
679 bool "Use stack-protector for all functions"
680 depends on CC_STACKPROTECTOR
681 help
682 Normally, GCC only inserts the canary value protection for
683 functions that use large-ish on-stack buffers. By enabling
684 this option, GCC will be asked to do this for ALL functions.
685
686source kernel/Kconfig.hz
687
688config K8_NB
689 def_bool y
690 depends on AGP_AMD64 || IOMMU || (PCI && NUMA)
691
692endmenu
693
694#
695# Use the generic interrupt handling code in kernel/irq/:
696#
697config GENERIC_HARDIRQS
698 bool
699 default y
700
701config GENERIC_IRQ_PROBE
702 bool
703 default y
704
705# we have no ISA slots, but we do have ISA-style DMA.
706config ISA_DMA_API
707 bool
708 default y
709
710config GENERIC_PENDING_IRQ
711 bool
712 depends on GENERIC_HARDIRQS && SMP
713 default y
714
715menu "Power management options"
716
717source kernel/power/Kconfig
718
719config ARCH_HIBERNATION_HEADER
720 bool
721 depends on HIBERNATION
722 default y
723
724source "drivers/acpi/Kconfig"
725
726source "arch/x86/kernel/cpu/cpufreq/Kconfig_64"
727
728source "drivers/cpuidle/Kconfig"
729
730endmenu
731
732menu "Bus options (PCI etc.)"
733
734config PCI
735 bool "PCI support"
736 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
737
738# x86-64 doesn't support PCI BIOS access from long mode so always go direct.
739config PCI_DIRECT
740 bool
741 depends on PCI
742 default y
743
744config PCI_MMCONFIG
745 bool "Support mmconfig PCI config space access"
746 depends on PCI && ACPI
747
748config PCI_DOMAINS
749 bool
750 depends on PCI
751 default y
752
753config DMAR
754 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
755 depends on PCI_MSI && ACPI && EXPERIMENTAL
756 default y
757 help
758 DMA remapping (DMAR) devices support enables independent address
759 translations for Direct Memory Access (DMA) from devices.
760 These DMA remapping devices are reported via ACPI tables
761 and include PCI device scope covered by these DMA
762 remapping devices.
763
764config DMAR_GFX_WA
765 bool "Support for Graphics workaround"
766 depends on DMAR
767 default y
768 help
769 Current Graphics drivers tend to use physical address
770 for DMA and avoid using DMA APIs. Setting this config
771 option permits the IOMMU driver to set a unity map for
772 all the OS-visible memory. Hence the driver can continue
773 to use physical addresses for DMA.
774
775config DMAR_FLOPPY_WA
776 bool
777 depends on DMAR
778 default y
779 help
780 Floppy disk drivers are know to bypass DMA API calls
781 thereby failing to work when IOMMU is enabled. This
782 workaround will setup a 1:1 mapping for the first
783 16M to make floppy (an ISA device) work.
784
785source "drivers/pci/pcie/Kconfig"
786
787source "drivers/pci/Kconfig"
788
789source "drivers/pcmcia/Kconfig"
790
791source "drivers/pci/hotplug/Kconfig"
792
793endmenu
794
795
796menu "Executable file formats / Emulations"
797
798source "fs/Kconfig.binfmt"
799
800config IA32_EMULATION
801 bool "IA32 Emulation"
802 help
803 Include code to run 32-bit programs under a 64-bit kernel. You should
804 likely turn this on, unless you're 100% sure that you don't have any
805 32-bit programs left.
806
807config IA32_AOUT
808 tristate "IA32 a.out support"
809 depends on IA32_EMULATION
810 help
811 Support old a.out binaries in the 32bit emulation.
812
813config COMPAT
814 bool
815 depends on IA32_EMULATION
816 default y
817
818config COMPAT_FOR_U64_ALIGNMENT
819 def_bool COMPAT
820
821config SYSVIPC_COMPAT
822 bool
823 depends on COMPAT && SYSVIPC
824 default y
825
826endmenu
827
828source "net/Kconfig"
829
830source drivers/Kconfig
831
832source "drivers/firmware/Kconfig"
833
834source fs/Kconfig
835
836source "kernel/Kconfig.instrumentation"
837
838source "arch/x86/Kconfig.debug"
839
840source "security/Kconfig"
841
842source "crypto/Kconfig"
843
844source "lib/Kconfig"
generated by cgit v1.2.2 (git 2.25.0) at 2024-11-22 00:13:44 -0500