1 menu "Code maturity level options"
4 bool "Prompt for development and/or incomplete code/drivers"
6 Some of the various things that Linux supports (such as network
7 drivers, file systems, network protocols, etc.) can be in a state
8 of development where the functionality, stability, or the level of
9 testing is not yet high enough for general use. This is usually
10 known as the "alpha-test" phase among developers. If a feature is
11 currently in alpha-test, then the developers usually discourage
12 uninformed widespread use of this feature by the general public to
13 avoid "Why doesn't this work?" type mail messages. However, active
14 testing and use of these systems is welcomed. Just be aware that it
15 may not meet the normal level of reliability or it may fail to work
16 in some special cases. Detailed bug reports from people familiar
17 with the kernel internals are usually welcomed by the developers
18 (before submitting bug reports, please read the documents
19 <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
20 <file:Documentation/BUG-HUNTING>, and
21 <file:Documentation/oops-tracing.txt> in the kernel source).
23 This option will also make obsoleted drivers available. These are
24 drivers that have been replaced by something else, and/or are
25 scheduled to be removed in a future kernel release.
27 Unless you intend to help test and develop a feature or driver that
28 falls into this category, or you have a situation that requires
29 using these features, you should probably say N here, which will
30 cause the configurator to present you with fewer choices. If
31 you say Y here, you will be offered the choice of using features or
32 drivers that are currently considered to be in the alpha-test phase.
39 depends on BROKEN || !SMP
44 depends on SMP || PREEMPT
47 config INIT_ENV_ARG_LIMIT
49 default 32 if !USERMODE
50 default 128 if USERMODE
52 Maximum of each of the number of arguments and environment
53 variables passed to init from the kernel command line.
60 string "Local version - append to kernel release"
62 Append an extra string to the end of your kernel version.
63 This will show up when you type uname, for example.
64 The string you set here will be appended after the contents of
65 any files with a filename matching localversion* in your
66 object and source tree, in that order. Your total string can
67 be a maximum of 64 characters.
69 config LOCALVERSION_AUTO
70 bool "Automatically append version information to the version string"
73 This will try to automatically determine if the current tree is a
74 release tree by looking for git tags that
75 belong to the current top of tree revision.
77 A string of the format -gxxxxxxxx will be added to the localversion
78 if a git based tree is found. The string generated by this will be
79 appended after any matching localversion* files, and after the value
80 set in CONFIG_LOCALVERSION
82 Note: This requires Perl, and a git repository, but not necessarily
83 the git or cogito tools to be installed.
86 bool "Support for paging of anonymous memory (swap)"
90 This option allows you to choose whether you want to have support
91 for so called swap devices or swap files in your kernel that are
92 used to provide more virtual memory than the actual RAM present
93 in your computer. If unsure say Y.
98 Inter Process Communication is a suite of library functions and
99 system calls which let processes (running programs) synchronize and
100 exchange information. It is generally considered to be a good thing,
101 and some programs won't run unless you say Y here. In particular, if
102 you want to run the DOS emulator dosemu under Linux (read the
103 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
104 you'll need to say Y here.
106 You can find documentation about IPC with "info ipc" and also in
107 section 6.4 of the Linux Programmer's Guide, available from
108 <http://www.tldp.org/guides.html>.
111 bool "POSIX Message Queues"
112 depends on NET && EXPERIMENTAL
114 POSIX variant of message queues is a part of IPC. In POSIX message
115 queues every message has a priority which decides about succession
116 of receiving it by a process. If you want to compile and run
117 programs written e.g. for Solaris with use of its POSIX message
118 queues (functions mq_*) say Y here. To use this feature you will
119 also need mqueue library, available from
120 <http://www.mat.uni.torun.pl/~wrona/posix_ipc/>
122 POSIX message queues are visible as a filesystem called 'mqueue'
123 and can be mounted somewhere if you want to do filesystem
124 operations on message queues.
128 config BSD_PROCESS_ACCT
129 bool "BSD Process Accounting"
131 If you say Y here, a user level program will be able to instruct the
132 kernel (via a special system call) to write process accounting
133 information to a file: whenever a process exits, information about
134 that process will be appended to the file by the kernel. The
135 information includes things such as creation time, owning user,
136 command name, memory usage, controlling terminal etc. (the complete
137 list is in the struct acct in <file:include/linux/acct.h>). It is
138 up to the user level program to do useful things with this
139 information. This is generally a good idea, so say Y.
141 config BSD_PROCESS_ACCT_V3
142 bool "BSD Process Accounting version 3 file format"
143 depends on BSD_PROCESS_ACCT
146 If you say Y here, the process accounting information is written
147 in a new file format that also logs the process IDs of each
148 process and it's parent. Note that this file format is incompatible
149 with previous v0/v1/v2 file formats, so you will need updated tools
150 for processing it. A preliminary version of these tools is available
151 at <http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/>.
154 bool "Sysctl support"
156 The sysctl interface provides a means of dynamically changing
157 certain kernel parameters and variables on the fly without requiring
158 a recompile of the kernel or reboot of the system. The primary
159 interface consists of a system call, but if you say Y to "/proc
160 file system support", a tree of modifiable sysctl entries will be
161 generated beneath the /proc/sys directory. They are explained in the
162 files in <file:Documentation/sysctl/>. Note that enabling this
163 option will enlarge the kernel by at least 8 KB.
165 As it is generally a good thing, you should say Y here unless
166 building a kernel for install/rescue disks or your system is very
170 bool "Auditing support"
173 Enable auditing infrastructure that can be used with another
174 kernel subsystem, such as SELinux (which requires this for
175 logging of avc messages output). Does not do system-call
176 auditing without CONFIG_AUDITSYSCALL.
179 bool "Enable system-call auditing support"
180 depends on AUDIT && (X86 || PPC || PPC64 || S390 || IA64 || UML || SPARC64)
181 default y if SECURITY_SELINUX
183 Enable low-overhead system-call auditing infrastructure that
184 can be used independently or with another kernel subsystem,
188 bool "Kernel .config support"
190 This option enables the complete Linux kernel ".config" file
191 contents to be saved in the kernel. It provides documentation
192 of which kernel options are used in a running kernel or in an
193 on-disk kernel. This information can be extracted from the kernel
194 image file with the script scripts/extract-ikconfig and used as
195 input to rebuild the current kernel or to build another kernel.
196 It can also be extracted from a running kernel by reading
197 /proc/config.gz if enabled (below).
200 bool "Enable access to .config through /proc/config.gz"
201 depends on IKCONFIG && PROC_FS
203 This option enables access to the kernel configuration file
204 through /proc/config.gz.
210 This option enables panic() to be called when a system is out of
211 memory. This feature along with /proc/sys/kernel/panic allows a
212 different behavior on out-of-memory conditions when the standard
213 behavior (killing processes in an attempt to recover) does not
220 depends on !OOM_PANIC
224 bool "Cpuset support"
227 This option will let you create and manage CPUSETs which
228 allow dynamically partitioning a system into sets of CPUs and
229 Memory Nodes and assigning tasks to run only within those sets.
230 This is primarily useful on large SMP or NUMA systems.
235 bool "Kernel->user space relay support (formerly relayfs)"
237 This option enables support for relay interface support in
238 certain file systems (such as debugfs).
239 It is designed to provide an efficient mechanism for tools and
240 facilities to relay large amounts of data from kernel space to
248 bool "Enable 16-bit UID system calls" if EMBEDDED
249 depends on ARM || CRIS || FRV || H8300 || X86_32 || M68K || (S390 && !64BIT) || SUPERH || SPARC32 || (SPARC64 && SPARC32_COMPAT) || UML || (X86_64 && IA32_EMULATION)
252 This enables the legacy 16-bit UID syscall wrappers.
257 bool "Enable VM86 support" if EMBEDDED
259 This option is required by programs like DOSEMU to run 16-bit legacy
260 code on X86 processors. It also may be needed by software like
261 XFree86 to initialize some video cards via BIOS. Disabling this
262 option saves about 6k.
264 config CC_OPTIMIZE_FOR_SIZE
265 bool "Optimize for size (Look out for broken compilers!)"
267 depends on ARM || H8300 || EXPERIMENTAL
269 Enabling this option will pass "-Os" instead of "-O2" to gcc
270 resulting in a smaller kernel.
272 WARNING: some versions of gcc may generate incorrect code with this
273 option. If problems are observed, a gcc upgrade may be needed.
278 bool "Configure standard kernel features (for small systems)"
280 This option allows certain base kernel options and settings
281 to be disabled or tweaked. This is for specialized
282 environments which can tolerate a "non-standard" kernel.
283 Only use this if you really know what you are doing.
286 bool "Load all symbols for debugging/kksymoops" if EMBEDDED
289 Say Y here to let the kernel print out symbolic crash information and
290 symbolic stack backtraces. This increases the size of the kernel
291 somewhat, as all symbols have to be loaded into the kernel image.
294 bool "Include all symbols in kallsyms"
295 depends on DEBUG_KERNEL && KALLSYMS
297 Normally kallsyms only contains the symbols of functions, for nicer
298 OOPS messages. Some debuggers can use kallsyms for other
299 symbols too: say Y here to include all symbols, if you need them
300 and you don't care about adding 300k to the size of your kernel.
304 config KALLSYMS_EXTRA_PASS
305 bool "Do an extra kallsyms pass"
308 If kallsyms is not working correctly, the build will fail with
309 inconsistent kallsyms data. If that occurs, log a bug report and
310 turn on KALLSYMS_EXTRA_PASS which should result in a stable build.
311 Always say N here unless you find a bug in kallsyms, which must be
312 reported. KALLSYMS_EXTRA_PASS is only a temporary workaround while
313 you wait for kallsyms to be fixed.
317 bool "Support for hot-pluggable devices" if EMBEDDED
320 This option is provided for the case where no hotplug or uevent
321 capabilities is wanted by the kernel. You should only consider
322 disabling this option for embedded systems that do not use modules, a
323 dynamic /dev tree, or dynamic device discovery. Just say Y.
327 bool "Enable support for printk" if EMBEDDED
329 This option enables normal printk support. Removing it
330 eliminates most of the message strings from the kernel image
331 and makes the kernel more or less silent. As this makes it
332 very difficult to diagnose system problems, saying N here is
333 strongly discouraged.
336 bool "BUG() support" if EMBEDDED
339 Disabling this option eliminates support for BUG and WARN, reducing
340 the size of your kernel image and potentially quietly ignoring
341 numerous fatal conditions. You should only consider disabling this
342 option for embedded systems with no facilities for reporting errors.
347 bool "Enable ELF core dumps" if EMBEDDED
349 Enable support for generating core dumps. Disabling saves about 4k.
353 bool "Enable full-sized data structures for core" if EMBEDDED
355 Disabling this option reduces the size of miscellaneous core
356 kernel data structures. This saves memory on small machines,
357 but may reduce performance.
360 bool "Enable futex support" if EMBEDDED
363 Disabling this option will cause the kernel to be built without
364 support for "fast userspace mutexes". The resulting kernel may not
365 run glibc-based applications correctly.
368 bool "Enable eventpoll support" if EMBEDDED
371 Disabling this option will cause the kernel to be built without
372 support for epoll family of system calls.
375 bool "Use full shmem filesystem" if EMBEDDED
379 The shmem is an internal filesystem used to manage shared memory.
380 It is backed by swap and manages resource limits. It is also exported
381 to userspace as tmpfs if TMPFS is enabled. Disabling this
382 option replaces shmem and tmpfs with the much simpler ramfs code,
383 which may be appropriate on small systems without swap.
387 bool "Use full SLAB allocator" if EMBEDDED
389 Disabling this replaces the advanced SLAB allocator and
390 kmalloc support with the drastically simpler SLOB allocator.
391 SLOB is more space efficient but does not scale well and is
392 more susceptible to fragmentation.
394 endmenu # General setup
402 default 0 if BASE_FULL
403 default 1 if !BASE_FULL
409 config OBSOLETE_INTERMODULE
412 menu "Loadable module support"
415 bool "Enable loadable module support"
417 Kernel modules are small pieces of compiled code which can
418 be inserted in the running kernel, rather than being
419 permanently built into the kernel. You use the "modprobe"
420 tool to add (and sometimes remove) them. If you say Y here,
421 many parts of the kernel can be built as modules (by
422 answering M instead of Y where indicated): this is most
423 useful for infrequently used options which are not required
424 for booting. For more information, see the man pages for
425 modprobe, lsmod, modinfo, insmod and rmmod.
427 If you say Y here, you will need to run "make
428 modules_install" to put the modules under /lib/modules/
429 where modprobe can find them (you may need to be root to do
435 bool "Module unloading"
438 Without this option you will not be able to unload any
439 modules (note that some modules may not be unloadable
440 anyway), which makes your kernel slightly smaller and
441 simpler. If unsure, say Y.
443 config MODULE_FORCE_UNLOAD
444 bool "Forced module unloading"
445 depends on MODULE_UNLOAD && EXPERIMENTAL
447 This option allows you to force a module to unload, even if the
448 kernel believes it is unsafe: the kernel will remove the module
449 without waiting for anyone to stop using it (using the -f option to
450 rmmod). This is mainly for kernel developers and desperate users.
454 bool "Module versioning support"
457 Usually, you have to use modules compiled with your kernel.
458 Saying Y here makes it sometimes possible to use modules
459 compiled for different kernels, by adding enough information
460 to the modules to (hopefully) spot any changes which would
461 make them incompatible with the kernel you are running. If
464 config MODULE_SRCVERSION_ALL
465 bool "Source checksum for all modules"
468 Modules which contain a MODULE_VERSION get an extra "srcversion"
469 field inserted into their modinfo section, which contains a
470 sum of the source files which made it. This helps maintainers
471 see exactly which source was used to build a module (since
472 others sometimes change the module source without updating
473 the version). With this option, such a "srcversion" field
474 will be created for all modules. If unsure, say N.
477 bool "Module signature verification (EXPERIMENTAL)"
478 depends on MODULES && EXPERIMENTAL
481 select CRYPTO_SIGNATURE
483 Check modules for valid signatures upon load.
485 config MODULE_SIG_FORCE
486 bool "Required modules to be validly signed (EXPERIMENTAL)"
487 depends on MODULE_SIG
489 Reject unsigned modules or signed modules for which we don't have a
493 bool "Automatic kernel module loading"
496 Normally when you have selected some parts of the kernel to
497 be created as kernel modules, you must load them (using the
498 "modprobe" command) before you can use them. If you say Y
499 here, some parts of the kernel will be able to load modules
500 automatically: when a part of the kernel needs a module, it
501 runs modprobe with the appropriate arguments, thereby
502 loading the module if it is available. If unsure, say Y.
507 depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
509 Need stop_machine() primitive.
513 source "block/Kconfig"