Lines Matching +full:cpu +full:- +full:to +full:- +full:pci
1 # SPDX-License-Identifier: GPL-2.0
4 bool "64-bit kernel" if "$(ARCH)" = "x86"
7 Say yes to build a 64-bit kernel - formerly known as x86_64
8 Say no to build a 32-bit kernel - formerly known as i386
13 # Options that are inherently 32-bit kernel only:
26 # Options that are inherently 64-bit kernel only:
48 in order to test the non static function tracing in the
50 only need to keep it around for x86_64. No need to keep it
56 # ported to 32-bit as well. )
158 # Word-size accesses may read uninitialized data past the trailing \0
312 select PCI_DOMAINS if PCI
313 select PCI_LOCKLESS_CONFIG if PCI
342 default "elf32-i386" if X86_32
343 default "elf64-x86-64" if X86_64
433 bool "Symmetric multi-processing support"
435 This enables support for systems with more than one CPU. If you have
436 a system with only one CPU, say N. If you have a system with more
437 than one CPU, say Y.
439 If you say N here, the kernel will run on uni- and multiprocessor
440 machines, but will use only one CPU of a multiprocessor machine. If
451 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
454 See also <file:Documentation/arch/x86/i386/IO-APIC.rst>,
455 <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO available at
458 If you don't know what to do here, say N.
466 (the local APIC) is present in the CPU. It allows faster access to
472 emulated in virtual machines, even when the host CPU does not support
473 it. Support in the CPU can be checked by executing
480 to older APIC implementations.
488 Enable this to get AMD Secure AVIC support on guests that have this feature.
491 APIC accesses and support for managing guest owned APIC state for SEV-SNP
495 If you don't know what to do here, say N.
498 bool "Enable MSI and MSI-x delivery by posted interrupts"
501 This enables MSIs that are under interrupt remapping to be delivered as
502 posted interrupts to the host kernel. Interrupt throughput can
503 potentially be improved by coalescing CPU notifications during high
506 If you don't know what to do here, say N.
517 bool "x86 CPU resource control support"
524 Enable x86 CPU resource control support.
527 usage by the CPU.
543 When enabled, try to use Flexible Return and Event Delivery
549 bool "Support for extended (non-PC) x86 platforms"
556 If you enable this option then you'll be able to select support
557 for the following non-PC x86 platforms, depending on the value of
560 32-bit platforms (CONFIG_64BIT=n):
564 RDC R-321x SoC
566 64-bit platforms (CONFIG_64BIT=y):
573 If you have one of these systems, or if you want to build a
574 generic distribution kernel, say Y here - otherwise say N.
587 Adds support for Numascale NumaChip large-SMP systems. Needed to
595 depends on X86_64 && PCI
600 supposed to run on these EM64T-based machines. Only choose this option
611 depends on PCI
613 This option is needed in order to support SGI Ultraviolet systems.
620 depends on PCI
627 Select to build a kernel capable of supporting 64-bit Intel MID
629 the PCI legacy interfaces.
636 If you are building for a PC class system or non-MID tablet
655 depends on PCI
674 depends on PCI
681 Select to include support for Quark X1000 SoC.
686 bool "RDC R-321x SoC"
692 This option is needed for RDC R-321x system-on-chip, also known
693 as R-8610-(G).
698 depends on X86 && ACPI && PCI
703 Select to build support for Intel Low Power Subsystem such as
714 Select to interpret AMD specific ACPI device to platform device
716 I2C and UART depend on COMMON_CLK to set clock. GPIO driver is
721 depends on PCI
725 MSR's for some register accesses, mostly but not limited to thermal
726 and power. Drivers may query the availability of this device to
727 determine if they need the sideband in order to work on these
729 This list is not meant to be exclusive.
730 - BayTrail
731 - Braswell
732 - Quark
740 Select this option to expose the IOSF sideband access registers (MCR,
741 MDR, MCRX) through debugfs to write and read register information from
745 device they want to access.
753 # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:
754 # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:
763 to shut themselves down properly. A special I/O sequence is
764 needed to do so, which is what this module does at
773 prompt "Single-depth WCHAN output"
777 is disabled then wchan values will recurse back to the
786 Say Y here to enable options for running Linux under various hyper-
809 bool "paravirt-ops debugging"
812 Enable to debug paravirt_ops internals. Specifically, BUG if
819 Paravirtualized spinlocks allow a pvops backend to replace the
820 spinlock implementation with something virtualization-friendly
821 (for example, block the virtual CPU rather than spinning).
826 If you are unsure how to answer this question, answer Y.
863 Select this option to enable fine granularity task steal time
865 the current vCPU is discounted from the vCPU power. To account for
874 bool "Jailhouse non-root cell support"
875 depends on X86_64 && PCI
878 This option allows to run Linux as guest in a Jailhouse non-root
879 cell. You can leave this option disabled if you only want to start
887 This option allows to run Linux as guest in the ACRN hypervisor. ACRN is
888 a flexible, lightweight reference open-source hypervisor, built with
889 real-time and safety-criticality in mind. It is built for embedded
890 IOT with small footprint and real-time features. More details can be
897 This option allows to run Linux to recognise when it is running as a
898 guest in the Bhyve hypervisor, and to support more than 255 vCPUs when
903 bool "Intel TDX (Trust Domain Extensions) - Guest Support"
917 memory contents and CPU state. TDX guests are protected from
922 source "arch/x86/Kconfig.cpu"
928 Use the IA-PC HPET (High Precision Event Timer) to manage
929 time in preference to the PIT and RTC, if a HPET is
933 systems, unlike the TSC, but it is more expensive to access,
934 as it is off-chip. The interface used is documented
941 Choose N to continue using the legacy 8254 timer.
954 Enabled scanning of DMI to identify machine quirks. Say Y
963 depends on X86_64 && PCI && AMD_NB
968 The GART supports full DMA access for devices with 32-bit access
977 32-bit limited device.
998 # The main config value is NR_CPUS, which defaults to NR_CPUS_DEFAULT,
1002 # The ranges are different on 32-bit and 64-bit kernels, depending on
1046 This allows you to specify the maximum number of CPUs which this
1051 This is purely to save memory: each supported CPU adds about 8KB
1052 to the kernel image.
1055 bool "CPU core priorities scheduler support"
1064 certain cores to reach higher turbo frequencies (when running
1068 the TBM3 (aka ITMT) priority order of the CPU cores and adjusts the
1069 scheduler's CPU selection logic accordingly, so that higher
1086 integrated interrupt controller in the CPU. If you have a single-CPU
1087 system which has a processor with a local APIC, you can say Y here to
1090 all. The local APIC supports CPU-generated self-interrupts (timer,
1095 bool "IO-APIC support on uniprocessors"
1098 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
1099 SMP-capable replacement for PC-style interrupt controllers. Most
1102 If you have a single-CPU system with an IO-APIC, you can say Y here
1103 to use it. If you say Y here even though your machine doesn't have
1104 an IO-APIC, then the kernel will still run with no slowdown at all.
1132 entry in the chipset's IO-APIC is masked (as, e.g. the RT
1136 IRQ" is delivered to the CPUs. The workaround also tells the
1137 kernel to set up the IRQ handler on the boot IRQ line. In this
1138 way only one interrupt is delivered to the kernel. Otherwise
1139 the spurious second interrupt may cause the kernel to bring
1150 Machine Check support allows the processor to notify the
1153 ranging from warning messages to halting the machine.
1160 userspace logging daemon. Consider switching to the new generation
1184 systems. These typically need to be enabled explicitly on the command
1197 QA it is safe to say n.
1205 This option allows user programs to put the CPU into V8086
1206 mode, which is an 80286-era approximation of 16-bit real mode.
1210 available to accelerate real mode DOS programs. However, any
1213 fall back to software emulation. Nevertheless, if you are using
1214 a 16-bit DOS program where 16-bit performance matters, vm86
1215 mode might be faster than emulation and you might want to
1218 Note that any app that works on a 64-bit kernel is unlikely to
1219 need this option, as 64-bit kernels don't, and can't, support
1220 V8086 mode. This option is also unrelated to 16-bit protected
1221 mode and is not needed to run most 16-bit programs under Wine.
1233 bool "Enable support for 16-bit segments" if EXPERT
1237 This option is required by programs like Wine to run 16-bit
1240 plus 16K runtime memory on x86-64,
1256 it is roughly equivalent to booting with vsyscall=none, except
1258 tries to use a vsyscall. With this option set to N, offending
1263 care should be used even with newer programs if set to N.
1276 space aside of accessing all 65536 I/O ports also to disable
1277 interrupts. To gain this access the caller needs CAP_SYS_RAWIO
1281 The emulation restricts the functionality of the syscall to
1283 ability to disable interrupts from user space which would be
1290 This adds a driver to safely access the System Management Mode of
1291 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
1293 is used to set the BIOS and power saving options on Toshiba portables.
1295 For information on utilities to make use of this driver see the
1299 Say Y if you intend to run this kernel on a Toshiba portable.
1306 This enables chipset and/or board specific fixups to be done
1307 in order to get reboot to work correctly. This is only needed on
1313 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
1315 Say Y if you want to enable the fixup. Currently, it's safe to
1347 To prevent that users load microcode late which modifies already
1350 revision must be active in the CPU to safely load that new microcode
1367 related to patch parsing and handling is done as on baremetal with
1370 You almost certainly want to say n here.
1373 tristate "/dev/cpu/*/msr - Model-specific register support"
1375 This device gives privileged processes access to the x86
1376 Model-Specific Registers (MSRs). It is a character device with
1377 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
1378 MSR accesses are directed to a specific CPU on multi-processor
1382 tristate "/dev/cpu/*/cpuid - CPU information support"
1384 This device gives processes access to the x86 CPUID instruction to
1386 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
1387 /dev/cpu/31/cpuid.
1393 Linux can use up to 4 Gigabytes of physical memory on x86 systems.
1394 However, the address space of 32-bit x86 processors is only 4
1405 by the kernel to permanently map as much physical memory as
1420 If the address range available to the kernel is less than the
1423 than low memory, as it needs to be mapped into the kernel first.
1425 available to user programs, making the address space there
1427 will also likely make your kernel incompatible with binary-only
1465 larger swapspace support for non-overcommit purposes. It
1474 linear 1 GB mappings (even if the CPU otherwise
1483 helps to determine the effectiveness of preserving large and huge
1503 Say yes to enable support for the encryption of system memory.
1515 Enable NUMA (Non-Uniform Memory Access) support.
1517 The kernel will try to allocate memory used by a CPU on the
1518 local memory controller of the CPU and add some more
1519 NUMA awareness to the kernel.
1521 For 64-bit this is recommended if the system is Intel Core i7
1529 depends on X86_64 && NUMA && PCI
1532 you have a multi processor AMD system. This uses an old method to
1534 of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,
1540 depends on X86_64 && NUMA && ACPI && PCI
1554 system. Increases memory reserved to accommodate various tables.
1577 See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
1578 If you are unsure how to answer this question, answer N.
1593 tristate "Support non-standard NVDIMMs and ADR protected memory"
1600 Treat memory marked using the non-standard e820 type of 12 as used
1601 by the Intel Sandy Bridge-EP reference BIOS as protected memory.
1602 The kernel will offer these regions to the 'pmem' driver so
1611 is suspected to be caused by BIOS. Even when enabled in the
1617 Documentation/admin-guide/kernel-parameters.rst to adjust this.
1625 BIOS-originated corruption always affects the same memory,
1626 you can use memmap= to prevent the kernel from using that
1649 If you don't have a math coprocessor, you need to say Y here; if you
1654 loader (lilo or loadlin) about how to pass options to the kernel at
1655 boot time.) This means that it is a good idea to say Y here if you
1656 intend to use this kernel on different machines.
1659 emulation can be found in <file:arch/x86/math-emu/README>.
1669 the Memory Type Range Registers (MTRRs) may be used to control
1670 processor access to memory ranges. This is most useful if you have
1671 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1672 allows bus write transfers to be combined into a larger transfer
1673 before bursting over the PCI/AGP bus. This can increase performance
1675 /proc/mtrr file which may be used to manipulate your processor's
1683 Registers (ARRs) which provide a similar functionality to MTRRs. For
1684 these, the ARRs are used to emulate the MTRRs.
1685 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1687 write-combining. All of these processors are supported by this code
1688 and it makes sense to say Y here if you have one of them.
1691 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1692 can lead to all sorts of problems, so it's good to say Y here.
1695 just add about 9 KB to your kernel.
1704 Convert MTRR layout from continuous to discrete, so X drivers can
1714 int "MTRR cleanup enable value (0-1)"
1722 int "MTRR cleanup spare reg num (0-7)"
1736 Use PAT attributes to setup page level cache control.
1742 spontaneous reboots) or a non-working video driver.
1758 specific cases in protected and virtual-8086 modes. Emulated
1763 # Retpoline check to work around https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93654
1764 …def_bool ((CC_IS_GCC && $(cc-option, -fcf-protection=branch -mindirect-branch-register)) || CC_IS_…
1765 $(as-instr,endbr64)
1780 hardware support course-grain forward-edge Control Flow Integrity
1783 code with them to make this happen.
1785 In addition to building the kernel with IBT, seal all functions that
1795 # Note: only available in 64-bit mode
1801 page-based protections, but without requiring modification of the
1804 For details, see Documentation/core-api/protection-keys.rst
1818 allows to optimize locking protocols through lock elision which
1819 can lead to a noticeable performance boost.
1822 to form side channel attacks (e.g. TAA) and chances are there
1827 Even with TSX enabled, the kernel will attempt to enable the best
1831 This option allows to set the default tsx mode between tsx=on, =off
1832 and =auto. See Documentation/admin-guide/kernel-parameters.txt for more
1842 TSX is disabled if possible - equals to tsx=off command line parameter.
1847 TSX is always enabled on TSX capable HW - equals the tsx=on command
1853 TSX is enabled on TSX capable HW that is believed to be safe against
1854 side channel attacks- equals the tsx=auto command line parameter.
1865 Intel(R) Software Guard eXtensions (SGX) is a set of CPU instructions
1866 that can be used by applications to set aside private regions of code
1867 and data, referred to as enclaves. An enclave's private memory can
1884 Applications must be enabled to use it, and old userspace does not
1905 support in the host kernel to run confidential VMs.
1917 This enables the kernel to use EFI runtime services that are
1922 at <http://elilo.sourceforge.net> in order to take advantage
1924 resultant kernel should continue to boot on existing non-EFI
1932 This kernel feature allows a bzImage to be loaded directly
1935 See Documentation/admin-guide/efi-stub.rst for more information.
1942 Select this in order to include support for the deprecated EFI
1955 bool "EFI mixed-mode support"
1958 Enabling this feature allows a 64-bit kernel to be booted
1959 on a 32-bit firmware, provided that your CPU supports 64-bit
1962 Note that it is not possible to boot a mixed-mode enabled
1963 kernel via the EFI boot stub - a bootloader that supports
1969 bool "Export EFI runtime maps to sysfs" if EXPERT
1972 Export EFI runtime memory regions to /sys/firmware/efi/runtime-map.
1973 That memory map is required by the 2nd kernel to set up EFI virtual
1976 See also Documentation/ABI/testing/sysfs-firmware-efi-runtime-map.
2028 will decompress itself to above physical address and run from there.
2033 In normal kdump cases one does not have to set/change this option
2035 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
2037 to use a bzImage for capturing the crash dump and want to use a
2039 to be specifically compiled to run from a specific memory area
2043 leave the value here unchanged to 0x1000000 and set
2044 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
2045 for capturing the crash dump change this value to start of
2048 command line boot parameter passed to the panic-ed
2049 kernel. Please take a look at Documentation/admin-guide/kdump/kdump.rst
2053 one does not have to build two kernels. Same kernel can be used
2056 is present because there are users out there who continue to use
2068 The relocations tend to make the kernel binary about 10% larger,
2091 On 64-bit, the kernel physical and virtual addresses are
2093 between 16MB and the top of physical memory (up to 64TB). The
2094 virtual address will be randomized from 16MB up to 1GB (9 bits
2096 available to kernel modules from 1.5GB to 1GB.
2098 On 32-bit, the kernel physical and virtual addresses are
2099 randomized together. They will be randomized from 16MB up to
2110 limited due to memory layouts.
2121 hex "Alignment value to which kernel should be aligned"
2130 If bootloader loads the kernel at a non-aligned address and
2131 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
2132 address aligned to above value and run from there.
2134 If bootloader loads the kernel at a non-aligned address and
2136 load address and decompress itself to the address it has been
2142 On 32-bit this value must be a multiple of 0x2000. On 64-bit
2172 Define the padding in terabytes added to the existing physical
2185 to 64-bit linear addresses, allowing software to use of the
2201 presented with a 32-bit vDSO that is not mapped at the address
2211 dl_main: Assertion `(void *) ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed!
2214 option from 1 to 0, which turns off the 32-bit vDSO entirely.
2218 are unlikely to be using a buggy version of glibc.
2225 Legacy user code that does not know how to find the vDSO expects
2226 to be able to issue three syscalls by calling fixed addresses in
2228 it can be used to assist security vulnerability exploitation.
2237 to improve security.
2249 certain uses of the vsyscall area as an ASLR-bypassing
2256 eliminate any risk of ASLR bypass due to the vsyscall
2257 fixed address mapping. Attempts to use the vsyscalls
2258 will be reported to dmesg, so that either old or
2264 bool "Built-in kernel command line"
2266 Allow for specifying boot arguments to the kernel at
2268 necessary or convenient to provide some or all of the
2270 to not rely on the boot loader to provide them.)
2272 To compile command line arguments into the kernel,
2273 set this option to 'Y', then fill in the
2276 Systems with fully functional boot loaders (i.e. non-embedded)
2277 should leave this option set to 'N'.
2280 string "Built-in kernel command string"
2286 command line at boot time, it is appended to this string to
2289 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
2292 In most cases, the command line (whether built-in or provided
2297 bool "Built-in command line overrides boot loader arguments"
2300 Set this option to 'Y' to have the kernel ignore the boot loader
2301 command line, and use ONLY the built-in command line.
2303 This is used to work around broken boot loaders. This should
2304 be set to 'N' under normal conditions.
2310 Linux can allow user programs to install a per-process x86
2312 call. This is required to run 16-bit or segmented code such as
2316 Enabling this feature adds a small amount of overhead to
2317 context switches and increases the low-level kernel attack
2327 already too small with AVX512 support. Add a mechanism to
2336 Say 'N' unless you want to really enforce this check.
2339 bool "Attempt to use FineIBT by default at boot time"
2344 Attempt to use FineIBT by default at boot time. If enabled,
2361 def_bool $(success,echo 'int __seg_fs fs; int __seg_gs gs;' | $(CC) -x c - -S -o /dev/null)
2365 # -fsanitize=kernel-address (KASAN) and -fsanitize=thread (KCSAN)
2380 def_bool $(cc-option,-mharden-sls=all)
2383 def_bool $(cc-option,-mfunction-return=thunk-extern)
2386 def_bool $(cc-option,-fpatchable-function-entry=16,16)
2389 def_bool $(cc-option,-fsanitize=kcfi -fsanitize-kcfi-arity)
2400 # Basically: FUNCTION_ALIGNMENT - 5*CFI
2434 bool "Mitigations for CPU vulnerabilities"
2437 Say Y here to enable options which enable mitigations for hardware
2438 vulnerabilities (usually related to speculative execution).
2439 Mitigations can be disabled or restricted to SMT systems at runtime
2465 Compile kernel with the retpoline compiler options to guard against
2466 kernel-to-user data leaks by avoiding speculative indirect
2467 branches. Requires a compiler with -mindirect-branch=thunk-extern
2471 bool "Enable return-thunks"
2476 Compile the kernel with the return-thunks compiler option to guard
2477 against kernel-to-user data leaks by avoiding return speculation.
2478 Requires a compiler with -mfunction-return=thunk-extern
2495 Compile the kernel with call depth tracking to mitigate the Intel
2496 SKL Return-Stack-Buffer (RSB) underflow issue. The mitigation is off
2497 by default and needs to be enabled on the kernel command line via the
2498 retbleed=stuff option. For non-affected systems the overhead of this
2499 option is marginal as the call depth tracking is using run-time
2513 trouble shooting. The debug prints need to be enabled on the
2514 kernel command line with 'debug-callthunks'.
2524 spec_rstack_overflow={ibpb,ibpb-vmexit} mitigations.
2532 This mitigates both spectre_v2 and retbleed at great cost to
2540 Enable the SRSO mitigation needed on AMD Zen1-4 machines.
2543 bool "Mitigate Straight-Line-Speculation"
2548 Compile the kernel with straight-line-speculation options to guard
2558 vulnerability which allows unprivileged speculative access to data
2560 instructions to infer the stale vector register data.
2569 allows unprivileged speculative access to stale data previously
2571 See also <file:Documentation/admin-guide/hw-vuln/reg-file-data-sampling.rst>
2574 bool "Mitigate Spectre-BHB (Branch History Injection)"
2579 where the branch history buffer is poisoned to speculatively steer
2581 See <file:Documentation/admin-guide/hw-vuln/spectre.rst>
2590 to data which is available in various CPU internal buffers.
2591 See also <file:Documentation/admin-guide/hw-vuln/mds.rst>
2599 vulnerability that allows unprivileged speculative access to data
2600 which is available in various CPU internal buffers by using
2602 See also <file:Documentation/admin-guide/hw-vuln/tsx_async_abort.rst>
2610 Stale Data Vulnerabilities are a class of memory-mapped I/O (MMIO)
2612 attacker to have access to MMIO.
2614 <file:Documentation/admin-guide/hw-vuln/processor_mmio_stale_data.rst>
2622 hardware vulnerability which allows unprivileged speculative access to data
2624 See <file:Documentation/admin-guide/hw-vuln/l1tf.rst
2634 in many modern microprocessors, similar to Spectre v2. An
2635 unprivileged attacker can use these flaws to bypass conventional
2636 memory security restrictions to gain read access to privileged memory
2647 See also <file:Documentation/admin-guide/hw-vuln/spectre.rst>
2657 victim to gadget code by poisoning the branch target buffer of a CPU
2659 See also <file:Documentation/admin-guide/hw-vuln/spectre.rst>
2668 Sampling (MDS) techniques to infer values returned from special
2673 <file:Documentation/admin-guide/hw-vuln/special-register-buffer-data-sampling.rst>
2681 of speculative execution in a similar way to the Meltdown and Spectre
2694 See <file:Documentation/admin-guide/hw-vuln/indirect-target-selection.rst>
2702 security vulnerability on AMD CPUs which can lead to forwarding of
2703 invalid info to subsequent instructions and thus can affect their
2712 vulnerability on Intel and AMD CPUs that may allow a guest to do
2742 battery status information, and user-space programs will receive
2746 BIOS by passing the "apm=off" option to the kernel at boot time.
2749 machines with more than one CPU.
2751 In order to use APM, you will need supporting software. For location
2752 and more information, read <file:Documentation/power/apm-acpi.rst>
2753 and the Battery Powered Linux mini-HOWTO, available from
2758 VESA-compliant "green" monitors.
2763 may cause those machines to panic during the boot phase.
2767 random kernel OOPSes or reboots that don't seem to be related to
2776 2) pass the "idle=poll" option to the kernel
2778 the "no387" option to the kernel
2779 4) pass the "floppy=nodma" option to the kernel
2780 5) pass the "mem=4M" option to the kernel (thereby disabling
2782 6) make sure that the CPU is not over clocked.
2786 10) install a better fan for the CPU
2790 To compile this driver as a module, choose M here: the
2799 compliant APM BIOS, you want to say N. However, on the NEC Versa M
2800 series notebooks, it is necessary to say Y because of a BIOS bug.
2808 State, or take power saving steps in response to CPU Idle calls."
2809 This driver will make CPU Idle calls when Linux is idle (unless this
2810 feature is turned off -- see "Do CPU IDLE calls", below). This
2812 will be dependent on your BIOS implementation. You may need to turn
2821 bool "Make CPU Idle calls when idle"
2823 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
2825 a slowed CPU clock rate, when the machine is idle. These idle calls
2828 whenever the CPU becomes idle. (On machines with more than one CPU,
2834 Enable console blanking using the APM. Some laptops can use this to
2838 when using the X Window system. This also doesn't have anything to
2839 do with your VESA-compliant power-saving monitor. Further, this
2840 option doesn't work for all laptops -- it might not turn off your
2841 backlight at all, or it might print a lot of errors to the console,
2847 Normally we disable external interrupts while we are making calls to
2848 the APM BIOS as a measure to lessen the effects of a badly behaving
2850 needs to. Unfortunately, some BIOSes do not -- especially those in
2852 suspend, try setting this to Y. Otherwise, say N.
2864 menu "Bus options (PCI etc.)"
2867 prompt "PCI access mode"
2868 depends on X86_32 && PCI
2871 On PCI systems, the BIOS can be used to detect the PCI devices and
2872 determine their configuration. However, some old PCI motherboards
2874 PCI-based systems don't have any BIOS at all. Linux can also try to
2875 detect the PCI hardware directly without using the BIOS.
2878 PCI devices. If you choose "BIOS", the BIOS will be used,
2880 choose "MMConfig", then PCI Express MMCONFIG will be used.
2882 direct access method and falls back to the BIOS if that doesn't
2895 bool "OLPC XO-1"
2905 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
2907 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
2910 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))
2913 bool "Support mmconfig PCI config space access" if X86_64
2915 depends on PCI && (ACPI || JAILHOUSE_GUEST)
2918 Add support for accessing the PCI configuration space as a memory
2920 this (it must have PCI Express and ACPI for it to be available).
2923 problems, the mechanism can be switched off with the 'pci=nommconf'
2933 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
2937 depends on PCI && XEN
2944 bool "Read PCI host bridge windows from the CNB20LE chipset" if EXPERT
2945 depends on X86_32 && PCI
2947 Read the PCI windows out of the CNB20LE host bridge. This allows
2948 PCI hotplug to work on systems with the CNB20LE chipset which do
2954 To find out if you have such a chipset, search for a PCI device with
2955 1166:0009 PCI IDs, for example by executing
2956 lspci -nn | grep '1166:0009'
2960 is known to be incomplete.
2969 bus. ISA is an older system, displaced by PCI and newer bus
2970 architectures -- if your target machine is modern, it probably does
2975 # x86_64 have no ISA slots, but can have ISA-style DMA.
2977 bool "ISA-style DMA support" if (X86_64 && EXPERT)
2980 Enables ISA-style DMA support for devices requiring such controllers.
2989 name of a bus system, i.e. the way the CPU talks to the other stuff
2990 inside your box. Other bus systems are PCI, EISA, MicroChannel
2991 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
2999 PCI-IDs of several on-chip devices, so its a good dependency
3005 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
3009 This driver provides a clocksource built upon the on-chip
3010 27MHz high-resolution timer. Its also a workaround for
3011 NSC Geode SC-1100's buggy TSC, which loses time when the
3028 bool "OLPC XO-1 Power Management"
3031 Add support for poweroff and suspend of the OLPC XO-1 laptop.
3034 bool "OLPC XO-1 Real Time Clock"
3037 Add support for the XO-1 real time clock, which can be used as a
3041 bool "OLPC XO-1 SCI extras"
3046 Add support for SCI-based features of the OLPC XO-1 laptop:
3047 - EC-driven system wakeups
3048 - Power button
3049 - Ebook switch
3050 - Lid switch
3051 - AC adapter status updates
3052 - Battery status updates
3055 bool "OLPC XO-1.5 SCI extras"
3059 Add support for SCI-based features of the OLPC XO-1.5 laptop:
3060 - EC-driven system wakeups
3061 - AC adapter status updates
3062 - Battery status updates
3078 (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs
3080 Note: You have to set alix.force=1 for boards with Award BIOS.
3098 bool "Technologic Systems TS-5500 platform support"
3104 This option enables system support for the Technologic Systems TS-5500.
3114 depends on CPU_SUP_AMD && PCI
3127 Include code to run legacy 32-bit programs under a
3128 64-bit kernel. You should likely turn this on, unless you're
3129 100% sure that you don't have any 32-bit programs left.
3136 Make IA32 emulation disabled by default. This prevents loading 32-bit
3137 processes and access to 32-bit syscalls. If unsure, leave it to its
3141 bool "x32 ABI for 64-bit mode"
3143 # llvm-objcopy does not convert x86_64 .note.gnu.property or
3144 # compressed debug sections to x86_x32 properly:
3147 depends on $(success,$(OBJCOPY) --version | head -n1 | grep -qv llvm)
3149 Include code to run binaries for the x32 native 32-bit ABI
3150 for 64-bit processors. An x32 process gets access to the
3151 full 64-bit register file and wide data path while leaving