📄 kconfig
字号:
config SB1_PASS_1_WORKAROUNDS bool depends on CPU_SB1_PASS_1 default yconfig SB1_PASS_2_WORKAROUNDS bool depends on CPU_SB1 && (CPU_SB1_PASS_2_2 || CPU_SB1_PASS_2) default yconfig SB1_PASS_2_1_WORKAROUNDS bool depends on CPU_SB1 && CPU_SB1_PASS_2 default yconfig 64BIT_PHYS_ADDR boolconfig CPU_HAS_LLSC boolconfig CPU_HAS_SMARTMIPS depends on SYS_SUPPORTS_SMARTMIPS bool "Support for the SmartMIPS ASE" help SmartMIPS is a extension of the MIPS32 architecture aimed at increased security at both hardware and software level for smartcards. Enabling this option will allow proper use of the SmartMIPS instructions by Linux applications. However a kernel with this option will not work on a MIPS core without SmartMIPS core. If you don't know you probably don't have SmartMIPS and should say N here.config CPU_HAS_WB boolconfig 64BIT_CONTEXT bool "Save 64bit integer registers" depends on 32BIT && CPU_LOONGSON2 help Loongson2 CPU is 64bit , when used in 32BIT mode, its integer registers can still be accessed as 64bit, mainly for multimedia instructions. We must have all 64bit save/restored to make sure those instructions to get correct result.## Vectored interrupt mode is an R2 feature#config CPU_MIPSR2_IRQ_VI bool## Extended interrupt mode is an R2 feature#config CPU_MIPSR2_IRQ_EI boolconfig CPU_HAS_SYNC bool depends on !CPU_R3000 default yconfig GENERIC_CLOCKEVENTS_BROADCAST bool## Use the generic interrupt handling code in kernel/irq/:#config GENERIC_HARDIRQS bool default yconfig GENERIC_IRQ_PROBE bool default yconfig IRQ_PER_CPU bool## - Highmem only makes sense for the 32-bit kernel.# - The current highmem code will only work properly on physically indexed# caches such as R3000, SB1, R7000 or those that look like they're virtually# indexed such as R4000/R4400 SC and MC versions or R10000. So for the# moment we protect the user and offer the highmem option only on machines# where it's known to be safe. This will not offer highmem on a few systems# such as MIPS32 and MIPS64 CPUs which may have virtual and physically# indexed CPUs but we're playing safe.# - We use SYS_SUPPORTS_HIGHMEM to offer highmem only for systems where we# know they might have memory configurations that could make use of highmem# support.#config HIGHMEM bool "High Memory Support" depends on 32BIT && CPU_SUPPORTS_HIGHMEM && SYS_SUPPORTS_HIGHMEMconfig CPU_SUPPORTS_HIGHMEM boolconfig SYS_SUPPORTS_HIGHMEM boolconfig SYS_SUPPORTS_SMARTMIPS boolconfig ARCH_FLATMEM_ENABLE def_bool y depends on !NUMAconfig ARCH_DISCONTIGMEM_ENABLE bool default y if SGI_IP27 help Say Y to support efficient handling of discontiguous physical memory, for architectures which are either NUMA (Non-Uniform Memory Access) or have huge holes in the physical address space for other reasons. See <file:Documentation/vm/numa> for more.config ARCH_POPULATES_NODE_MAP def_bool yconfig ARCH_SPARSEMEM_ENABLE bool select SPARSEMEM_STATICconfig NUMA bool "NUMA Support" depends on SYS_SUPPORTS_NUMA help Say Y to compile the kernel to support NUMA (Non-Uniform Memory Access). This option improves performance on systems with more than two nodes; on two node systems it is generally better to leave it disabled; on single node systems disable this option disabled.config SYS_SUPPORTS_NUMA boolconfig NODES_SHIFT int default "6" depends on NEED_MULTIPLE_NODESsource "mm/Kconfig"config SMP bool "Multi-Processing support" depends on SYS_SUPPORTS_SMP select IRQ_PER_CPU help This enables support for systems with more than one CPU. If you have a system with only one CPU, like most personal computers, say N. If you have a system with more than one CPU, say Y. If you say N here, the kernel will run on single and multiprocessor machines, but will use only one CPU of a multiprocessor machine. If you say Y here, the kernel will run on many, but not all, singleprocessor machines. On a singleprocessor machine, the kernel will run faster if you say N here. People using multiprocessor machines who say Y here should also say Y to "Enhanced Real Time Clock Support", below. See also the <file:Documentation/smp.txt> and the SMP-HOWTO available at <http://www.tldp.org/docs.html#howto>. If you don't know what to do here, say N.config SYS_SUPPORTS_SMP boolconfig NR_CPUS_DEFAULT_1 boolconfig NR_CPUS_DEFAULT_2 boolconfig NR_CPUS_DEFAULT_4 boolconfig NR_CPUS_DEFAULT_8 boolconfig NR_CPUS_DEFAULT_16 boolconfig NR_CPUS_DEFAULT_32 boolconfig NR_CPUS_DEFAULT_64 boolconfig NR_CPUS int "Maximum number of CPUs (2-64)" range 1 64 if NR_CPUS_DEFAULT_1 depends on SMP default "1" if NR_CPUS_DEFAULT_1 default "2" if NR_CPUS_DEFAULT_2 default "4" if NR_CPUS_DEFAULT_4 default "8" if NR_CPUS_DEFAULT_8 default "16" if NR_CPUS_DEFAULT_16 default "32" if NR_CPUS_DEFAULT_32 default "64" if NR_CPUS_DEFAULT_64 help This allows you to specify the maximum number of CPUs which this kernel will support. The maximum supported value is 32 for 32-bit kernel and 64 for 64-bit kernels; the minimum value which makes sense is 1 for Qemu (useful only for kernel debugging purposes) and 2 for all others. This is purely to save memory - each supported CPU adds approximately eight kilobytes to the kernel image. For best performance should round up your number of processors to the next power of two.source "kernel/time/Kconfig"## Timer Interrupt Frequency Configuration#choice prompt "Timer frequency" default HZ_250 help Allows the configuration of the timer frequency. config HZ_48 bool "48 HZ" if SYS_SUPPORTS_48HZ config HZ_100 bool "100 HZ" if SYS_SUPPORTS_100HZ || SYS_SUPPORTS_ARBIT_HZ config HZ_128 bool "128 HZ" if SYS_SUPPORTS_128HZ || SYS_SUPPORTS_ARBIT_HZ config HZ_250 bool "250 HZ" if SYS_SUPPORTS_250HZ || SYS_SUPPORTS_ARBIT_HZ config HZ_256 bool "256 HZ" if SYS_SUPPORTS_256HZ || SYS_SUPPORTS_ARBIT_HZ config HZ_1000 bool "1000 HZ" if SYS_SUPPORTS_1000HZ || SYS_SUPPORTS_ARBIT_HZ config HZ_1024 bool "1024 HZ" if SYS_SUPPORTS_1024HZ || SYS_SUPPORTS_ARBIT_HZendchoiceconfig SYS_SUPPORTS_48HZ boolconfig SYS_SUPPORTS_100HZ boolconfig SYS_SUPPORTS_128HZ boolconfig SYS_SUPPORTS_250HZ boolconfig SYS_SUPPORTS_256HZ boolconfig SYS_SUPPORTS_1000HZ boolconfig SYS_SUPPORTS_1024HZ boolconfig SYS_SUPPORTS_ARBIT_HZ bool default y if !SYS_SUPPORTS_48HZ && !SYS_SUPPORTS_100HZ && \ !SYS_SUPPORTS_128HZ && !SYS_SUPPORTS_250HZ && \ !SYS_SUPPORTS_256HZ && !SYS_SUPPORTS_1000HZ && \ !SYS_SUPPORTS_1024HZconfig HZ int default 48 if HZ_48 default 100 if HZ_100 default 128 if HZ_128 default 250 if HZ_250 default 256 if HZ_256 default 1000 if HZ_1000 default 1024 if HZ_1024source "kernel/Kconfig.preempt"config MIPS_INSANE_LARGE bool "Support for large 64-bit configurations" depends on CPU_R10000 && 64BIT help MIPS R10000 does support a 44 bit / 16TB address space as opposed to previous 64-bit processors which only supported 40 bit / 1TB. If you need processes of more than 1TB virtual address space, say Y here. This will result in additional memory usage, so it is not recommended for normal users.config KEXEC bool "Kexec system call (EXPERIMENTAL)" depends on EXPERIMENTAL help kexec is a system call that implements the ability to shutdown your current kernel, and to start another kernel. It is like a reboot but it is independent of the system firmware. And like a reboot you can start any kernel with it, not just Linux. The name comes from the similarity to the exec system call. It is an ongoing process to be certain the hardware in a machine is properly shutdown, so do not be surprised if this code does not initially work for you. It may help to enable device hotplugging support. As of this writing the exact hardware interface is strongly in flux, so no good recommendation can be made.config SECCOMP bool "Enable seccomp to safely compute untrusted bytecode" depends on PROC_FS default y help This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/<pid>/seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode. If unsure, say Y. Only embedded should say N here.endmenuconfig RWSEM_GENERIC_SPINLOCK bool default yconfig LOCKDEP_SUPPORT bool default yconfig STACKTRACE_SUPPORT bool default ysource "init/Kconfig"menu "Bus options (PCI, PCMCIA, EISA, ISA, TC)"config HW_HAS_EISA boolconfig HW_HAS_PCI boolconfig PCI bool "Support for PCI controller" depends on HW_HAS_PCI select PCI_DOMAINS help Find out whether you have a PCI motherboard. PCI is the name of a bus system, i.e. the way the CPU talks to the other stuff inside your box. Other bus systems are ISA, EISA, or VESA. If you have PCI, say Y, otherwise N. The PCI-HOWTO, available from <http://www.tldp.org/docs.html#howto>, contains valuable information about which PCI hardware does work under Linux and which doesn't.config PCI_DOMAINS boolsource "drivers/pci/Kconfig"## ISA support is now enabled via select. Too many systems still have the one# or other ISA chip on the board that users don't know about so don't expect# users to choose the right thing ...#config ISA boolconfig EISA bool "EISA support" depends on HW_HAS_EISA select ISA select GENERIC_ISA_DMA ---help--- The Extended Industry Standard Architecture (EISA) bus was developed as an open alternative to the IBM MicroChannel bus. The EISA bus provided some of the features of the IBM MicroChannel bus while maintaining backward compatibility with cards made for the older ISA bus. The EISA bus saw limited use between 1988 and 1995 when it was made obsolete by the PCI bus. Say Y here if you are building a kernel for an EISA-based machine. Otherwise, say N.source "drivers/eisa/Kconfig"config TC bool "TURBOchannel support" depends on MACH_DECSTATION help TurboChannel is a DEC (now Compaq (now HP)) bus for Alpha and MIPS processors. Documentation on writing device drivers for TurboChannel is available at: <http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.#config ACCESSBUS# bool "Access.Bus support"# depends on TCconfig MMU bool default yconfig I8253 boolconfig PCSPEAKER boolconfig ZONE_DMA32 boolsource "drivers/pcmcia/Kconfig"source "drivers/pci/hotplug/Kconfig"endmenumenu "Executable file formats"source "fs/Kconfig.binfmt"config TRAD_SIGNALS boolconfig BINFMT_IRIX bool "Include IRIX binary compatibility" depends on CPU_BIG_ENDIAN && 32BIT && BROKENconfig MIPS32_COMPAT bool "Kernel support for Linux/MIPS 32-bit binary compatibility" depends on 64BIT help Select this option if you want Linux/MIPS 32-bit binary compatibility. Since all software available for Linux/MIPS is currently 32-bit you should say Y here.config COMPAT bool depends on MIPS32_COMPAT default yconfig SYSVIPC_COMPAT bool depends on COMPAT && SYSVIPC default yconfig MIPS32_O32 bool "Kernel support for o32 binaries" depends on MIPS32_COMPAT help Select this option if you want to run o32 binaries. These are pure 32-bit binaries as used by the 32-bit Linux/MIPS port. Most of existing binaries are in this format. If unsure, say Y.config MIPS32_N32 bool "Kernel support for n32 binaries" depends on MIPS32_COMPAT help Select this option if you want to run n32 binaries. These are 64-bit binaries using 32-bit quantities for addressing and certain data that would normally be 64-bit. They are used in special cases. If unsure, say N.config BINFMT_ELF32 bool default y if MIPS32_O32 || MIPS32_N32endmenumenu "Power management options"source "kernel/power/Kconfig"endmenusource "net/Kconfig"source "drivers/Kconfig"source "fs/Kconfig"source "kernel/Kconfig.instrumentation"source "arch/mips/Kconfig.debug"source "security/Kconfig"source "crypto/Kconfig"source "lib/Kconfig"⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -