]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | menu "Code maturity level options" |
2 | ||
3 | config EXPERIMENTAL | |
4 | bool "Prompt for development and/or incomplete code/drivers" | |
5 | ---help--- | |
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). | |
22 | ||
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. | |
26 | ||
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. | |
33 | ||
34 | config CLEAN_COMPILE | |
35 | bool "Select only drivers expected to compile cleanly" if EXPERIMENTAL | |
36 | default y | |
37 | help | |
38 | Select this option if you don't even want to see the option | |
39 | to configure known-broken drivers. | |
40 | ||
41 | If unsure, say Y | |
42 | ||
43 | config BROKEN | |
44 | bool | |
45 | depends on !CLEAN_COMPILE | |
46 | default y | |
47 | ||
48 | config BROKEN_ON_SMP | |
49 | bool | |
50 | depends on BROKEN || !SMP | |
51 | default y | |
52 | ||
53 | config LOCK_KERNEL | |
54 | bool | |
55 | depends on SMP || PREEMPT | |
56 | default y | |
57 | ||
58 | config INIT_ENV_ARG_LIMIT | |
59 | int | |
60 | default 32 if !USERMODE | |
61 | default 128 if USERMODE | |
62 | help | |
34ad92c2 RD |
63 | Maximum of each of the number of arguments and environment |
64 | variables passed to init from the kernel command line. | |
1da177e4 LT |
65 | |
66 | endmenu | |
67 | ||
68 | menu "General setup" | |
69 | ||
70 | config LOCALVERSION | |
71 | string "Local version - append to kernel release" | |
72 | help | |
73 | Append an extra string to the end of your kernel version. | |
74 | This will show up when you type uname, for example. | |
75 | The string you set here will be appended after the contents of | |
76 | any files with a filename matching localversion* in your | |
77 | object and source tree, in that order. Your total string can | |
78 | be a maximum of 64 characters. | |
79 | ||
aaebf433 RA |
80 | config LOCALVERSION_AUTO |
81 | bool "Automatically append version information to the version string" | |
82 | default y | |
83 | help | |
84 | This will try to automatically determine if the current tree is a | |
85 | release tree by looking for git tags that | |
86 | belong to the current top of tree revision. | |
87 | ||
88 | A string of the format -gxxxxxxxx will be added to the localversion | |
89 | if a git based tree is found. The string generated by this will be | |
90 | appended after any matching localversion* files, and after the value | |
91 | set in CONFIG_LOCALVERSION | |
92 | ||
93 | Note: This requires Perl, and a git repository, but not necessarily | |
94 | the git or cogito tools to be installed. | |
95 | ||
1da177e4 LT |
96 | config SWAP |
97 | bool "Support for paging of anonymous memory (swap)" | |
98 | depends on MMU | |
99 | default y | |
100 | help | |
101 | This option allows you to choose whether you want to have support | |
102 | for socalled swap devices or swap files in your kernel that are | |
103 | used to provide more virtual memory than the actual RAM present | |
104 | in your computer. If unsure say Y. | |
105 | ||
106 | config SYSVIPC | |
107 | bool "System V IPC" | |
108 | depends on MMU | |
109 | ---help--- | |
110 | Inter Process Communication is a suite of library functions and | |
111 | system calls which let processes (running programs) synchronize and | |
112 | exchange information. It is generally considered to be a good thing, | |
113 | and some programs won't run unless you say Y here. In particular, if | |
114 | you want to run the DOS emulator dosemu under Linux (read the | |
115 | DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>), | |
116 | you'll need to say Y here. | |
117 | ||
118 | You can find documentation about IPC with "info ipc" and also in | |
119 | section 6.4 of the Linux Programmer's Guide, available from | |
120 | <http://www.tldp.org/guides.html>. | |
121 | ||
122 | config POSIX_MQUEUE | |
123 | bool "POSIX Message Queues" | |
124 | depends on NET && EXPERIMENTAL | |
125 | ---help--- | |
126 | POSIX variant of message queues is a part of IPC. In POSIX message | |
127 | queues every message has a priority which decides about succession | |
128 | of receiving it by a process. If you want to compile and run | |
129 | programs written e.g. for Solaris with use of its POSIX message | |
130 | queues (functions mq_*) say Y here. To use this feature you will | |
131 | also need mqueue library, available from | |
132 | <http://www.mat.uni.torun.pl/~wrona/posix_ipc/> | |
133 | ||
134 | POSIX message queues are visible as a filesystem called 'mqueue' | |
135 | and can be mounted somewhere if you want to do filesystem | |
136 | operations on message queues. | |
137 | ||
138 | If unsure, say Y. | |
139 | ||
140 | config BSD_PROCESS_ACCT | |
141 | bool "BSD Process Accounting" | |
142 | help | |
143 | If you say Y here, a user level program will be able to instruct the | |
144 | kernel (via a special system call) to write process accounting | |
145 | information to a file: whenever a process exits, information about | |
146 | that process will be appended to the file by the kernel. The | |
147 | information includes things such as creation time, owning user, | |
148 | command name, memory usage, controlling terminal etc. (the complete | |
149 | list is in the struct acct in <file:include/linux/acct.h>). It is | |
150 | up to the user level program to do useful things with this | |
151 | information. This is generally a good idea, so say Y. | |
152 | ||
153 | config BSD_PROCESS_ACCT_V3 | |
154 | bool "BSD Process Accounting version 3 file format" | |
155 | depends on BSD_PROCESS_ACCT | |
156 | default n | |
157 | help | |
158 | If you say Y here, the process accounting information is written | |
159 | in a new file format that also logs the process IDs of each | |
160 | process and it's parent. Note that this file format is incompatible | |
161 | with previous v0/v1/v2 file formats, so you will need updated tools | |
162 | for processing it. A preliminary version of these tools is available | |
163 | at <http://www.physik3.uni-rostock.de/tim/kernel/utils/acct/>. | |
164 | ||
165 | config SYSCTL | |
166 | bool "Sysctl support" | |
167 | ---help--- | |
168 | The sysctl interface provides a means of dynamically changing | |
169 | certain kernel parameters and variables on the fly without requiring | |
170 | a recompile of the kernel or reboot of the system. The primary | |
171 | interface consists of a system call, but if you say Y to "/proc | |
172 | file system support", a tree of modifiable sysctl entries will be | |
173 | generated beneath the /proc/sys directory. They are explained in the | |
174 | files in <file:Documentation/sysctl/>. Note that enabling this | |
175 | option will enlarge the kernel by at least 8 KB. | |
176 | ||
177 | As it is generally a good thing, you should say Y here unless | |
178 | building a kernel for install/rescue disks or your system is very | |
179 | limited in memory. | |
180 | ||
181 | config AUDIT | |
182 | bool "Auditing support" | |
804a6a49 | 183 | depends on NET |
1da177e4 LT |
184 | default y if SECURITY_SELINUX |
185 | help | |
186 | Enable auditing infrastructure that can be used with another | |
187 | kernel subsystem, such as SELinux (which requires this for | |
188 | logging of avc messages output). Does not do system-call | |
189 | auditing without CONFIG_AUDITSYSCALL. | |
190 | ||
191 | config AUDITSYSCALL | |
192 | bool "Enable system-call auditing support" | |
f7ceba36 | 193 | depends on AUDIT && (X86 || PPC || PPC64 || ARCH_S390 || IA64 || UML || SPARC64) |
1da177e4 LT |
194 | default y if SECURITY_SELINUX |
195 | help | |
196 | Enable low-overhead system-call auditing infrastructure that | |
197 | can be used independently or with another kernel subsystem, | |
198 | such as SELinux. | |
199 | ||
200 | config HOTPLUG | |
201 | bool "Support for hot-pluggable devices" if !ARCH_S390 | |
202 | default ARCH_S390 | |
203 | help | |
204 | This option is provided for the case where no in-kernel-tree | |
205 | modules require HOTPLUG functionality, but a module built | |
206 | outside the kernel tree does. Such modules require Y here. | |
207 | ||
1da177e4 LT |
208 | config IKCONFIG |
209 | bool "Kernel .config support" | |
210 | ---help--- | |
211 | This option enables the complete Linux kernel ".config" file | |
212 | contents to be saved in the kernel. It provides documentation | |
213 | of which kernel options are used in a running kernel or in an | |
214 | on-disk kernel. This information can be extracted from the kernel | |
215 | image file with the script scripts/extract-ikconfig and used as | |
216 | input to rebuild the current kernel or to build another kernel. | |
217 | It can also be extracted from a running kernel by reading | |
218 | /proc/config.gz if enabled (below). | |
219 | ||
220 | config IKCONFIG_PROC | |
221 | bool "Enable access to .config through /proc/config.gz" | |
222 | depends on IKCONFIG && PROC_FS | |
223 | ---help--- | |
224 | This option enables access to the kernel configuration file | |
225 | through /proc/config.gz. | |
226 | ||
227 | config CPUSETS | |
228 | bool "Cpuset support" | |
229 | depends on SMP | |
230 | help | |
d9fd8a6d | 231 | This option will let you create and manage CPUSETs which |
1da177e4 LT |
232 | allow dynamically partitioning a system into sets of CPUs and |
233 | Memory Nodes and assigning tasks to run only within those sets. | |
234 | This is primarily useful on large SMP or NUMA systems. | |
235 | ||
236 | Say N if unsure. | |
237 | ||
dbec4866 SR |
238 | source "usr/Kconfig" |
239 | ||
c45b4f1f LT |
240 | config CC_OPTIMIZE_FOR_SIZE |
241 | bool "Optimize for size (Look out for broken compilers!)" | |
242 | default y | |
243 | depends on ARM || H8300 || EXPERIMENTAL | |
c45b4f1f LT |
244 | help |
245 | Enabling this option will pass "-Os" instead of "-O2" to gcc | |
246 | resulting in a smaller kernel. | |
247 | ||
248 | WARNING: some versions of gcc may generate incorrect code with this | |
249 | option. If problems are observed, a gcc upgrade may be needed. | |
250 | ||
251 | If unsure, say N. | |
252 | ||
1da177e4 LT |
253 | menuconfig EMBEDDED |
254 | bool "Configure standard kernel features (for small systems)" | |
255 | help | |
256 | This option allows certain base kernel options and settings | |
257 | to be disabled or tweaked. This is for specialized | |
258 | environments which can tolerate a "non-standard" kernel. | |
259 | Only use this if you really know what you are doing. | |
260 | ||
261 | config KALLSYMS | |
262 | bool "Load all symbols for debugging/kksymoops" if EMBEDDED | |
263 | default y | |
264 | help | |
265 | Say Y here to let the kernel print out symbolic crash information and | |
266 | symbolic stack backtraces. This increases the size of the kernel | |
267 | somewhat, as all symbols have to be loaded into the kernel image. | |
268 | ||
269 | config KALLSYMS_ALL | |
270 | bool "Include all symbols in kallsyms" | |
271 | depends on DEBUG_KERNEL && KALLSYMS | |
272 | help | |
273 | Normally kallsyms only contains the symbols of functions, for nicer | |
274 | OOPS messages. Some debuggers can use kallsyms for other | |
f9f97bc0 JJ |
275 | symbols too: say Y here to include all symbols, if you need them |
276 | and you don't care about adding 300k to the size of your kernel. | |
1da177e4 LT |
277 | |
278 | Say N. | |
279 | ||
280 | config KALLSYMS_EXTRA_PASS | |
281 | bool "Do an extra kallsyms pass" | |
282 | depends on KALLSYMS | |
283 | help | |
284 | If kallsyms is not working correctly, the build will fail with | |
285 | inconsistent kallsyms data. If that occurs, log a bug report and | |
286 | turn on KALLSYMS_EXTRA_PASS which should result in a stable build. | |
287 | Always say N here unless you find a bug in kallsyms, which must be | |
288 | reported. KALLSYMS_EXTRA_PASS is only a temporary workaround while | |
289 | you wait for kallsyms to be fixed. | |
290 | ||
d59745ce MM |
291 | |
292 | config PRINTK | |
293 | default y | |
294 | bool "Enable support for printk" if EMBEDDED | |
295 | help | |
296 | This option enables normal printk support. Removing it | |
297 | eliminates most of the message strings from the kernel image | |
298 | and makes the kernel more or less silent. As this makes it | |
299 | very difficult to diagnose system problems, saying N here is | |
300 | strongly discouraged. | |
301 | ||
c8538a7a MM |
302 | config BUG |
303 | bool "BUG() support" if EMBEDDED | |
304 | default y | |
305 | help | |
306 | Disabling this option eliminates support for BUG and WARN, reducing | |
307 | the size of your kernel image and potentially quietly ignoring | |
308 | numerous fatal conditions. You should only consider disabling this | |
309 | option for embedded systems with no facilities for reporting errors. | |
310 | Just say Y. | |
311 | ||
1da177e4 LT |
312 | config BASE_FULL |
313 | default y | |
314 | bool "Enable full-sized data structures for core" if EMBEDDED | |
315 | help | |
316 | Disabling this option reduces the size of miscellaneous core | |
317 | kernel data structures. This saves memory on small machines, | |
318 | but may reduce performance. | |
319 | ||
320 | config FUTEX | |
321 | bool "Enable futex support" if EMBEDDED | |
322 | default y | |
323 | help | |
324 | Disabling this option will cause the kernel to be built without | |
325 | support for "fast userspace mutexes". The resulting kernel may not | |
326 | run glibc-based applications correctly. | |
327 | ||
328 | config EPOLL | |
329 | bool "Enable eventpoll support" if EMBEDDED | |
330 | default y | |
331 | help | |
332 | Disabling this option will cause the kernel to be built without | |
333 | support for epoll family of system calls. | |
334 | ||
1da177e4 LT |
335 | config SHMEM |
336 | bool "Use full shmem filesystem" if EMBEDDED | |
337 | default y | |
338 | depends on MMU | |
339 | help | |
340 | The shmem is an internal filesystem used to manage shared memory. | |
341 | It is backed by swap and manages resource limits. It is also exported | |
342 | to userspace as tmpfs if TMPFS is enabled. Disabling this | |
343 | option replaces shmem and tmpfs with the much simpler ramfs code, | |
344 | which may be appropriate on small systems without swap. | |
345 | ||
346 | config CC_ALIGN_FUNCTIONS | |
347 | int "Function alignment" if EMBEDDED | |
348 | default 0 | |
349 | help | |
350 | Align the start of functions to the next power-of-two greater than n, | |
351 | skipping up to n bytes. For instance, 32 aligns functions | |
352 | to the next 32-byte boundary, but 24 would align to the next | |
353 | 32-byte boundary only if this can be done by skipping 23 bytes or less. | |
354 | Zero means use compiler's default. | |
355 | ||
356 | config CC_ALIGN_LABELS | |
357 | int "Label alignment" if EMBEDDED | |
358 | default 0 | |
359 | help | |
360 | Align all branch targets to a power-of-two boundary, skipping | |
361 | up to n bytes like ALIGN_FUNCTIONS. This option can easily | |
362 | make code slower, because it must insert dummy operations for | |
363 | when the branch target is reached in the usual flow of the code. | |
364 | Zero means use compiler's default. | |
365 | ||
366 | config CC_ALIGN_LOOPS | |
367 | int "Loop alignment" if EMBEDDED | |
368 | default 0 | |
369 | help | |
370 | Align loops to a power-of-two boundary, skipping up to n bytes. | |
371 | Zero means use compiler's default. | |
372 | ||
373 | config CC_ALIGN_JUMPS | |
374 | int "Jump alignment" if EMBEDDED | |
375 | default 0 | |
376 | help | |
377 | Align branch targets to a power-of-two boundary, for branch | |
378 | targets where the targets can only be reached by jumping, | |
379 | skipping up to n bytes like ALIGN_FUNCTIONS. In this case, | |
380 | no dummy operations need be executed. | |
381 | Zero means use compiler's default. | |
382 | ||
383 | endmenu # General setup | |
384 | ||
385 | config TINY_SHMEM | |
386 | default !SHMEM | |
387 | bool | |
388 | ||
389 | config BASE_SMALL | |
390 | int | |
391 | default 0 if BASE_FULL | |
392 | default 1 if !BASE_FULL | |
393 | ||
394 | menu "Loadable module support" | |
395 | ||
396 | config MODULES | |
397 | bool "Enable loadable module support" | |
398 | help | |
399 | Kernel modules are small pieces of compiled code which can | |
400 | be inserted in the running kernel, rather than being | |
401 | permanently built into the kernel. You use the "modprobe" | |
402 | tool to add (and sometimes remove) them. If you say Y here, | |
403 | many parts of the kernel can be built as modules (by | |
404 | answering M instead of Y where indicated): this is most | |
405 | useful for infrequently used options which are not required | |
406 | for booting. For more information, see the man pages for | |
407 | modprobe, lsmod, modinfo, insmod and rmmod. | |
408 | ||
409 | If you say Y here, you will need to run "make | |
410 | modules_install" to put the modules under /lib/modules/ | |
411 | where modprobe can find them (you may need to be root to do | |
412 | this). | |
413 | ||
414 | If unsure, say Y. | |
415 | ||
416 | config MODULE_UNLOAD | |
417 | bool "Module unloading" | |
418 | depends on MODULES | |
419 | help | |
420 | Without this option you will not be able to unload any | |
421 | modules (note that some modules may not be unloadable | |
422 | anyway), which makes your kernel slightly smaller and | |
423 | simpler. If unsure, say Y. | |
424 | ||
425 | config MODULE_FORCE_UNLOAD | |
426 | bool "Forced module unloading" | |
427 | depends on MODULE_UNLOAD && EXPERIMENTAL | |
428 | help | |
429 | This option allows you to force a module to unload, even if the | |
430 | kernel believes it is unsafe: the kernel will remove the module | |
431 | without waiting for anyone to stop using it (using the -f option to | |
432 | rmmod). This is mainly for kernel developers and desperate users. | |
433 | If unsure, say N. | |
434 | ||
435 | config OBSOLETE_MODPARM | |
436 | bool | |
437 | default y | |
438 | depends on MODULES | |
439 | help | |
440 | You need this option to use module parameters on modules which | |
441 | have not been converted to the new module parameter system yet. | |
442 | If unsure, say Y. | |
443 | ||
444 | config MODVERSIONS | |
445 | bool "Module versioning support (EXPERIMENTAL)" | |
34a1a63e | 446 | depends on MODULES && EXPERIMENTAL |
1da177e4 LT |
447 | help |
448 | Usually, you have to use modules compiled with your kernel. | |
449 | Saying Y here makes it sometimes possible to use modules | |
450 | compiled for different kernels, by adding enough information | |
451 | to the modules to (hopefully) spot any changes which would | |
452 | make them incompatible with the kernel you are running. If | |
453 | unsure, say N. | |
454 | ||
455 | config MODULE_SRCVERSION_ALL | |
456 | bool "Source checksum for all modules" | |
457 | depends on MODULES | |
458 | help | |
459 | Modules which contain a MODULE_VERSION get an extra "srcversion" | |
460 | field inserted into their modinfo section, which contains a | |
461 | sum of the source files which made it. This helps maintainers | |
462 | see exactly which source was used to build a module (since | |
463 | others sometimes change the module source without updating | |
464 | the version). With this option, such a "srcversion" field | |
465 | will be created for all modules. If unsure, say N. | |
466 | ||
467 | config KMOD | |
468 | bool "Automatic kernel module loading" | |
469 | depends on MODULES | |
470 | help | |
471 | Normally when you have selected some parts of the kernel to | |
472 | be created as kernel modules, you must load them (using the | |
473 | "modprobe" command) before you can use them. If you say Y | |
474 | here, some parts of the kernel will be able to load modules | |
475 | automatically: when a part of the kernel needs a module, it | |
476 | runs modprobe with the appropriate arguments, thereby | |
477 | loading the module if it is available. If unsure, say Y. | |
478 | ||
479 | config STOP_MACHINE | |
480 | bool | |
481 | default y | |
482 | depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU | |
483 | help | |
484 | Need stop_machine() primitive. | |
485 | endmenu | |
3a65dfe8 JA |
486 | |
487 | menu "Block layer" | |
488 | source "block/Kconfig" | |
489 | endmenu |