2 menu "Code maturity level options"
5 bool "Prompt for development and/or incomplete code/drivers"
7 Some of the various things that Linux supports (such as network
8 drivers, file systems, network protocols, etc.) can be in a state
9 of development where the functionality, stability, or the level of
10 testing is not yet high enough for general use. This is usually
11 known as the "alpha-test" phase among developers. If a feature is
12 currently in alpha-test, then the developers usually discourage
13 uninformed widespread use of this feature by the general public to
14 avoid "Why doesn't this work?" type mail messages. However, active
15 testing and use of these systems is welcomed. Just be aware that it
16 may not meet the normal level of reliability or it may fail to work
17 in some special cases. Detailed bug reports from people familiar
18 with the kernel internals are usually welcomed by the developers
19 (before submitting bug reports, please read the documents
20 <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
21 <file:Documentation/BUG-HUNTING>, and
22 <file:Documentation/oops-tracing.txt> in the kernel source).
24 This option will also make obsoleted drivers available. These are
25 drivers that have been replaced by something else, and/or are
26 scheduled to be removed in a future kernel release.
28 Unless you intend to help test and develop a feature or driver that
29 falls into this category, or you have a situation that requires
30 using these features, you should probably say N here, which will
31 cause the configurator to present you with fewer choices. If
32 you say Y here, you will be offered the choice of using features or
33 drivers that are currently considered to be in the alpha-test phase.
36 bool "Select only drivers expected to compile cleanly" if EXPERIMENTAL
39 Select this option if you don't even want to see the option
40 to configure known-broken drivers.
46 depends on !CLEAN_COMPILE
51 depends on BROKEN || !SMP
60 bool "Support for paging of anonymous memory (swap)"
64 This option allows you to choose whether you want to have support
65 for socalled swap devices or swap files in your kernel that are
66 used to provide more virtual memory than the actual RAM present
67 in your computer. If unsure say Y.
73 Inter Process Communication is a suite of library functions and
74 system calls which let processes (running programs) synchronize and
75 exchange information. It is generally considered to be a good thing,
76 and some programs won't run unless you say Y here. In particular, if
77 you want to run the DOS emulator dosemu under Linux (read the
78 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
79 you'll need to say Y here.
80 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
81 you'll need to say Y here.
83 You can find documentation about IPC with "info ipc" and also in
84 section 6.4 of the Linux Programmer's Guide, available from
85 <http://www.tldp.org/guides.html>.
88 bool "POSIX Message Queues"
89 depends on NET && EXPERIMENTAL
91 POSIX variant of message queues is a part of IPC. In POSIX message
92 queues every message has a priority which decides about succession
93 of receiving it by a process. If you want to compile and run
94 programs written e.g. for Solaris with use of its POSIX message
95 queues (functions mq_*) say Y here. To use this feature you will
96 also need mqueue library, available from
97 <http://www.mat.uni.torun.pl/~wrona/posix_ipc/>
99 POSIX message queues are visible as a filesystem called 'mqueue'
100 and can be mounted somewhere if you want to do filesystem
101 operations on message queues.
105 config BSD_PROCESS_ACCT
106 bool "BSD Process Accounting"
108 If you say Y here, a user level program will be able to instruct the
109 kernel (via a special system call) to write process accounting
110 information to a file: whenever a process exits, information about
111 that process will be appended to the file by the kernel. The
112 information includes things such as creation time, owning user,
113 command name, memory usage, controlling terminal etc. (the complete
114 list is in the struct acct in <file:include/linux/acct.h>). It is
115 up to the user level program to do useful things with this
116 information. This is generally a good idea, so say Y.
118 config BSD_PROCESS_ACCT_V3
119 bool "BSD Process Accounting version 3 file format"
120 depends on BSD_PROCESS_ACCT
123 If you say Y here, the process accounting information is written
124 in a new file format that also logs the process IDs of each
125 process and it's parent. Note that this file format is incompatible
126 with previous v0/v1/v2 file formats, so you will need updated tools
127 for processing it. A preliminary version of these tools is available
128 at <http://http://www.de.kernel.org/pub/linux/utils/acct/>.
130 menu "Class Based Kernel Resource Management"
133 bool "Class Based Kernel Resource Management Core"
134 depends on EXPERIMENTAL
136 Class-based Kernel Resource Management is a framework for controlling
137 and monitoring resource allocation of user-defined groups of tasks or
138 incoming socket connections. For more information, please visit
141 If you say Y here, enable the Resource Class File System and atleast
142 one of the resource controllers below. Say N if you are unsure.
145 tristate "Resource Class File System (User API)"
148 RCFS is the filesystem API for CKRM. This separate configuration
149 option is provided only for debugging and will eventually disappear
150 since rcfs will be automounted whenever CKRM is configured.
152 Say N if unsure, Y if you've enabled CKRM, M to debug rcfs
155 config CKRM_TYPE_TASKCLASS
156 bool "Class Manager for Task Groups"
159 TASKCLASS provides the extensions for CKRM to track task classes
160 This is the base to enable task class based resource control for
161 cpu, memory and disk I/O.
165 config CKRM_RES_NUMTASKS
166 tristate "Number of Tasks Resource Manager"
167 depends on CKRM_TYPE_TASKCLASS
170 Provides a Resource Controller for CKRM that allows limiting no of
171 tasks a task class can have.
173 Say N if unsure, Y to use the feature.
175 config CKRM_CPU_SCHEDULE
176 bool "CKRM CPU scheduler"
177 depends on CKRM_TYPE_TASKCLASS
180 Use CKRM CPU scheduler instead of Linux Scheduler
182 Say N if unsure, Y to use the feature.
184 config CKRM_RES_BLKIO
185 tristate " Disk I/O Resource Controller"
186 depends on CKRM_TYPE_TASKCLASS && IOSCHED_CFQ
189 Provides a resource controller for best-effort block I/O
190 bandwidth control. The controller attempts this by proportional
191 servicing of requests in the I/O scheduler. However, seek
192 optimizations and reordering by device drivers/disk controllers may
193 alter the actual bandwidth delivered to a class.
195 Say N if unsure, Y to use the feature.
198 bool "Class based physical memory controller"
202 Provide the basic support for collecting physical memory usage information
203 among classes. Say Y if you want to know the memory usage of each class.
205 config CKRM_MEM_LRUORDER_CHANGE
206 bool "Change the LRU ordering of scanned pages"
208 depends on CKRM_RES_MEM
210 While trying to free pages, by default(n), scanned pages are left were they
211 are found if they belong to relatively under-used class. In this case the
212 LRU ordering of the memory subsystemis left intact. If this option is chosen,
213 then the scanned pages are moved to the tail of the list(active or inactive).
214 Changing this to yes reduces the checking overhead but violates the approximate
215 LRU order that is maintained by the paging subsystem.
217 config CKRM_TYPE_SOCKETCLASS
218 bool "Class Manager for socket groups"
221 SOCKET provides the extensions for CKRM to track per socket
222 classes. This is the base to enable socket based resource
223 control for inbound connection control, bandwidth control etc.
227 config CKRM_RES_LISTENAQ
228 tristate "Multiple Accept Queues Resource Manager"
229 depends on CKRM_TYPE_SOCKETCLASS && ACCEPT_QUEUES
232 Provides a resource controller for CKRM to prioritize inbound
233 connection requests. See inbound control description for
234 "IP: TCP Multiple accept queues support". If you choose that
235 option choose this option to control the queue weights.
240 tristate "Vanilla Rule-based Classification Engine (RBCE)"
241 depends on CKRM && RCFS_FS
244 Provides an optional module to support creation of rules for automatic
245 classification of kernel objects. Rules are created/deleted/modified
246 through an rcfs interface. RBCE is not required for CKRM.
251 tristate "Enhanced Rule-based Classification Engine (RBCE)"
252 depends on CKRM && RCFS_FS && RELAYFS_FS && DELAY_ACCT
255 Provides an optional module to support creation of rules for automatic
256 classification of kernel objects, just like RBCE above. In addition,
257 CRBCE provides per-process delay data (requires DELAY_ACCT configured)
258 enabled) and makes information on significant kernel events available
259 to userspace tools through relayfs (requires RELAYFS_FS configured).
266 bool "Sysctl support"
268 The sysctl interface provides a means of dynamically changing
269 certain kernel parameters and variables on the fly without requiring
270 a recompile of the kernel or reboot of the system. The primary
271 interface consists of a system call, but if you say Y to "/proc
272 file system support", a tree of modifiable sysctl entries will be
273 generated beneath the /proc/sys directory. They are explained in the
274 files in <file:Documentation/sysctl/>. Note that enabling this
275 option will enlarge the kernel by at least 8 KB.
277 As it is generally a good thing, you should say Y here unless
278 building a kernel for install/rescue disks or your system is very
282 bool "Auditing support"
283 default y if SECURITY_SELINUX
286 Enable auditing infrastructure that can be used with another
287 kernel subsystem, such as SELinux (which requires this for
288 logging of avc messages output). Does not do system-call
289 auditing without CONFIG_AUDITSYSCALL.
292 bool "Enable system-call auditing support"
293 depends on AUDIT && (X86 || PPC64 || ARCH_S390 || IA64)
294 default y if SECURITY_SELINUX
297 Enable low-overhead system-call auditing infrastructure that
298 can be used independently or with another kernel subsystem,
302 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
304 default 17 if ARCH_S390
305 default 16 if X86_NUMAQ || IA64
309 Select kernel log buffer size as a power of 2.
310 Defaults and Examples:
311 17 => 128 KB for S/390
312 16 => 64 KB for x86 NUMAQ or IA-64
314 14 => 16 KB for uniprocessor
319 bool "Support for hot-pluggable devices" if !ARCH_S390
322 Say Y here if you want to plug devices into your computer while
323 the system is running, and be able to use them quickly. In many
324 cases, the devices can likewise be unplugged at any time too.
326 One well known example of this is PCMCIA- or PC-cards, credit-card
327 size devices such as network cards, modems or hard drives which are
328 plugged into slots found on all modern laptop computers. Another
329 example, used on modern desktops as well as laptops, is USB.
331 Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
332 software (at <http://linux-hotplug.sourceforge.net/>) and install it.
333 Then your kernel will automatically call out to a user mode "policy
334 agent" (/sbin/hotplug) to load modules and set up software needed
335 to use devices as you hotplug them.
338 bool "Kernel .config support"
340 This option enables the complete Linux kernel ".config" file
341 contents to be saved in the kernel. It provides documentation
342 of which kernel options are used in a running kernel or in an
343 on-disk kernel. This information can be extracted from the kernel
344 image file with the script scripts/extract-ikconfig and used as
345 input to rebuild the current kernel or to build another kernel.
346 It can also be extracted from a running kernel by reading
347 /proc/config.gz if enabled (below).
350 bool "Enable access to .config through /proc/config.gz"
351 depends on IKCONFIG && PROC_FS
353 This option enables access to the kernel configuration file
354 through /proc/config.gz.
358 bool "Configure standard kernel features (for small systems)"
360 This option allows certain base kernel options and settings
361 to be disabled or tweaked. This is for specialized
362 environments which can tolerate a "non-standard" kernel.
363 Only use this if you really know what you are doing.
366 bool "Enable delay accounting (EXPERIMENTAL)"
368 In addition to counting frequency the total delay in ns is also
369 recorded. CPU delays are specified as cpu-wait and cpu-run.
370 I/O delays are recorded for memory and regular I/O.
371 Information is accessible through /proc/<pid>/delay.
375 bool "Load all symbols for debugging/kksymoops" if EMBEDDED
378 Say Y here to let the kernel print out symbolic crash information and
379 symbolic stack backtraces. This increases the size of the kernel
380 somewhat, as all symbols have to be loaded into the kernel image.
383 bool "Include all symbols in kallsyms"
384 depends on DEBUG_KERNEL && KALLSYMS
386 Normally kallsyms only contains the symbols of functions, for nicer
387 OOPS messages. Some debuggers can use kallsyms for other
388 symbols too: say Y here to include all symbols, and you
389 don't care about adding 300k to the size of your kernel.
393 config KALLSYMS_EXTRA_PASS
394 bool "Do an extra kallsyms pass"
397 If kallsyms is not working correctly, the build will fail with
398 inconsistent kallsyms data. If that occurs, log a bug report and
399 turn on KALLSYMS_EXTRA_PASS which should result in a stable build.
400 Always say N here unless you find a bug in kallsyms, which must be
401 reported. KALLSYMS_EXTRA_PASS is only a temporary workaround while
402 you wait for kallsyms to be fixed.
405 bool "Enable futex support" if EMBEDDED
408 Disabling this option will cause the kernel to be built without
409 support for "fast userspace mutexes". The resulting kernel may not
410 run glibc-based applications correctly.
413 bool "Enable eventpoll support" if EMBEDDED
416 Disabling this option will cause the kernel to be built without
417 support for epoll family of system calls.
419 source "drivers/block/Kconfig.iosched"
421 config CC_OPTIMIZE_FOR_SIZE
422 bool "Optimize for size"
423 default y if ARM || H8300
426 Enabling this option will pass "-Os" instead of "-O2" to gcc
427 resulting in a smaller kernel.
429 WARNING: some versions of gcc may generate incorrect code with this
430 option. If problems are observed, a gcc upgrade may be needed.
434 endmenu # General setup
437 menu "Loadable module support"
440 bool "Enable loadable module support"
442 Kernel modules are small pieces of compiled code which can
443 be inserted in the running kernel, rather than being
444 permanently built into the kernel. You use the "modprobe"
445 tool to add (and sometimes remove) them. If you say Y here,
446 many parts of the kernel can be built as modules (by
447 answering M instead of Y where indicated): this is most
448 useful for infrequently used options which are not required
449 for booting. For more information, see the man pages for
450 modprobe, lsmod, modinfo, insmod and rmmod.
452 If you say Y here, you will need to run "make
453 modules_install" to put the modules under /lib/modules/
454 where modprobe can find them (you may need to be root to do
460 bool "Module unloading"
463 Without this option you will not be able to unload any
464 modules (note that some modules may not be unloadable
465 anyway), which makes your kernel slightly smaller and
466 simpler. If unsure, say Y.
468 config MODULE_FORCE_UNLOAD
469 bool "Forced module unloading"
470 depends on MODULE_UNLOAD && EXPERIMENTAL
472 This option allows you to force a module to unload, even if the
473 kernel believes it is unsafe: the kernel will remove the module
474 without waiting for anyone to stop using it (using the -f option to
475 rmmod). This is mainly for kernel developers and desperate users.
478 config OBSOLETE_MODPARM
483 You need this option to use module parameters on modules which
484 have not been converted to the new module parameter system yet.
488 bool "Module versioning support (EXPERIMENTAL)"
489 depends on MODULES && EXPERIMENTAL
491 Usually, you have to use modules compiled with your kernel.
492 Saying Y here makes it sometimes possible to use modules
493 compiled for different kernels, by adding enough information
494 to the modules to (hopefully) spot any changes which would
495 make them incompatible with the kernel you are running. If
499 bool "Module signature verification (EXPERIMENTAL)"
500 depends on MODULES && EXPERIMENTAL
502 select CRYPTO_SIGNATURE
504 Check modules for valid signatures upon load.
506 config MODULE_SIG_FORCE
507 bool "Required modules to be validly signed (EXPERIMENTAL)"
508 depends on MODULE_SIG
510 Reject unsigned modules or signed modules for which we don't have a
514 bool "Automatic kernel module loading"
517 Normally when you have selected some parts of the kernel to
518 be created as kernel modules, you must load them (using the
519 "modprobe" command) before you can use them. If you say Y
520 here, some parts of the kernel will be able to load modules
521 automatically: when a part of the kernel needs a module, it
522 runs modprobe with the appropriate arguments, thereby
523 loading the module if it is available. If unsure, say Y.
528 depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
530 Need stop_machine() primitive.