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.
45 bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL
48 Select this option if you don't have magic firmware for drivers that
55 depends on !CLEAN_COMPILE
60 depends on BROKEN || !SMP
69 bool "Support for paging of anonymous memory (swap)"
73 This option allows you to choose whether you want to have support
74 for socalled swap devices or swap files in your kernel that are
75 used to provide more virtual memory than the actual RAM present
76 in your computer. If unsure say Y.
81 Inter Process Communication is a suite of library functions and
82 system calls which let processes (running programs) synchronize and
83 exchange information. It is generally considered to be a good thing,
84 and some programs won't run unless you say Y here. In particular, if
85 you want to run the DOS emulator dosemu under Linux (read the
86 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
87 you'll need to say Y here.
88 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
89 you'll need to say Y here.
91 You can find documentation about IPC with "info ipc" and also in
92 section 6.4 of the Linux Programmer's Guide, available from
93 <http://www.tldp.org/guides.html>.
96 bool "POSIX Message Queues"
97 depends on NET && EXPERIMENTAL
99 POSIX variant of message queues is a part of IPC. In POSIX message
100 queues every message has a priority which decides about succession
101 of receiving it by a process. If you want to compile and run
102 programs written e.g. for Solaris with use of its POSIX message
103 queues (functions mq_*) say Y here. To use this feature you will
104 also need mqueue library, available from
105 <http://www.mat.uni.torun.pl/~wrona/posix_ipc/>
107 POSIX message queues are visible as a filesystem called 'mqueue'
108 and can be mounted somewhere if you want to do filesystem
109 operations on message queues.
113 config BSD_PROCESS_ACCT
114 bool "BSD Process Accounting"
116 If you say Y here, a user level program will be able to instruct the
117 kernel (via a special system call) to write process accounting
118 information to a file: whenever a process exits, information about
119 that process will be appended to the file by the kernel. The
120 information includes things such as creation time, owning user,
121 command name, memory usage, controlling terminal etc. (the complete
122 list is in the struct acct in <file:include/linux/acct.h>). It is
123 up to the user level program to do useful things with this
124 information. This is generally a good idea, so say Y.
126 menu "Class Based Kernel Resource Management"
129 bool "Class Based Kernel Resource Management Core"
130 depends on EXPERIMENTAL
132 Class-based Kernel Resource Management is a framework for controlling
133 and monitoring resource allocation of user-defined groups of tasks or
134 incoming socket connections. For more information, please visit
137 If you say Y here, enable the Resource Class File System and atleast
138 one of the resource controllers below. Say N if you are unsure.
141 tristate "Resource Class File System (User API)"
144 RCFS is the filesystem API for CKRM. This separate configuration
145 option is provided only for debugging and will eventually disappear
146 since rcfs will be automounted whenever CKRM is configured.
148 Say N if unsure, Y if you've enabled CKRM, M to debug rcfs
151 config CKRM_TYPE_TASKCLASS
152 bool "Class Manager for Task Groups"
155 TASKCLASS provides the extensions for CKRM to track task classes
156 This is the base to enable task class based resource control for
157 cpu, memory and disk I/O.
161 config CKRM_RES_NUMTASKS
162 tristate "Number of Tasks Resource Manager"
163 depends on CKRM_TYPE_TASKCLASS
166 Provides a Resource Controller for CKRM that allows limiting no of
167 tasks a task class can have.
169 Say N if unsure, Y to use the feature.
171 config CKRM_CPU_SCHEDULE
172 bool "CKRM CPU scheduler"
173 depends on CKRM_TYPE_TASKCLASS
176 Use CKRM CPU scheduler instead of Linux Scheduler
178 Say N if unsure, Y to use the feature.
180 config CKRM_CPU_MONITOR
181 tristate "CKRM CPU Resoure Monitor"
182 depends on CKRM_CPU_SCHEDULE
185 Monitor CPU Resource Usage of the classes
187 Say N if unsure, Y to use the feature.
189 config CKRM_TYPE_SOCKETCLASS
190 bool "Class Manager for socket groups"
193 SOCKET provides the extensions for CKRM to track per socket
194 classes. This is the base to enable socket based resource
195 control for inbound connection control, bandwidth control etc.
199 config CKRM_RES_LISTENAQ
200 tristate "Multiple Accept Queues Resource Manager"
201 depends on CKRM_TYPE_SOCKETCLASS && ACCEPT_QUEUES
204 Provides a resource controller for CKRM to prioritize inbound
205 connection requests. See inbound control description for
206 "IP: TCP Multiple accept queues support". If you choose that
207 option choose this option to control the queue weights.
212 tristate "Vanilla Rule-based Classification Engine (RBCE)"
213 depends on CKRM && RCFS_FS
216 Provides an optional module to support creation of rules for automatic
217 classification of kernel objects. Rules are created/deleted/modified
218 through an rcfs interface. RBCE is not required for CKRM.
223 tristate "Enhanced Rule-based Classification Engine (RBCE)"
224 depends on CKRM && RCFS_FS && RELAYFS_FS && DELAY_ACCT
227 Provides an optional module to support creation of rules for automatic
228 classification of kernel objects, just like RBCE above. In addition,
229 CRBCE provides per-process delay data (requires DELAY_ACCT configured)
230 enabled) and makes information on significant kernel events available
231 to userspace tools through relayfs (requires RELAYFS_FS configured).
238 bool "Sysctl support"
240 The sysctl interface provides a means of dynamically changing
241 certain kernel parameters and variables on the fly without requiring
242 a recompile of the kernel or reboot of the system. The primary
243 interface consists of a system call, but if you say Y to "/proc
244 file system support", a tree of modifiable sysctl entries will be
245 generated beneath the /proc/sys directory. They are explained in the
246 files in <file:Documentation/sysctl/>. Note that enabling this
247 option will enlarge the kernel by at least 8 KB.
249 As it is generally a good thing, you should say Y here unless
250 building a kernel for install/rescue disks or your system is very
254 bool "Auditing support"
255 default y if SECURITY_SELINUX
258 Enable auditing infrastructure that can be used with another
259 kernel subsystem, such as SELinux (which requires this for
260 logging of avc messages output). Does not do system-call
261 auditing without CONFIG_AUDITSYSCALL.
264 bool "Enable system-call auditing support"
265 depends on AUDIT && (X86 || PPC64 || ARCH_S390)
266 default y if SECURITY_SELINUX
269 Enable low-overhead system-call auditing infrastructure that
270 can be used independently or with another kernel subsystem,
274 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
276 default 17 if ARCH_S390
277 default 16 if X86_NUMAQ || IA64
281 Select kernel log buffer size as a power of 2.
282 Defaults and Examples:
283 17 => 128 KB for S/390
284 16 => 64 KB for x86 NUMAQ or IA-64
286 14 => 16 KB for uniprocessor
291 bool "Support for hot-pluggable devices" if !ARCH_S390
294 Say Y here if you want to plug devices into your computer while
295 the system is running, and be able to use them quickly. In many
296 cases, the devices can likewise be unplugged at any time too.
298 One well known example of this is PCMCIA- or PC-cards, credit-card
299 size devices such as network cards, modems or hard drives which are
300 plugged into slots found on all modern laptop computers. Another
301 example, used on modern desktops as well as laptops, is USB.
303 Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
304 software (at <http://linux-hotplug.sourceforge.net/>) and install it.
305 Then your kernel will automatically call out to a user mode "policy
306 agent" (/sbin/hotplug) to load modules and set up software needed
307 to use devices as you hotplug them.
310 bool "Kernel .config support"
312 This option enables the complete Linux kernel ".config" file
313 contents, information on compiler used to build the kernel,
314 kernel running when this kernel was built and kernel version
315 from Makefile to be saved in the kernel. It provides documentation
316 of which kernel options are used in a running kernel or in an
317 on-disk kernel. This information can be extracted from the kernel
318 image file with the script scripts/extract-ikconfig and used as
319 input to rebuild the current kernel or to build another kernel.
320 It can also be extracted from a running kernel by reading
321 /proc/config.gz and /proc/config_built_with, if enabled (below).
322 /proc/config.gz will list the configuration that was used
323 to build the kernel and /proc/config_built_with will list
324 information on the compiler and host machine that was used to
328 bool "Enable access to .config through /proc/config.gz"
329 depends on IKCONFIG && PROC_FS
331 This option enables access to kernel configuration file and build
332 information through /proc/config.gz.
336 bool "Configure standard kernel features (for small systems)"
338 This option allows certain base kernel options and settings
339 to be disabled or tweaked. This is for specialized
340 environments which can tolerate a "non-standard" kernel.
341 Only use this if you really know what you are doing.
344 bool "Enable delay accounting (EXPERIMENTAL)"
346 In addition to counting frequency the total delay in ns is also
347 recorded. CPU delays are specified as cpu-wait and cpu-run.
348 I/O delays are recorded for memory and regular I/O.
349 Information is accessible through /proc/<pid>/delay.
353 bool "Load all symbols for debugging/kksymoops" if EMBEDDED
356 Say Y here to let the kernel print out symbolic crash information and
357 symbolic stack backtraces. This increases the size of the kernel
358 somewhat, as all symbols have to be loaded into the kernel image.
361 bool "Include all symbols in kallsyms"
362 depends on DEBUG_KERNEL && KALLSYMS
364 Normally kallsyms only contains the symbols of functions, for nicer
365 OOPS messages. Some debuggers can use kallsyms for other
366 symbols too: say Y here to include all symbols, and you
367 don't care about adding 300k to the size of your kernel.
372 bool "Enable futex support" if EMBEDDED
375 Disabling this option will cause the kernel to be built without
376 support for "fast userspace mutexes". The resulting kernel may not
377 run glibc-based applications correctly.
380 bool "Enable eventpoll support" if EMBEDDED
383 Disabling this option will cause the kernel to be built without
384 support for epoll family of system calls.
386 source "drivers/block/Kconfig.iosched"
388 config CC_OPTIMIZE_FOR_SIZE
389 bool "Optimize for size" if EMBEDDED
390 default y if ARM || H8300
393 Enabling this option will pass "-Os" instead of "-O2" to gcc
394 resulting in a smaller kernel.
396 WARNING: some versions of gcc may generate incorrect code with this
397 option. If problems are observed, a gcc upgrade may be needed.
401 endmenu # General setup
404 menu "Loadable module support"
407 bool "Enable loadable module support"
409 Kernel modules are small pieces of compiled code which can
410 be inserted in the running kernel, rather than being
411 permanently built into the kernel. You use the "modprobe"
412 tool to add (and sometimes remove) them. If you say Y here,
413 many parts of the kernel can be built as modules (by
414 answering M instead of Y where indicated): this is most
415 useful for infrequently used options which are not required
416 for booting. For more information, see the man pages for
417 modprobe, lsmod, modinfo, insmod and rmmod.
419 If you say Y here, you will need to run "make
420 modules_install" to put the modules under /lib/modules/
421 where modprobe can find them (you may need to be root to do
427 bool "Module unloading"
430 Without this option you will not be able to unload any
431 modules (note that some modules may not be unloadable
432 anyway), which makes your kernel slightly smaller and
433 simpler. If unsure, say Y.
435 config MODULE_FORCE_UNLOAD
436 bool "Forced module unloading"
437 depends on MODULE_UNLOAD && EXPERIMENTAL
439 This option allows you to force a module to unload, even if the
440 kernel believes it is unsafe: the kernel will remove the module
441 without waiting for anyone to stop using it (using the -f option to
442 rmmod). This is mainly for kernel developers and desperate users.
445 config OBSOLETE_MODPARM
450 You need this option to use module parameters on modules which
451 have not been converted to the new module parameter system yet.
455 bool "Module versioning support (EXPERIMENTAL)"
456 depends on MODULES && EXPERIMENTAL
458 Usually, you have to use modules compiled with your kernel.
459 Saying Y here makes it sometimes possible to use modules
460 compiled for different kernels, by adding enough information
461 to the modules to (hopefully) spot any changes which would
462 make them incompatible with the kernel you are running. If
466 bool "Automatic kernel module loading"
469 Normally when you have selected some parts of the kernel to
470 be created as kernel modules, you must load them (using the
471 "modprobe" command) before you can use them. If you say Y
472 here, some parts of the kernel will be able to load modules
473 automatically: when a part of the kernel needs a module, it
474 runs modprobe with the appropriate arguments, thereby
475 loading the module if it is available. If unsure, say Y.
480 depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
482 Need stop_machine() primitive.