7 option env="KERNELVERSION"
13 default "/lib/modules/$UNAME_RELEASE/.config"
14 default "/etc/kernel-config"
15 default "/boot/config-$UNAME_RELEASE"
16 default "arch/$ARCH/defconfig"
21 bool "Prompt for development and/or incomplete code/drivers"
23 Some of the various things that Linux supports (such as network
24 drivers, file systems, network protocols, etc.) can be in a state
25 of development where the functionality, stability, or the level of
26 testing is not yet high enough for general use. This is usually
27 known as the "alpha-test" phase among developers. If a feature is
28 currently in alpha-test, then the developers usually discourage
29 uninformed widespread use of this feature by the general public to
30 avoid "Why doesn't this work?" type mail messages. However, active
31 testing and use of these systems is welcomed. Just be aware that it
32 may not meet the normal level of reliability or it may fail to work
33 in some special cases. Detailed bug reports from people familiar
34 with the kernel internals are usually welcomed by the developers
35 (before submitting bug reports, please read the documents
36 <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
37 <file:Documentation/BUG-HUNTING>, and
38 <file:Documentation/oops-tracing.txt> in the kernel source).
40 This option will also make obsoleted drivers available. These are
41 drivers that have been replaced by something else, and/or are
42 scheduled to be removed in a future kernel release.
44 Unless you intend to help test and develop a feature or driver that
45 falls into this category, or you have a situation that requires
46 using these features, you should probably say N here, which will
47 cause the configurator to present you with fewer choices. If
48 you say Y here, you will be offered the choice of using features or
49 drivers that are currently considered to be in the alpha-test phase.
56 depends on BROKEN || !SMP
61 depends on SMP || PREEMPT
64 config INIT_ENV_ARG_LIMIT
69 Maximum of each of the number of arguments and environment
70 variables passed to init from the kernel command line.
74 string "Local version - append to kernel release"
76 Append an extra string to the end of your kernel version.
77 This will show up when you type uname, for example.
78 The string you set here will be appended after the contents of
79 any files with a filename matching localversion* in your
80 object and source tree, in that order. Your total string can
81 be a maximum of 64 characters.
83 config LOCALVERSION_AUTO
84 bool "Automatically append version information to the version string"
87 This will try to automatically determine if the current tree is a
88 release tree by looking for git tags that belong to the current
91 A string of the format -gxxxxxxxx will be added to the localversion
92 if a git-based tree is found. The string generated by this will be
93 appended after any matching localversion* files, and after the value
94 set in CONFIG_LOCALVERSION.
96 (The actual string used here is the first eight characters produced
97 by running the command:
99 $ git rev-parse --verify HEAD
101 which is done within the script "scripts/setlocalversion".)
104 bool "Support for paging of anonymous memory (swap)"
105 depends on MMU && BLOCK
108 This option allows you to choose whether you want to have support
109 for so called swap devices or swap files in your kernel that are
110 used to provide more virtual memory than the actual RAM present
111 in your computer. If unsure say Y.
116 Inter Process Communication is a suite of library functions and
117 system calls which let processes (running programs) synchronize and
118 exchange information. It is generally considered to be a good thing,
119 and some programs won't run unless you say Y here. In particular, if
120 you want to run the DOS emulator dosemu under Linux (read the
121 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
122 you'll need to say Y here.
124 You can find documentation about IPC with "info ipc" and also in
125 section 6.4 of the Linux Programmer's Guide, available from
126 <http://www.tldp.org/guides.html>.
128 config SYSVIPC_SYSCTL
135 bool "POSIX Message Queues"
136 depends on NET && EXPERIMENTAL
138 POSIX variant of message queues is a part of IPC. In POSIX message
139 queues every message has a priority which decides about succession
140 of receiving it by a process. If you want to compile and run
141 programs written e.g. for Solaris with use of its POSIX message
142 queues (functions mq_*) say Y here.
144 POSIX message queues are visible as a filesystem called 'mqueue'
145 and can be mounted somewhere if you want to do filesystem
146 operations on message queues.
150 config BSD_PROCESS_ACCT
151 bool "BSD Process Accounting"
153 If you say Y here, a user level program will be able to instruct the
154 kernel (via a special system call) to write process accounting
155 information to a file: whenever a process exits, information about
156 that process will be appended to the file by the kernel. The
157 information includes things such as creation time, owning user,
158 command name, memory usage, controlling terminal etc. (the complete
159 list is in the struct acct in <file:include/linux/acct.h>). It is
160 up to the user level program to do useful things with this
161 information. This is generally a good idea, so say Y.
163 config BSD_PROCESS_ACCT_V3
164 bool "BSD Process Accounting version 3 file format"
165 depends on BSD_PROCESS_ACCT
168 If you say Y here, the process accounting information is written
169 in a new file format that also logs the process IDs of each
170 process and it's parent. Note that this file format is incompatible
171 with previous v0/v1/v2 file formats, so you will need updated tools
172 for processing it. A preliminary version of these tools is available
173 at <http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/>.
176 bool "Export task/process statistics through netlink (EXPERIMENTAL)"
180 Export selected statistics for tasks/processes through the
181 generic netlink interface. Unlike BSD process accounting, the
182 statistics are available during the lifetime of tasks/processes as
183 responses to commands. Like BSD accounting, they are sent to user
188 config TASK_DELAY_ACCT
189 bool "Enable per-task delay accounting (EXPERIMENTAL)"
192 Collect information on time spent by a task waiting for system
193 resources like cpu, synchronous block I/O completion and swapping
194 in pages. Such statistics can help in setting a task's priorities
195 relative to other tasks for cpu, io, rss limits etc.
200 bool "Enable extended accounting over taskstats (EXPERIMENTAL)"
203 Collect extended task accounting data and send the data
204 to userland for processing over the taskstats interface.
208 config TASK_IO_ACCOUNTING
209 bool "Enable per-task storage I/O accounting (EXPERIMENTAL)"
210 depends on TASK_XACCT
212 Collect information on the number of bytes of storage I/O which this
218 bool "Auditing support"
221 Enable auditing infrastructure that can be used with another
222 kernel subsystem, such as SELinux (which requires this for
223 logging of avc messages output). Does not do system-call
224 auditing without CONFIG_AUDITSYSCALL.
227 bool "Enable system-call auditing support"
228 depends on AUDIT && (X86 || PPC || PPC64 || S390 || IA64 || UML || SPARC64|| SUPERH)
229 default y if SECURITY_SELINUX
231 Enable low-overhead system-call auditing infrastructure that
232 can be used independently or with another kernel subsystem,
233 such as SELinux. To use audit's filesystem watch feature, please
234 ensure that INOTIFY is configured.
238 depends on AUDITSYSCALL && INOTIFY
241 tristate "Kernel .config support"
243 This option enables the complete Linux kernel ".config" file
244 contents to be saved in the kernel. It provides documentation
245 of which kernel options are used in a running kernel or in an
246 on-disk kernel. This information can be extracted from the kernel
247 image file with the script scripts/extract-ikconfig and used as
248 input to rebuild the current kernel or to build another kernel.
249 It can also be extracted from a running kernel by reading
250 /proc/config.gz if enabled (below).
253 bool "Enable access to .config through /proc/config.gz"
254 depends on IKCONFIG && PROC_FS
256 This option enables access to the kernel configuration file
257 through /proc/config.gz.
260 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
262 default 17 if S390 || LOCKDEP
263 default 16 if X86_NUMAQ || IA64
267 Select kernel log buffer size as a power of 2.
268 Defaults and Examples:
269 17 => 128 KB for S/390
270 16 => 64 KB for x86 NUMAQ or IA-64
272 14 => 16 KB for uniprocessor
277 bool "Control Group support"
279 This option will let you use process cgroup subsystems
285 bool "Example debug cgroup subsystem"
288 This option enables a simple cgroup subsystem that
289 exports useful debugging information about the cgroups
295 bool "Namespace cgroup subsystem"
298 Provides a simple namespace cgroup subsystem to
299 provide hierarchical naming of sets of namespaces,
300 for instance virtual servers and checkpoint/restart
304 bool "Cpuset support"
305 depends on SMP && CGROUPS
307 This option will let you create and manage CPUSETs which
308 allow dynamically partitioning a system into sets of CPUs and
309 Memory Nodes and assigning tasks to run only within those sets.
310 This is primarily useful on large SMP or NUMA systems.
315 bool "Group CPU scheduler"
318 This feature lets CPU scheduler recognize task groups and control CPU
319 bandwidth allocation to such task groups.
321 config FAIR_GROUP_SCHED
322 bool "Group scheduling for SCHED_OTHER"
323 depends on GROUP_SCHED
326 config RT_GROUP_SCHED
327 bool "Group scheduling for SCHED_RR/FIFO"
328 depends on EXPERIMENTAL
329 depends on GROUP_SCHED
333 depends on GROUP_SCHED
334 prompt "Basis for grouping tasks"
340 This option will choose userid as the basis for grouping
341 tasks, thus providing equal CPU bandwidth to each user.
344 bool "Control groups"
347 This option allows you to create arbitrary task groups
348 using the "cgroup" pseudo filesystem and control
349 the cpu bandwidth allocated to each such task group.
350 Refer to Documentation/cgroups.txt for more information
351 on "cgroup" pseudo filesystem.
355 config CGROUP_CPUACCT
356 bool "Simple CPU accounting cgroup subsystem"
359 Provides a simple Resource Controller for monitoring the
360 total CPU consumed by the tasks in a cgroup
362 config RESOURCE_COUNTERS
363 bool "Resource counters"
365 This option enables controller independent resource accounting
366 infrastructure that works with cgroups
369 config SYSFS_DEPRECATED
370 bool "Create deprecated sysfs files"
374 This option creates deprecated symlinks such as the
375 "device"-link, the <subsystem>:<name>-link, and the
376 "bus"-link. It may also add deprecated key in the
378 None of these features or values should be used today, as
379 they export driver core implementation details to userspace
380 or export properties which can't be kept stable across kernel
383 If enabled, this option will also move any device structures
384 that belong to a class, back into the /sys/class hierarchy, in
385 order to support older versions of udev and some userspace
388 If you are using a distro with the most recent userspace
389 packages, it should be safe to say N here.
391 config CGROUP_MEM_CONT
392 bool "Memory controller for cgroups"
393 depends on CGROUPS && RESOURCE_COUNTERS
395 Provides a memory controller that manages both page cache and
398 Note that setting this option increases fixed memory overhead
399 associated with each page of memory in the system by 4/8 bytes
400 and also increases cache misses because struct page on many 64bit
401 systems will not fit into a single cache line anymore.
403 Only enable when you're ok with these trade offs and really
404 sure you need the memory controller.
406 config PROC_PID_CPUSET
407 bool "Include legacy /proc/<pid>/cpuset file"
412 bool "Kernel->user space relay support (formerly relayfs)"
414 This option enables support for relay interface support in
415 certain file systems (such as debugfs).
416 It is designed to provide an efficient mechanism for tools and
417 facilities to relay large amounts of data from kernel space to
423 bool "Namespaces support" if EMBEDDED
426 Provides the way to make tasks work with different objects using
427 the same id. For example same IPC id may refer to different objects
428 or same user id or pid may refer to different tasks when used in
429 different namespaces.
433 depends on NAMESPACES
435 In this namespace tasks see different info provided with the
440 depends on NAMESPACES && SYSVIPC
442 In this namespace tasks work with IPC ids which correspond to
443 different IPC objects in different namespaces
446 bool "User namespace (EXPERIMENTAL)"
447 depends on NAMESPACES && EXPERIMENTAL
449 This allows containers, i.e. vservers, to use user namespaces
450 to provide different user info for different servers.
454 bool "PID Namespaces (EXPERIMENTAL)"
456 depends on NAMESPACES && EXPERIMENTAL
458 Suport process id namespaces. This allows having multiple
459 process with the same pid as long as they are in different
460 pid namespaces. This is a building block of containers.
462 Unless you want to work with an experimental feature
465 config BLK_DEV_INITRD
466 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
467 depends on BROKEN || !FRV
469 The initial RAM filesystem is a ramfs which is loaded by the
470 boot loader (loadlin or lilo) and that is mounted as root
471 before the normal boot procedure. It is typically used to
472 load modules needed to mount the "real" root file system,
473 etc. See <file:Documentation/initrd.txt> for details.
475 If RAM disk support (BLK_DEV_RAM) is also included, this
476 also enables initial RAM disk (initrd) support and adds
477 15 Kbytes (more on some other architectures) to the kernel size.
487 config CC_OPTIMIZE_FOR_SIZE
488 bool "Optimize for size (Look out for broken compilers!)"
490 depends on ARM || H8300 || SUPERH || EXPERIMENTAL
492 Enabling this option will pass "-Os" instead of "-O2" to gcc
493 resulting in a smaller kernel.
495 WARNING: some versions of gcc may generate incorrect code with this
496 option. If problems are observed, a gcc upgrade may be needed.
504 bool "Configure standard kernel features (for small systems)"
506 This option allows certain base kernel options and settings
507 to be disabled or tweaked. This is for specialized
508 environments which can tolerate a "non-standard" kernel.
509 Only use this if you really know what you are doing.
512 bool "Enable 16-bit UID system calls" if EMBEDDED
513 depends on ARM || BLACKFIN || CRIS || FRV || H8300 || X86_32 || M68K || (S390 && !64BIT) || SUPERH || SPARC32 || (SPARC64 && SPARC32_COMPAT) || UML || (X86_64 && IA32_EMULATION)
516 This enables the legacy 16-bit UID syscall wrappers.
518 config SYSCTL_SYSCALL
519 bool "Sysctl syscall support" if EMBEDDED
523 sys_sysctl uses binary paths that have been found challenging
524 to properly maintain and use. The interface in /proc/sys
525 using paths with ascii names is now the primary path to this
528 Almost nothing using the binary sysctl interface so if you are
529 trying to save some space it is probably safe to disable this,
530 making your kernel marginally smaller.
532 If unsure say Y here.
535 bool "Load all symbols for debugging/ksymoops" if EMBEDDED
538 Say Y here to let the kernel print out symbolic crash information and
539 symbolic stack backtraces. This increases the size of the kernel
540 somewhat, as all symbols have to be loaded into the kernel image.
543 bool "Include all symbols in kallsyms"
544 depends on DEBUG_KERNEL && KALLSYMS
546 Normally kallsyms only contains the symbols of functions, for nicer
547 OOPS messages. Some debuggers can use kallsyms for other
548 symbols too: say Y here to include all symbols, if you need them
549 and you don't care about adding 300k to the size of your kernel.
553 config KALLSYMS_EXTRA_PASS
554 bool "Do an extra kallsyms pass"
557 If kallsyms is not working correctly, the build will fail with
558 inconsistent kallsyms data. If that occurs, log a bug report and
559 turn on KALLSYMS_EXTRA_PASS which should result in a stable build.
560 Always say N here unless you find a bug in kallsyms, which must be
561 reported. KALLSYMS_EXTRA_PASS is only a temporary workaround while
562 you wait for kallsyms to be fixed.
566 bool "Support for hot-pluggable devices" if EMBEDDED
569 This option is provided for the case where no hotplug or uevent
570 capabilities is wanted by the kernel. You should only consider
571 disabling this option for embedded systems that do not use modules, a
572 dynamic /dev tree, or dynamic device discovery. Just say Y.
576 bool "Enable support for printk" if EMBEDDED
578 This option enables normal printk support. Removing it
579 eliminates most of the message strings from the kernel image
580 and makes the kernel more or less silent. As this makes it
581 very difficult to diagnose system problems, saying N here is
582 strongly discouraged.
585 bool "BUG() support" if EMBEDDED
588 Disabling this option eliminates support for BUG and WARN, reducing
589 the size of your kernel image and potentially quietly ignoring
590 numerous fatal conditions. You should only consider disabling this
591 option for embedded systems with no facilities for reporting errors.
596 bool "Enable ELF core dumps" if EMBEDDED
598 Enable support for generating core dumps. Disabling saves about 4k.
601 bool "Disable heap randomization"
604 Randomizing heap placement makes heap exploits harder, but it
605 also breaks ancient binaries (including anything libc5 based).
606 This option changes the bootup default to heap randomization
607 disabled, and can be overriden runtime by setting
608 /proc/sys/kernel/randomize_va_space to 2.
610 On non-ancient distros (post-2000 ones) N is usually a safe choice.
614 bool "Enable full-sized data structures for core" if EMBEDDED
616 Disabling this option reduces the size of miscellaneous core
617 kernel data structures. This saves memory on small machines,
618 but may reduce performance.
621 bool "Enable futex support" if EMBEDDED
625 Disabling this option will cause the kernel to be built without
626 support for "fast userspace mutexes". The resulting kernel may not
627 run glibc-based applications correctly.
633 bool "Enable eventpoll support" if EMBEDDED
637 Disabling this option will cause the kernel to be built without
638 support for epoll family of system calls.
641 bool "Enable signalfd() system call" if EMBEDDED
645 Enable the signalfd() system call that allows to receive signals
646 on a file descriptor.
651 bool "Enable timerfd() system call" if EMBEDDED
655 Enable the timerfd() system call that allows to receive timer
656 events on a file descriptor.
661 bool "Enable eventfd() system call" if EMBEDDED
665 Enable the eventfd() system call that allows to receive both
666 kernel notification (ie. KAIO) or userspace notifications.
671 bool "Use full shmem filesystem" if EMBEDDED
675 The shmem is an internal filesystem used to manage shared memory.
676 It is backed by swap and manages resource limits. It is also exported
677 to userspace as tmpfs if TMPFS is enabled. Disabling this
678 option replaces shmem and tmpfs with the much simpler ramfs code,
679 which may be appropriate on small systems without swap.
681 config VM_EVENT_COUNTERS
683 bool "Enable VM event counters for /proc/vmstat" if EMBEDDED
685 VM event counters are needed for event counts to be shown.
686 This option allows the disabling of the VM event counters
687 on EMBEDDED systems. /proc/vmstat will only show page counts
688 if VM event counters are disabled.
692 bool "Enable SLUB debugging support" if EMBEDDED
695 SLUB has extensive debug support features. Disabling these can
696 result in significant savings in code size. This also disables
697 SLUB sysfs support. /sys/slab will not exist and there will be
698 no support for cache validation etc.
701 prompt "Choose SLAB allocator"
704 This option allows to select a slab allocator.
709 The regular slab allocator that is established and known to work
710 well in all environments. It organizes cache hot objects in
711 per cpu and per node queues. SLAB is the default choice for
715 bool "SLUB (Unqueued Allocator)"
717 SLUB is a slab allocator that minimizes cache line usage
718 instead of managing queues of cached objects (SLAB approach).
719 Per cpu caching is realized using slabs of objects instead
720 of queues of objects. SLUB can use memory efficiently
721 and has enhanced diagnostics.
725 bool "SLOB (Simple Allocator)"
727 SLOB replaces the stock allocator with a drastically simpler
728 allocator. SLOB is generally more space efficient but
729 does not perform as well on large systems.
734 bool "Profiling support (EXPERIMENTAL)"
736 Say Y here to enable the extended profiling support mechanisms used
737 by profilers such as OProfile.
740 bool "Activate markers"
742 Place an empty function call at each marker site. Can be
743 dynamically changed for a probe function.
745 source "arch/Kconfig"
747 config PROC_PAGE_MONITOR
749 depends on PROC_FS && MMU
750 bool "Enable /proc page monitoring" if EMBEDDED
752 Various /proc files exist to monitor process memory utilization:
753 /proc/pid/smaps, /proc/pid/clear_refs, /proc/pid/pagemap,
754 /proc/kpagecount, and /proc/kpageflags. Disabling these
755 interfaces will reduce the size of the kernel by approximately 4kb.
757 endmenu # General setup
762 depends on SLAB || SLUB
775 default 0 if BASE_FULL
776 default 1 if !BASE_FULL
779 bool "Enable loadable module support"
781 Kernel modules are small pieces of compiled code which can
782 be inserted in the running kernel, rather than being
783 permanently built into the kernel. You use the "modprobe"
784 tool to add (and sometimes remove) them. If you say Y here,
785 many parts of the kernel can be built as modules (by
786 answering M instead of Y where indicated): this is most
787 useful for infrequently used options which are not required
788 for booting. For more information, see the man pages for
789 modprobe, lsmod, modinfo, insmod and rmmod.
791 If you say Y here, you will need to run "make
792 modules_install" to put the modules under /lib/modules/
793 where modprobe can find them (you may need to be root to do
799 bool "Module unloading"
802 Without this option you will not be able to unload any
803 modules (note that some modules may not be unloadable
804 anyway), which makes your kernel slightly smaller and
805 simpler. If unsure, say Y.
807 config MODULE_FORCE_UNLOAD
808 bool "Forced module unloading"
809 depends on MODULE_UNLOAD && EXPERIMENTAL
811 This option allows you to force a module to unload, even if the
812 kernel believes it is unsafe: the kernel will remove the module
813 without waiting for anyone to stop using it (using the -f option to
814 rmmod). This is mainly for kernel developers and desperate users.
818 bool "Module versioning support"
821 Usually, you have to use modules compiled with your kernel.
822 Saying Y here makes it sometimes possible to use modules
823 compiled for different kernels, by adding enough information
824 to the modules to (hopefully) spot any changes which would
825 make them incompatible with the kernel you are running. If
828 config MODULE_SRCVERSION_ALL
829 bool "Source checksum for all modules"
832 Modules which contain a MODULE_VERSION get an extra "srcversion"
833 field inserted into their modinfo section, which contains a
834 sum of the source files which made it. This helps maintainers
835 see exactly which source was used to build a module (since
836 others sometimes change the module source without updating
837 the version). With this option, such a "srcversion" field
838 will be created for all modules. If unsure, say N.
841 bool "Automatic kernel module loading"
844 Normally when you have selected some parts of the kernel to
845 be created as kernel modules, you must load them (using the
846 "modprobe" command) before you can use them. If you say Y
847 here, some parts of the kernel will be able to load modules
848 automatically: when a part of the kernel needs a module, it
849 runs modprobe with the appropriate arguments, thereby
850 loading the module if it is available. If unsure, say Y.
855 depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
857 Need stop_machine() primitive.
859 source "block/Kconfig"
861 config PREEMPT_NOTIFIERS
865 prompt "RCU implementation type:"
868 This allows you to choose either the classic RCU implementation
869 that is designed for best read-side performance on non-realtime
870 systems, or the preemptible RCU implementation for best latency
871 on realtime systems. Note that some kernel preemption modes
872 will restrict your choice.
874 Select the default if you are unsure.
879 This option selects the classic RCU implementation that is
880 designed for best read-side performance on non-realtime
883 Say Y if you are unsure.
886 bool "Preemptible RCU"
889 This option reduces the latency of the kernel by making certain
890 RCU sections preemptible. Normally RCU code is non-preemptible, if
891 this option is selected then read-only RCU sections become
892 preemptible. This helps latency, but may expose bugs due to
893 now-naive assumptions about each RCU read-side critical section
894 remaining on a given CPU through its execution.
896 Say N if you are unsure.