5 default "/lib/modules/$UNAME_RELEASE/.config"
6 default "/etc/kernel-config"
7 default "/boot/config-$UNAME_RELEASE"
8 default "arch/$ARCH/defconfig"
10 menu "Code maturity level options"
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.
69 string "Local version - append to kernel release"
71 Append an extra string to the end of your kernel version.
72 This will show up when you type uname, for example.
73 The string you set here will be appended after the contents of
74 any files with a filename matching localversion* in your
75 object and source tree, in that order. Your total string can
76 be a maximum of 64 characters.
78 config LOCALVERSION_AUTO
79 bool "Automatically append version information to the version string"
82 This will try to automatically determine if the current tree is a
83 release tree by looking for git tags that belong to the current
86 A string of the format -gxxxxxxxx will be added to the localversion
87 if a git-based tree is found. The string generated by this will be
88 appended after any matching localversion* files, and after the value
89 set in CONFIG_LOCALVERSION.
91 (The actual string used here is the first eight characters produced
92 by running the command:
94 $ git rev-parse --verify HEAD
96 which is done within the script "scripts/setlocalversion".)
99 bool "Support for paging of anonymous memory (swap)"
100 depends on MMU && BLOCK
103 This option allows you to choose whether you want to have support
104 for so called swap devices or swap files in your kernel that are
105 used to provide more virtual memory than the actual RAM present
106 in your computer. If unsure say Y.
111 Inter Process Communication is a suite of library functions and
112 system calls which let processes (running programs) synchronize and
113 exchange information. It is generally considered to be a good thing,
114 and some programs won't run unless you say Y here. In particular, if
115 you want to run the DOS emulator dosemu under Linux (read the
116 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
117 you'll need to say Y here.
119 You can find documentation about IPC with "info ipc" and also in
120 section 6.4 of the Linux Programmer's Guide, available from
121 <http://www.tldp.org/guides.html>.
123 config SYSVIPC_SYSCTL
130 bool "POSIX Message Queues"
131 depends on NET && EXPERIMENTAL
133 POSIX variant of message queues is a part of IPC. In POSIX message
134 queues every message has a priority which decides about succession
135 of receiving it by a process. If you want to compile and run
136 programs written e.g. for Solaris with use of its POSIX message
137 queues (functions mq_*) say Y here.
139 POSIX message queues are visible as a filesystem called 'mqueue'
140 and can be mounted somewhere if you want to do filesystem
141 operations on message queues.
145 config BSD_PROCESS_ACCT
146 bool "BSD Process Accounting"
148 If you say Y here, a user level program will be able to instruct the
149 kernel (via a special system call) to write process accounting
150 information to a file: whenever a process exits, information about
151 that process will be appended to the file by the kernel. The
152 information includes things such as creation time, owning user,
153 command name, memory usage, controlling terminal etc. (the complete
154 list is in the struct acct in <file:include/linux/acct.h>). It is
155 up to the user level program to do useful things with this
156 information. This is generally a good idea, so say Y.
158 config BSD_PROCESS_ACCT_V3
159 bool "BSD Process Accounting version 3 file format"
160 depends on BSD_PROCESS_ACCT
163 If you say Y here, the process accounting information is written
164 in a new file format that also logs the process IDs of each
165 process and it's parent. Note that this file format is incompatible
166 with previous v0/v1/v2 file formats, so you will need updated tools
167 for processing it. A preliminary version of these tools is available
168 at <http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/>.
171 bool "Export task/process statistics through netlink (EXPERIMENTAL)"
175 Export selected statistics for tasks/processes through the
176 generic netlink interface. Unlike BSD process accounting, the
177 statistics are available during the lifetime of tasks/processes as
178 responses to commands. Like BSD accounting, they are sent to user
183 config TASK_DELAY_ACCT
184 bool "Enable per-task delay accounting (EXPERIMENTAL)"
187 Collect information on time spent by a task waiting for system
188 resources like cpu, synchronous block I/O completion and swapping
189 in pages. Such statistics can help in setting a task's priorities
190 relative to other tasks for cpu, io, rss limits etc.
195 bool "Enable extended accounting over taskstats (EXPERIMENTAL)"
198 Collect extended task accounting data and send the data
199 to userland for processing over the taskstats interface.
203 config TASK_IO_ACCOUNTING
204 bool "Enable per-task storage I/O accounting (EXPERIMENTAL)"
205 depends on TASK_XACCT
207 Collect information on the number of bytes of storage I/O which this
213 bool "Auditing support"
216 Enable auditing infrastructure that can be used with another
217 kernel subsystem, such as SELinux (which requires this for
218 logging of avc messages output). Does not do system-call
219 auditing without CONFIG_AUDITSYSCALL.
222 bool "Enable system-call auditing support"
223 depends on AUDIT && (X86 || PPC || PPC64 || S390 || IA64 || UML || SPARC64)
224 default y if SECURITY_SELINUX
226 Enable low-overhead system-call auditing infrastructure that
227 can be used independently or with another kernel subsystem,
228 such as SELinux. To use audit's filesystem watch feature, please
229 ensure that INOTIFY is configured.
232 tristate "Kernel .config support"
234 This option enables the complete Linux kernel ".config" file
235 contents to be saved in the kernel. It provides documentation
236 of which kernel options are used in a running kernel or in an
237 on-disk kernel. This information can be extracted from the kernel
238 image file with the script scripts/extract-ikconfig and used as
239 input to rebuild the current kernel or to build another kernel.
240 It can also be extracted from a running kernel by reading
241 /proc/config.gz if enabled (below).
244 bool "Enable access to .config through /proc/config.gz"
245 depends on IKCONFIG && PROC_FS
247 This option enables access to the kernel configuration file
248 through /proc/config.gz.
251 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
253 default 17 if S390 || LOCKDEP
254 default 16 if X86_NUMAQ || IA64
258 Select kernel log buffer size as a power of 2.
259 Defaults and Examples:
260 17 => 128 KB for S/390
261 16 => 64 KB for x86 NUMAQ or IA-64
263 14 => 16 KB for uniprocessor
268 bool "Cpuset support"
271 This option will let you create and manage CPUSETs which
272 allow dynamically partitioning a system into sets of CPUs and
273 Memory Nodes and assigning tasks to run only within those sets.
274 This is primarily useful on large SMP or NUMA systems.
278 config SYSFS_DEPRECATED
279 bool "Create deprecated sysfs files"
282 This option creates deprecated symlinks such as the
283 "device"-link, the <subsystem>:<name>-link, and the
284 "bus"-link. It may also add deprecated key in the
286 None of these features or values should be used today, as
287 they export driver core implementation details to userspace
288 or export properties which can't be kept stable across kernel
291 If enabled, this option will also move any device structures
292 that belong to a class, back into the /sys/class hierarchy, in
293 order to support older versions of udev.
295 If you are using a distro that was released in 2006 or later,
296 it should be safe to say N here.
299 bool "Kernel->user space relay support (formerly relayfs)"
301 This option enables support for relay interface support in
302 certain file systems (such as debugfs).
303 It is designed to provide an efficient mechanism for tools and
304 facilities to relay large amounts of data from kernel space to
309 config BLK_DEV_INITRD
310 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
311 depends on BROKEN || !FRV
313 The initial RAM filesystem is a ramfs which is loaded by the
314 boot loader (loadlin or lilo) and that is mounted as root
315 before the normal boot procedure. It is typically used to
316 load modules needed to mount the "real" root file system,
317 etc. See <file:Documentation/initrd.txt> for details.
319 If RAM disk support (BLK_DEV_RAM) is also included, this
320 also enables initial RAM disk (initrd) support and adds
321 15 Kbytes (more on some other architectures) to the kernel size.
331 config CC_OPTIMIZE_FOR_SIZE
332 bool "Optimize for size (Look out for broken compilers!)"
334 depends on ARM || H8300 || EXPERIMENTAL
336 Enabling this option will pass "-Os" instead of "-O2" to gcc
337 resulting in a smaller kernel.
339 WARNING: some versions of gcc may generate incorrect code with this
340 option. If problems are observed, a gcc upgrade may be needed.
348 bool "Configure standard kernel features (for small systems)"
350 This option allows certain base kernel options and settings
351 to be disabled or tweaked. This is for specialized
352 environments which can tolerate a "non-standard" kernel.
353 Only use this if you really know what you are doing.
356 bool "Enable 16-bit UID system calls" if EMBEDDED
357 depends on ARM || BFIN || CRIS || FRV || H8300 || X86_32 || M68K || (S390 && !64BIT) || SUPERH || SPARC32 || (SPARC64 && SPARC32_COMPAT) || UML || (X86_64 && IA32_EMULATION)
360 This enables the legacy 16-bit UID syscall wrappers.
362 config SYSCTL_SYSCALL
363 bool "Sysctl syscall support" if EMBEDDED
367 sys_sysctl uses binary paths that have been found challenging
368 to properly maintain and use. The interface in /proc/sys
369 using paths with ascii names is now the primary path to this
372 Almost nothing using the binary sysctl interface so if you are
373 trying to save some space it is probably safe to disable this,
374 making your kernel marginally smaller.
376 If unsure say Y here.
379 bool "Load all symbols for debugging/ksymoops" if EMBEDDED
382 Say Y here to let the kernel print out symbolic crash information and
383 symbolic stack backtraces. This increases the size of the kernel
384 somewhat, as all symbols have to be loaded into the kernel image.
387 bool "Include all symbols in kallsyms"
388 depends on DEBUG_KERNEL && KALLSYMS
390 Normally kallsyms only contains the symbols of functions, for nicer
391 OOPS messages. Some debuggers can use kallsyms for other
392 symbols too: say Y here to include all symbols, if you need them
393 and you don't care about adding 300k to the size of your kernel.
397 config KALLSYMS_EXTRA_PASS
398 bool "Do an extra kallsyms pass"
401 If kallsyms is not working correctly, the build will fail with
402 inconsistent kallsyms data. If that occurs, log a bug report and
403 turn on KALLSYMS_EXTRA_PASS which should result in a stable build.
404 Always say N here unless you find a bug in kallsyms, which must be
405 reported. KALLSYMS_EXTRA_PASS is only a temporary workaround while
406 you wait for kallsyms to be fixed.
410 bool "Support for hot-pluggable devices" if EMBEDDED
413 This option is provided for the case where no hotplug or uevent
414 capabilities is wanted by the kernel. You should only consider
415 disabling this option for embedded systems that do not use modules, a
416 dynamic /dev tree, or dynamic device discovery. Just say Y.
420 bool "Enable support for printk" if EMBEDDED
422 This option enables normal printk support. Removing it
423 eliminates most of the message strings from the kernel image
424 and makes the kernel more or less silent. As this makes it
425 very difficult to diagnose system problems, saying N here is
426 strongly discouraged.
429 bool "BUG() support" if EMBEDDED
432 Disabling this option eliminates support for BUG and WARN, reducing
433 the size of your kernel image and potentially quietly ignoring
434 numerous fatal conditions. You should only consider disabling this
435 option for embedded systems with no facilities for reporting errors.
440 bool "Enable ELF core dumps" if EMBEDDED
442 Enable support for generating core dumps. Disabling saves about 4k.
446 bool "Enable full-sized data structures for core" if EMBEDDED
448 Disabling this option reduces the size of miscellaneous core
449 kernel data structures. This saves memory on small machines,
450 but may reduce performance.
453 bool "Enable futex support" if EMBEDDED
457 Disabling this option will cause the kernel to be built without
458 support for "fast userspace mutexes". The resulting kernel may not
459 run glibc-based applications correctly.
462 bool "Enable anonymous inode source" if EMBEDDED
465 Anonymous inode source for pseudo-files like epoll, signalfd,
471 bool "Enable eventpoll support" if EMBEDDED
473 depends on ANON_INODES
475 Disabling this option will cause the kernel to be built without
476 support for epoll family of system calls.
479 bool "Enable signalfd() system call" if EMBEDDED
480 depends on ANON_INODES
483 Enable the signalfd() system call that allows to receive signals
484 on a file descriptor.
489 bool "Enable timerfd() system call" if EMBEDDED
490 depends on ANON_INODES
493 Enable the timerfd() system call that allows to receive timer
494 events on a file descriptor.
499 bool "Enable eventfd() system call" if EMBEDDED
500 depends on ANON_INODES
503 Enable the eventfd() system call that allows to receive both
504 kernel notification (ie. KAIO) or userspace notifications.
509 bool "Use full shmem filesystem" if EMBEDDED
513 The shmem is an internal filesystem used to manage shared memory.
514 It is backed by swap and manages resource limits. It is also exported
515 to userspace as tmpfs if TMPFS is enabled. Disabling this
516 option replaces shmem and tmpfs with the much simpler ramfs code,
517 which may be appropriate on small systems without swap.
519 config VM_EVENT_COUNTERS
521 bool "Enable VM event counters for /proc/vmstat" if EMBEDDED
523 VM event counters are needed for event counts to be shown.
524 This option allows the disabling of the VM event counters
525 on EMBEDDED systems. /proc/vmstat will only show page counts
526 if VM event counters are disabled.
530 bool "Enable SLUB debugging support" if EMBEDDED
533 SLUB has extensive debug support features. Disabling these can
534 result in significant savings in code size. This also disables
535 SLUB sysfs support. /sys/slab will not exist and there will be
536 no support for cache validation etc.
539 prompt "Choose SLAB allocator"
542 This option allows to select a slab allocator.
547 The regular slab allocator that is established and known to work
548 well in all environments. It organizes cache hot objects in
549 per cpu and per node queues. SLAB is the default choice for
553 bool "SLUB (Unqueued Allocator)"
555 SLUB is a slab allocator that minimizes cache line usage
556 instead of managing queues of cached objects (SLAB approach).
557 Per cpu caching is realized using slabs of objects instead
558 of queues of objects. SLUB can use memory efficiently
559 and has enhanced diagnostics.
563 bool "SLOB (Simple Allocator)"
565 SLOB replaces the SLAB allocator with a drastically simpler
566 allocator. SLOB is more space efficient than SLAB but does not
567 scale well (single lock for all operations) and is also highly
568 susceptible to fragmentation. SLUB can accomplish a higher object
569 density. It is usually better to use SLUB instead of SLOB.
573 endmenu # General setup
585 default 0 if BASE_FULL
586 default 1 if !BASE_FULL
589 bool "Enable loadable module support"
591 Kernel modules are small pieces of compiled code which can
592 be inserted in the running kernel, rather than being
593 permanently built into the kernel. You use the "modprobe"
594 tool to add (and sometimes remove) them. If you say Y here,
595 many parts of the kernel can be built as modules (by
596 answering M instead of Y where indicated): this is most
597 useful for infrequently used options which are not required
598 for booting. For more information, see the man pages for
599 modprobe, lsmod, modinfo, insmod and rmmod.
601 If you say Y here, you will need to run "make
602 modules_install" to put the modules under /lib/modules/
603 where modprobe can find them (you may need to be root to do
609 bool "Module unloading"
612 Without this option you will not be able to unload any
613 modules (note that some modules may not be unloadable
614 anyway), which makes your kernel slightly smaller and
615 simpler. If unsure, say Y.
617 config MODULE_FORCE_UNLOAD
618 bool "Forced module unloading"
619 depends on MODULE_UNLOAD && EXPERIMENTAL
621 This option allows you to force a module to unload, even if the
622 kernel believes it is unsafe: the kernel will remove the module
623 without waiting for anyone to stop using it (using the -f option to
624 rmmod). This is mainly for kernel developers and desperate users.
628 bool "Module versioning support"
631 Usually, you have to use modules compiled with your kernel.
632 Saying Y here makes it sometimes possible to use modules
633 compiled for different kernels, by adding enough information
634 to the modules to (hopefully) spot any changes which would
635 make them incompatible with the kernel you are running. If
638 config MODULE_SRCVERSION_ALL
639 bool "Source checksum for all modules"
642 Modules which contain a MODULE_VERSION get an extra "srcversion"
643 field inserted into their modinfo section, which contains a
644 sum of the source files which made it. This helps maintainers
645 see exactly which source was used to build a module (since
646 others sometimes change the module source without updating
647 the version). With this option, such a "srcversion" field
648 will be created for all modules. If unsure, say N.
651 bool "Automatic kernel module loading"
654 Normally when you have selected some parts of the kernel to
655 be created as kernel modules, you must load them (using the
656 "modprobe" command) before you can use them. If you say Y
657 here, some parts of the kernel will be able to load modules
658 automatically: when a part of the kernel needs a module, it
659 runs modprobe with the appropriate arguments, thereby
660 loading the module if it is available. If unsure, say Y.
665 depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
667 Need stop_machine() primitive.
669 source "block/Kconfig"