5 default "/lib/modules/$UNAME_RELEASE/.config"
6 default "/etc/kernel-config"
7 default "/boot/config-$UNAME_RELEASE"
8 default "arch/$ARCH/defconfig"
13 bool "Prompt for development and/or incomplete code/drivers"
15 Some of the various things that Linux supports (such as network
16 drivers, file systems, network protocols, etc.) can be in a state
17 of development where the functionality, stability, or the level of
18 testing is not yet high enough for general use. This is usually
19 known as the "alpha-test" phase among developers. If a feature is
20 currently in alpha-test, then the developers usually discourage
21 uninformed widespread use of this feature by the general public to
22 avoid "Why doesn't this work?" type mail messages. However, active
23 testing and use of these systems is welcomed. Just be aware that it
24 may not meet the normal level of reliability or it may fail to work
25 in some special cases. Detailed bug reports from people familiar
26 with the kernel internals are usually welcomed by the developers
27 (before submitting bug reports, please read the documents
28 <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
29 <file:Documentation/BUG-HUNTING>, and
30 <file:Documentation/oops-tracing.txt> in the kernel source).
32 This option will also make obsoleted drivers available. These are
33 drivers that have been replaced by something else, and/or are
34 scheduled to be removed in a future kernel release.
36 Unless you intend to help test and develop a feature or driver that
37 falls into this category, or you have a situation that requires
38 using these features, you should probably say N here, which will
39 cause the configurator to present you with fewer choices. If
40 you say Y here, you will be offered the choice of using features or
41 drivers that are currently considered to be in the alpha-test phase.
48 depends on BROKEN || !SMP
53 depends on SMP || PREEMPT
56 config INIT_ENV_ARG_LIMIT
61 Maximum of each of the number of arguments and environment
62 variables passed to init from the kernel command line.
66 string "Local version - append to kernel release"
68 Append an extra string to the end of your kernel version.
69 This will show up when you type uname, for example.
70 The string you set here will be appended after the contents of
71 any files with a filename matching localversion* in your
72 object and source tree, in that order. Your total string can
73 be a maximum of 64 characters.
75 config LOCALVERSION_AUTO
76 bool "Automatically append version information to the version string"
79 This will try to automatically determine if the current tree is a
80 release tree by looking for git tags that belong to the current
83 A string of the format -gxxxxxxxx will be added to the localversion
84 if a git-based tree is found. The string generated by this will be
85 appended after any matching localversion* files, and after the value
86 set in CONFIG_LOCALVERSION.
88 (The actual string used here is the first eight characters produced
89 by running the command:
91 $ git rev-parse --verify HEAD
93 which is done within the script "scripts/setlocalversion".)
96 bool "Support for paging of anonymous memory (swap)"
97 depends on MMU && BLOCK
100 This option allows you to choose whether you want to have support
101 for so called swap devices or swap files in your kernel that are
102 used to provide more virtual memory than the actual RAM present
103 in your computer. If unsure say Y.
108 Inter Process Communication is a suite of library functions and
109 system calls which let processes (running programs) synchronize and
110 exchange information. It is generally considered to be a good thing,
111 and some programs won't run unless you say Y here. In particular, if
112 you want to run the DOS emulator dosemu under Linux (read the
113 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
114 you'll need to say Y here.
116 You can find documentation about IPC with "info ipc" and also in
117 section 6.4 of the Linux Programmer's Guide, available from
118 <http://www.tldp.org/guides.html>.
120 config SYSVIPC_SYSCTL
127 bool "POSIX Message Queues"
128 depends on NET && EXPERIMENTAL
130 POSIX variant of message queues is a part of IPC. In POSIX message
131 queues every message has a priority which decides about succession
132 of receiving it by a process. If you want to compile and run
133 programs written e.g. for Solaris with use of its POSIX message
134 queues (functions mq_*) say Y here.
136 POSIX message queues are visible as a filesystem called 'mqueue'
137 and can be mounted somewhere if you want to do filesystem
138 operations on message queues.
142 config BSD_PROCESS_ACCT
143 bool "BSD Process Accounting"
145 If you say Y here, a user level program will be able to instruct the
146 kernel (via a special system call) to write process accounting
147 information to a file: whenever a process exits, information about
148 that process will be appended to the file by the kernel. The
149 information includes things such as creation time, owning user,
150 command name, memory usage, controlling terminal etc. (the complete
151 list is in the struct acct in <file:include/linux/acct.h>). It is
152 up to the user level program to do useful things with this
153 information. This is generally a good idea, so say Y.
155 config BSD_PROCESS_ACCT_V3
156 bool "BSD Process Accounting version 3 file format"
157 depends on BSD_PROCESS_ACCT
160 If you say Y here, the process accounting information is written
161 in a new file format that also logs the process IDs of each
162 process and it's parent. Note that this file format is incompatible
163 with previous v0/v1/v2 file formats, so you will need updated tools
164 for processing it. A preliminary version of these tools is available
165 at <http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/>.
168 bool "Export task/process statistics through netlink (EXPERIMENTAL)"
172 Export selected statistics for tasks/processes through the
173 generic netlink interface. Unlike BSD process accounting, the
174 statistics are available during the lifetime of tasks/processes as
175 responses to commands. Like BSD accounting, they are sent to user
180 config TASK_DELAY_ACCT
181 bool "Enable per-task delay accounting (EXPERIMENTAL)"
184 Collect information on time spent by a task waiting for system
185 resources like cpu, synchronous block I/O completion and swapping
186 in pages. Such statistics can help in setting a task's priorities
187 relative to other tasks for cpu, io, rss limits etc.
192 bool "Enable extended accounting over taskstats (EXPERIMENTAL)"
195 Collect extended task accounting data and send the data
196 to userland for processing over the taskstats interface.
200 config TASK_IO_ACCOUNTING
201 bool "Enable per-task storage I/O accounting (EXPERIMENTAL)"
202 depends on TASK_XACCT
204 Collect information on the number of bytes of storage I/O which this
210 bool "User Namespaces (EXPERIMENTAL)"
212 depends on EXPERIMENTAL
214 Support user namespaces. This allows containers, i.e.
215 vservers, to use user namespaces to provide different
216 user info for different servers. If unsure, say N.
219 bool "PID Namespaces (EXPERIMENTAL)"
221 depends on EXPERIMENTAL
223 Suport process id namespaces. This allows having multiple
224 process with the same pid as long as they are in different
225 pid namespaces. This is a building block of containers.
227 Unless you want to work with an experimental feature
231 bool "Auditing support"
234 Enable auditing infrastructure that can be used with another
235 kernel subsystem, such as SELinux (which requires this for
236 logging of avc messages output). Does not do system-call
237 auditing without CONFIG_AUDITSYSCALL.
240 bool "Enable system-call auditing support"
241 depends on AUDIT && (X86 || PPC || PPC64 || S390 || IA64 || UML || SPARC64|| SUPERH)
242 default y if SECURITY_SELINUX
244 Enable low-overhead system-call auditing infrastructure that
245 can be used independently or with another kernel subsystem,
246 such as SELinux. To use audit's filesystem watch feature, please
247 ensure that INOTIFY is configured.
251 depends on AUDITSYSCALL && INOTIFY
254 tristate "Kernel .config support"
256 This option enables the complete Linux kernel ".config" file
257 contents to be saved in the kernel. It provides documentation
258 of which kernel options are used in a running kernel or in an
259 on-disk kernel. This information can be extracted from the kernel
260 image file with the script scripts/extract-ikconfig and used as
261 input to rebuild the current kernel or to build another kernel.
262 It can also be extracted from a running kernel by reading
263 /proc/config.gz if enabled (below).
266 bool "Enable access to .config through /proc/config.gz"
267 depends on IKCONFIG && PROC_FS
269 This option enables access to the kernel configuration file
270 through /proc/config.gz.
273 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
275 default 17 if S390 || LOCKDEP
276 default 16 if X86_NUMAQ || IA64
280 Select kernel log buffer size as a power of 2.
281 Defaults and Examples:
282 17 => 128 KB for S/390
283 16 => 64 KB for x86 NUMAQ or IA-64
285 14 => 16 KB for uniprocessor
290 bool "Control Group support"
292 This option will let you use process cgroup subsystems
298 bool "Example debug cgroup subsystem"
301 This option enables a simple cgroup subsystem that
302 exports useful debugging information about the cgroups
308 bool "Namespace cgroup subsystem"
311 Provides a simple namespace cgroup subsystem to
312 provide hierarchical naming of sets of namespaces,
313 for instance virtual servers and checkpoint/restart
317 bool "Cpuset support"
318 depends on SMP && CGROUPS
320 This option will let you create and manage CPUSETs which
321 allow dynamically partitioning a system into sets of CPUs and
322 Memory Nodes and assigning tasks to run only within those sets.
323 This is primarily useful on large SMP or NUMA systems.
327 config FAIR_GROUP_SCHED
328 bool "Fair group CPU scheduler"
331 This feature lets CPU scheduler recognize task groups and control CPU
332 bandwidth allocation to such task groups.
335 depends on FAIR_GROUP_SCHED
336 prompt "Basis for grouping tasks"
337 default FAIR_USER_SCHED
339 config FAIR_USER_SCHED
342 This option will choose userid as the basis for grouping
343 tasks, thus providing equal CPU bandwidth to each user.
345 config FAIR_CGROUP_SCHED
346 bool "Control groups"
349 This option allows you to create arbitrary task groups
350 using the "cgroup" pseudo filesystem and control
351 the cpu bandwidth allocated to each such task group.
352 Refer to Documentation/cgroups.txt for more information
353 on "cgroup" pseudo filesystem.
357 config RESOURCE_COUNTERS
358 bool "Resource counters"
360 This option enables controller independent resource accounting
361 infrastructure that works with cgroups
364 config SYSFS_DEPRECATED
365 bool "Create deprecated sysfs files"
368 This option creates deprecated symlinks such as the
369 "device"-link, the <subsystem>:<name>-link, and the
370 "bus"-link. It may also add deprecated key in the
372 None of these features or values should be used today, as
373 they export driver core implementation details to userspace
374 or export properties which can't be kept stable across kernel
377 If enabled, this option will also move any device structures
378 that belong to a class, back into the /sys/class hierarchy, in
379 order to support older versions of udev.
381 If you are using a distro that was released in 2006 or later,
382 it should be safe to say N here.
384 config CGROUP_MEM_CONT
385 bool "Memory controller for cgroups"
386 depends on CGROUPS && RESOURCE_COUNTERS
388 Provides a memory controller that manages both page cache and
391 config PROC_PID_CPUSET
392 bool "Include legacy /proc/<pid>/cpuset file"
397 bool "Kernel->user space relay support (formerly relayfs)"
399 This option enables support for relay interface support in
400 certain file systems (such as debugfs).
401 It is designed to provide an efficient mechanism for tools and
402 facilities to relay large amounts of data from kernel space to
407 config BLK_DEV_INITRD
408 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
409 depends on BROKEN || !FRV
411 The initial RAM filesystem is a ramfs which is loaded by the
412 boot loader (loadlin or lilo) and that is mounted as root
413 before the normal boot procedure. It is typically used to
414 load modules needed to mount the "real" root file system,
415 etc. See <file:Documentation/initrd.txt> for details.
417 If RAM disk support (BLK_DEV_RAM) is also included, this
418 also enables initial RAM disk (initrd) support and adds
419 15 Kbytes (more on some other architectures) to the kernel size.
429 config CC_OPTIMIZE_FOR_SIZE
430 bool "Optimize for size (Look out for broken compilers!)"
432 depends on ARM || H8300 || SUPERH || EXPERIMENTAL
434 Enabling this option will pass "-Os" instead of "-O2" to gcc
435 resulting in a smaller kernel.
437 WARNING: some versions of gcc may generate incorrect code with this
438 option. If problems are observed, a gcc upgrade may be needed.
446 bool "Configure standard kernel features (for small systems)"
448 This option allows certain base kernel options and settings
449 to be disabled or tweaked. This is for specialized
450 environments which can tolerate a "non-standard" kernel.
451 Only use this if you really know what you are doing.
454 bool "Enable 16-bit UID system calls" if EMBEDDED
455 depends on ARM || BFIN || CRIS || FRV || H8300 || X86_32 || M68K || (S390 && !64BIT) || SUPERH || SPARC32 || (SPARC64 && SPARC32_COMPAT) || UML || (X86_64 && IA32_EMULATION)
458 This enables the legacy 16-bit UID syscall wrappers.
460 config SYSCTL_SYSCALL
461 bool "Sysctl syscall support" if EMBEDDED
465 sys_sysctl uses binary paths that have been found challenging
466 to properly maintain and use. The interface in /proc/sys
467 using paths with ascii names is now the primary path to this
470 Almost nothing using the binary sysctl interface so if you are
471 trying to save some space it is probably safe to disable this,
472 making your kernel marginally smaller.
474 If unsure say Y here.
477 bool "Load all symbols for debugging/ksymoops" if EMBEDDED
480 Say Y here to let the kernel print out symbolic crash information and
481 symbolic stack backtraces. This increases the size of the kernel
482 somewhat, as all symbols have to be loaded into the kernel image.
485 bool "Include all symbols in kallsyms"
486 depends on DEBUG_KERNEL && KALLSYMS
488 Normally kallsyms only contains the symbols of functions, for nicer
489 OOPS messages. Some debuggers can use kallsyms for other
490 symbols too: say Y here to include all symbols, if you need them
491 and you don't care about adding 300k to the size of your kernel.
495 config KALLSYMS_EXTRA_PASS
496 bool "Do an extra kallsyms pass"
499 If kallsyms is not working correctly, the build will fail with
500 inconsistent kallsyms data. If that occurs, log a bug report and
501 turn on KALLSYMS_EXTRA_PASS which should result in a stable build.
502 Always say N here unless you find a bug in kallsyms, which must be
503 reported. KALLSYMS_EXTRA_PASS is only a temporary workaround while
504 you wait for kallsyms to be fixed.
508 bool "Support for hot-pluggable devices" if EMBEDDED
511 This option is provided for the case where no hotplug or uevent
512 capabilities is wanted by the kernel. You should only consider
513 disabling this option for embedded systems that do not use modules, a
514 dynamic /dev tree, or dynamic device discovery. Just say Y.
518 bool "Enable support for printk" if EMBEDDED
520 This option enables normal printk support. Removing it
521 eliminates most of the message strings from the kernel image
522 and makes the kernel more or less silent. As this makes it
523 very difficult to diagnose system problems, saying N here is
524 strongly discouraged.
527 bool "BUG() support" if EMBEDDED
530 Disabling this option eliminates support for BUG and WARN, reducing
531 the size of your kernel image and potentially quietly ignoring
532 numerous fatal conditions. You should only consider disabling this
533 option for embedded systems with no facilities for reporting errors.
538 bool "Enable ELF core dumps" if EMBEDDED
540 Enable support for generating core dumps. Disabling saves about 4k.
544 bool "Enable full-sized data structures for core" if EMBEDDED
546 Disabling this option reduces the size of miscellaneous core
547 kernel data structures. This saves memory on small machines,
548 but may reduce performance.
551 bool "Enable futex support" if EMBEDDED
555 Disabling this option will cause the kernel to be built without
556 support for "fast userspace mutexes". The resulting kernel may not
557 run glibc-based applications correctly.
563 bool "Enable eventpoll support" if EMBEDDED
567 Disabling this option will cause the kernel to be built without
568 support for epoll family of system calls.
571 bool "Enable signalfd() system call" if EMBEDDED
575 Enable the signalfd() system call that allows to receive signals
576 on a file descriptor.
581 bool "Enable timerfd() system call" if EMBEDDED
586 Enable the timerfd() system call that allows to receive timer
587 events on a file descriptor.
592 bool "Enable eventfd() system call" if EMBEDDED
596 Enable the eventfd() system call that allows to receive both
597 kernel notification (ie. KAIO) or userspace notifications.
602 bool "Use full shmem filesystem" if EMBEDDED
606 The shmem is an internal filesystem used to manage shared memory.
607 It is backed by swap and manages resource limits. It is also exported
608 to userspace as tmpfs if TMPFS is enabled. Disabling this
609 option replaces shmem and tmpfs with the much simpler ramfs code,
610 which may be appropriate on small systems without swap.
612 config VM_EVENT_COUNTERS
614 bool "Enable VM event counters for /proc/vmstat" if EMBEDDED
616 VM event counters are needed for event counts to be shown.
617 This option allows the disabling of the VM event counters
618 on EMBEDDED systems. /proc/vmstat will only show page counts
619 if VM event counters are disabled.
623 bool "Enable SLUB debugging support" if EMBEDDED
626 SLUB has extensive debug support features. Disabling these can
627 result in significant savings in code size. This also disables
628 SLUB sysfs support. /sys/slab will not exist and there will be
629 no support for cache validation etc.
632 prompt "Choose SLAB allocator"
635 This option allows to select a slab allocator.
640 The regular slab allocator that is established and known to work
641 well in all environments. It organizes cache hot objects in
642 per cpu and per node queues. SLAB is the default choice for
646 bool "SLUB (Unqueued Allocator)"
648 SLUB is a slab allocator that minimizes cache line usage
649 instead of managing queues of cached objects (SLAB approach).
650 Per cpu caching is realized using slabs of objects instead
651 of queues of objects. SLUB can use memory efficiently
652 and has enhanced diagnostics.
656 bool "SLOB (Simple Allocator)"
658 SLOB replaces the SLAB allocator with a drastically simpler
659 allocator. SLOB is more space efficient than SLAB but does not
660 scale well (single lock for all operations) and is also highly
661 susceptible to fragmentation. SLUB can accomplish a higher object
662 density. It is usually better to use SLUB instead of SLOB.
666 config PROC_PAGE_MONITOR
668 depends on PROC_FS && MMU
669 bool "Enable /proc page monitoring" if EMBEDDED
671 Various /proc files exist to monitor process memory utilization:
672 /proc/pid/smaps, /proc/pid/clear_refs, /proc/pid/pagemap,
673 /proc/kpagecount, and /proc/kpageflags. Disabling these
674 interfaces will reduce the size of the kernel by approximately 4kb.
676 endmenu # General setup
688 default 0 if BASE_FULL
689 default 1 if !BASE_FULL
692 bool "Enable loadable module support"
694 Kernel modules are small pieces of compiled code which can
695 be inserted in the running kernel, rather than being
696 permanently built into the kernel. You use the "modprobe"
697 tool to add (and sometimes remove) them. If you say Y here,
698 many parts of the kernel can be built as modules (by
699 answering M instead of Y where indicated): this is most
700 useful for infrequently used options which are not required
701 for booting. For more information, see the man pages for
702 modprobe, lsmod, modinfo, insmod and rmmod.
704 If you say Y here, you will need to run "make
705 modules_install" to put the modules under /lib/modules/
706 where modprobe can find them (you may need to be root to do
712 bool "Module unloading"
715 Without this option you will not be able to unload any
716 modules (note that some modules may not be unloadable
717 anyway), which makes your kernel slightly smaller and
718 simpler. If unsure, say Y.
720 config MODULE_FORCE_UNLOAD
721 bool "Forced module unloading"
722 depends on MODULE_UNLOAD && EXPERIMENTAL
724 This option allows you to force a module to unload, even if the
725 kernel believes it is unsafe: the kernel will remove the module
726 without waiting for anyone to stop using it (using the -f option to
727 rmmod). This is mainly for kernel developers and desperate users.
731 bool "Module versioning support"
734 Usually, you have to use modules compiled with your kernel.
735 Saying Y here makes it sometimes possible to use modules
736 compiled for different kernels, by adding enough information
737 to the modules to (hopefully) spot any changes which would
738 make them incompatible with the kernel you are running. If
741 config MODULE_SRCVERSION_ALL
742 bool "Source checksum for all modules"
745 Modules which contain a MODULE_VERSION get an extra "srcversion"
746 field inserted into their modinfo section, which contains a
747 sum of the source files which made it. This helps maintainers
748 see exactly which source was used to build a module (since
749 others sometimes change the module source without updating
750 the version). With this option, such a "srcversion" field
751 will be created for all modules. If unsure, say N.
754 bool "Automatic kernel module loading"
757 Normally when you have selected some parts of the kernel to
758 be created as kernel modules, you must load them (using the
759 "modprobe" command) before you can use them. If you say Y
760 here, some parts of the kernel will be able to load modules
761 automatically: when a part of the kernel needs a module, it
762 runs modprobe with the appropriate arguments, thereby
763 loading the module if it is available. If unsure, say Y.
768 depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
770 Need stop_machine() primitive.
772 source "block/Kconfig"
774 config PREEMPT_NOTIFIERS