]>
Commit | Line | Data |
---|---|---|
80daa560 RZ |
1 | config ARCH |
2 | string | |
3 | option env="ARCH" | |
4 | ||
5 | config KERNELVERSION | |
6 | string | |
7 | option env="KERNELVERSION" | |
8 | ||
face4374 RZ |
9 | config DEFCONFIG_LIST |
10 | string | |
b2670eac | 11 | depends on !UML |
face4374 RZ |
12 | option defconfig_list |
13 | default "/lib/modules/$UNAME_RELEASE/.config" | |
14 | default "/etc/kernel-config" | |
15 | default "/boot/config-$UNAME_RELEASE" | |
73531905 | 16 | default "$ARCH_DEFCONFIG" |
face4374 RZ |
17 | default "arch/$ARCH/defconfig" |
18 | ||
b99b87f7 PO |
19 | config CONSTRUCTORS |
20 | bool | |
21 | depends on !UML | |
b99b87f7 | 22 | |
e360adbe PZ |
23 | config IRQ_WORK |
24 | bool | |
e360adbe | 25 | |
1dbdc6f1 DD |
26 | config BUILDTIME_EXTABLE_SORT |
27 | bool | |
28 | ||
c65eacbe AL |
29 | config THREAD_INFO_IN_TASK |
30 | bool | |
31 | help | |
32 | Select this to move thread_info off the stack into task_struct. To | |
33 | make this work, an arch will need to remove all thread_info fields | |
34 | except flags and fix any runtime bugs. | |
35 | ||
ff0cfc66 | 36 | menu "General setup" |
1da177e4 | 37 | |
1da177e4 LT |
38 | config BROKEN |
39 | bool | |
1da177e4 LT |
40 | |
41 | config BROKEN_ON_SMP | |
42 | bool | |
43 | depends on BROKEN || !SMP | |
44 | default y | |
45 | ||
1da177e4 LT |
46 | config INIT_ENV_ARG_LIMIT |
47 | int | |
dd673bca AB |
48 | default 32 if !UML |
49 | default 128 if UML | |
1da177e4 | 50 | help |
34ad92c2 RD |
51 | Maximum of each of the number of arguments and environment |
52 | variables passed to init from the kernel command line. | |
1da177e4 | 53 | |
1da177e4 | 54 | |
84336466 RM |
55 | config CROSS_COMPILE |
56 | string "Cross-compiler tool prefix" | |
57 | help | |
58 | Same as running 'make CROSS_COMPILE=prefix-' but stored for | |
59 | default make runs in this kernel build directory. You don't | |
60 | need to set this unless you want the configured kernel build | |
61 | directory to select the cross-compiler automatically. | |
62 | ||
4bb16672 JS |
63 | config COMPILE_TEST |
64 | bool "Compile also drivers which will not load" | |
bc083a64 | 65 | depends on !UML |
4bb16672 JS |
66 | default n |
67 | help | |
68 | Some drivers can be compiled on a different platform than they are | |
69 | intended to be run on. Despite they cannot be loaded there (or even | |
70 | when they load they cannot be used due to missing HW support), | |
71 | developers still, opposing to distributors, might want to build such | |
72 | drivers to compile-test them. | |
73 | ||
74 | If you are a developer and want to build everything available, say Y | |
75 | here. If you are a user/distributor, say N here to exclude useless | |
76 | drivers to be distributed. | |
77 | ||
1da177e4 LT |
78 | config LOCALVERSION |
79 | string "Local version - append to kernel release" | |
80 | help | |
81 | Append an extra string to the end of your kernel version. | |
82 | This will show up when you type uname, for example. | |
83 | The string you set here will be appended after the contents of | |
84 | any files with a filename matching localversion* in your | |
85 | object and source tree, in that order. Your total string can | |
86 | be a maximum of 64 characters. | |
87 | ||
aaebf433 RA |
88 | config LOCALVERSION_AUTO |
89 | bool "Automatically append version information to the version string" | |
90 | default y | |
ac3339ba | 91 | depends on !COMPILE_TEST |
aaebf433 RA |
92 | help |
93 | This will try to automatically determine if the current tree is a | |
6e5a5420 RD |
94 | release tree by looking for git tags that belong to the current |
95 | top of tree revision. | |
aaebf433 RA |
96 | |
97 | A string of the format -gxxxxxxxx will be added to the localversion | |
6e5a5420 | 98 | if a git-based tree is found. The string generated by this will be |
aaebf433 | 99 | appended after any matching localversion* files, and after the value |
6e5a5420 | 100 | set in CONFIG_LOCALVERSION. |
aaebf433 | 101 | |
6e5a5420 RD |
102 | (The actual string used here is the first eight characters produced |
103 | by running the command: | |
104 | ||
105 | $ git rev-parse --verify HEAD | |
106 | ||
107 | which is done within the script "scripts/setlocalversion".) | |
aaebf433 | 108 | |
2e9f3bdd PA |
109 | config HAVE_KERNEL_GZIP |
110 | bool | |
111 | ||
112 | config HAVE_KERNEL_BZIP2 | |
113 | bool | |
114 | ||
115 | config HAVE_KERNEL_LZMA | |
116 | bool | |
117 | ||
3ebe1243 LC |
118 | config HAVE_KERNEL_XZ |
119 | bool | |
120 | ||
7dd65feb AT |
121 | config HAVE_KERNEL_LZO |
122 | bool | |
123 | ||
e76e1fdf KL |
124 | config HAVE_KERNEL_LZ4 |
125 | bool | |
126 | ||
30d65dbf | 127 | choice |
2e9f3bdd PA |
128 | prompt "Kernel compression mode" |
129 | default KERNEL_GZIP | |
2d3c6275 | 130 | depends on HAVE_KERNEL_GZIP || HAVE_KERNEL_BZIP2 || HAVE_KERNEL_LZMA || HAVE_KERNEL_XZ || HAVE_KERNEL_LZO || HAVE_KERNEL_LZ4 |
2e9f3bdd | 131 | help |
30d65dbf AK |
132 | The linux kernel is a kind of self-extracting executable. |
133 | Several compression algorithms are available, which differ | |
134 | in efficiency, compression and decompression speed. | |
135 | Compression speed is only relevant when building a kernel. | |
136 | Decompression speed is relevant at each boot. | |
137 | ||
138 | If you have any problems with bzip2 or lzma compressed | |
139 | kernels, mail me (Alain Knaff) <alain@knaff.lu>. (An older | |
140 | version of this functionality (bzip2 only), for 2.4, was | |
141 | supplied by Christian Ludwig) | |
142 | ||
143 | High compression options are mostly useful for users, who | |
144 | are low on disk space (embedded systems), but for whom ram | |
145 | size matters less. | |
146 | ||
147 | If in doubt, select 'gzip' | |
148 | ||
149 | config KERNEL_GZIP | |
2e9f3bdd PA |
150 | bool "Gzip" |
151 | depends on HAVE_KERNEL_GZIP | |
152 | help | |
7dd65feb AT |
153 | The old and tried gzip compression. It provides a good balance |
154 | between compression ratio and decompression speed. | |
30d65dbf AK |
155 | |
156 | config KERNEL_BZIP2 | |
157 | bool "Bzip2" | |
2e9f3bdd | 158 | depends on HAVE_KERNEL_BZIP2 |
30d65dbf AK |
159 | help |
160 | Its compression ratio and speed is intermediate. | |
0a4dd35c | 161 | Decompression speed is slowest among the choices. The kernel |
2e9f3bdd PA |
162 | size is about 10% smaller with bzip2, in comparison to gzip. |
163 | Bzip2 uses a large amount of memory. For modern kernels you | |
164 | will need at least 8MB RAM or more for booting. | |
30d65dbf AK |
165 | |
166 | config KERNEL_LZMA | |
2e9f3bdd PA |
167 | bool "LZMA" |
168 | depends on HAVE_KERNEL_LZMA | |
169 | help | |
0a4dd35c RD |
170 | This compression algorithm's ratio is best. Decompression speed |
171 | is between gzip and bzip2. Compression is slowest. | |
172 | The kernel size is about 33% smaller with LZMA in comparison to gzip. | |
30d65dbf | 173 | |
3ebe1243 LC |
174 | config KERNEL_XZ |
175 | bool "XZ" | |
176 | depends on HAVE_KERNEL_XZ | |
177 | help | |
178 | XZ uses the LZMA2 algorithm and instruction set specific | |
179 | BCJ filters which can improve compression ratio of executable | |
180 | code. The size of the kernel is about 30% smaller with XZ in | |
181 | comparison to gzip. On architectures for which there is a BCJ | |
182 | filter (i386, x86_64, ARM, IA-64, PowerPC, and SPARC), XZ | |
183 | will create a few percent smaller kernel than plain LZMA. | |
184 | ||
185 | The speed is about the same as with LZMA: The decompression | |
186 | speed of XZ is better than that of bzip2 but worse than gzip | |
187 | and LZO. Compression is slow. | |
188 | ||
7dd65feb AT |
189 | config KERNEL_LZO |
190 | bool "LZO" | |
191 | depends on HAVE_KERNEL_LZO | |
192 | help | |
0a4dd35c | 193 | Its compression ratio is the poorest among the choices. The kernel |
681b3049 | 194 | size is about 10% bigger than gzip; however its speed |
7dd65feb AT |
195 | (both compression and decompression) is the fastest. |
196 | ||
e76e1fdf KL |
197 | config KERNEL_LZ4 |
198 | bool "LZ4" | |
199 | depends on HAVE_KERNEL_LZ4 | |
200 | help | |
201 | LZ4 is an LZ77-type compressor with a fixed, byte-oriented encoding. | |
202 | A preliminary version of LZ4 de/compression tool is available at | |
203 | <https://code.google.com/p/lz4/>. | |
204 | ||
205 | Its compression ratio is worse than LZO. The size of the kernel | |
206 | is about 8% bigger than LZO. But the decompression speed is | |
207 | faster than LZO. | |
208 | ||
30d65dbf AK |
209 | endchoice |
210 | ||
bd5dc17b JT |
211 | config DEFAULT_HOSTNAME |
212 | string "Default hostname" | |
213 | default "(none)" | |
214 | help | |
215 | This option determines the default system hostname before userspace | |
216 | calls sethostname(2). The kernel traditionally uses "(none)" here, | |
217 | but you may wish to use a different default here to make a minimal | |
218 | system more usable with less configuration. | |
219 | ||
1da177e4 LT |
220 | config SWAP |
221 | bool "Support for paging of anonymous memory (swap)" | |
9361401e | 222 | depends on MMU && BLOCK |
1da177e4 LT |
223 | default y |
224 | help | |
225 | This option allows you to choose whether you want to have support | |
92c3504e | 226 | for so called swap devices or swap files in your kernel that are |
1da177e4 LT |
227 | used to provide more virtual memory than the actual RAM present |
228 | in your computer. If unsure say Y. | |
229 | ||
230 | config SYSVIPC | |
231 | bool "System V IPC" | |
1da177e4 LT |
232 | ---help--- |
233 | Inter Process Communication is a suite of library functions and | |
234 | system calls which let processes (running programs) synchronize and | |
235 | exchange information. It is generally considered to be a good thing, | |
236 | and some programs won't run unless you say Y here. In particular, if | |
237 | you want to run the DOS emulator dosemu under Linux (read the | |
238 | DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>), | |
239 | you'll need to say Y here. | |
240 | ||
241 | You can find documentation about IPC with "info ipc" and also in | |
242 | section 6.4 of the Linux Programmer's Guide, available from | |
243 | <http://www.tldp.org/guides.html>. | |
244 | ||
a5494dcd EB |
245 | config SYSVIPC_SYSCTL |
246 | bool | |
247 | depends on SYSVIPC | |
248 | depends on SYSCTL | |
249 | default y | |
250 | ||
1da177e4 LT |
251 | config POSIX_MQUEUE |
252 | bool "POSIX Message Queues" | |
19c92399 | 253 | depends on NET |
1da177e4 LT |
254 | ---help--- |
255 | POSIX variant of message queues is a part of IPC. In POSIX message | |
256 | queues every message has a priority which decides about succession | |
257 | of receiving it by a process. If you want to compile and run | |
258 | programs written e.g. for Solaris with use of its POSIX message | |
b0e37650 | 259 | queues (functions mq_*) say Y here. |
1da177e4 LT |
260 | |
261 | POSIX message queues are visible as a filesystem called 'mqueue' | |
262 | and can be mounted somewhere if you want to do filesystem | |
263 | operations on message queues. | |
264 | ||
265 | If unsure, say Y. | |
266 | ||
bdc8e5f8 SH |
267 | config POSIX_MQUEUE_SYSCTL |
268 | bool | |
269 | depends on POSIX_MQUEUE | |
270 | depends on SYSCTL | |
271 | default y | |
272 | ||
226b4ccd KK |
273 | config CROSS_MEMORY_ATTACH |
274 | bool "Enable process_vm_readv/writev syscalls" | |
275 | depends on MMU | |
276 | default y | |
277 | help | |
278 | Enabling this option adds the system calls process_vm_readv and | |
279 | process_vm_writev which allow a process with the correct privileges | |
a2a368d9 | 280 | to directly read from or write to another process' address space. |
226b4ccd KK |
281 | See the man page for more details. |
282 | ||
391dc69c | 283 | config FHANDLE |
f76be617 | 284 | bool "open by fhandle syscalls" if EXPERT |
391dc69c | 285 | select EXPORTFS |
f76be617 | 286 | default y |
391dc69c FW |
287 | help |
288 | If you say Y here, a user level program will be able to map | |
289 | file names to handle and then later use the handle for | |
290 | different file system operations. This is useful in implementing | |
291 | userspace file servers, which now track files using handles instead | |
292 | of names. The handle would remain the same even if file names | |
293 | get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2) | |
294 | syscalls. | |
295 | ||
69369a70 JT |
296 | config USELIB |
297 | bool "uselib syscall" | |
b2113a41 | 298 | def_bool ALPHA || M68K || SPARC || X86_32 || IA32_EMULATION |
69369a70 JT |
299 | help |
300 | This option enables the uselib syscall, a system call used in the | |
301 | dynamic linker from libc5 and earlier. glibc does not use this | |
302 | system call. If you intend to run programs built on libc5 or | |
303 | earlier, you may need to enable this syscall. Current systems | |
304 | running glibc can safely disable this. | |
305 | ||
391dc69c FW |
306 | config AUDIT |
307 | bool "Auditing support" | |
308 | depends on NET | |
309 | help | |
310 | Enable auditing infrastructure that can be used with another | |
311 | kernel subsystem, such as SELinux (which requires this for | |
cb74ed27 PM |
312 | logging of avc messages output). System call auditing is included |
313 | on architectures which support it. | |
391dc69c | 314 | |
7a017721 AT |
315 | config HAVE_ARCH_AUDITSYSCALL |
316 | bool | |
317 | ||
391dc69c | 318 | config AUDITSYSCALL |
cb74ed27 | 319 | def_bool y |
7a017721 | 320 | depends on AUDIT && HAVE_ARCH_AUDITSYSCALL |
391dc69c FW |
321 | |
322 | config AUDIT_WATCH | |
323 | def_bool y | |
324 | depends on AUDITSYSCALL | |
325 | select FSNOTIFY | |
326 | ||
327 | config AUDIT_TREE | |
328 | def_bool y | |
329 | depends on AUDITSYSCALL | |
330 | select FSNOTIFY | |
331 | ||
391dc69c FW |
332 | source "kernel/irq/Kconfig" |
333 | source "kernel/time/Kconfig" | |
334 | ||
335 | menu "CPU/Task time and stats accounting" | |
336 | ||
abf917cd FW |
337 | config VIRT_CPU_ACCOUNTING |
338 | bool | |
339 | ||
fdf9c356 FW |
340 | choice |
341 | prompt "Cputime accounting" | |
342 | default TICK_CPU_ACCOUNTING if !PPC64 | |
02fc8d37 | 343 | default VIRT_CPU_ACCOUNTING_NATIVE if PPC64 |
fdf9c356 FW |
344 | |
345 | # Kind of a stub config for the pure tick based cputime accounting | |
346 | config TICK_CPU_ACCOUNTING | |
347 | bool "Simple tick based cputime accounting" | |
c58b0df1 | 348 | depends on !S390 && !NO_HZ_FULL |
fdf9c356 FW |
349 | help |
350 | This is the basic tick based cputime accounting that maintains | |
351 | statistics about user, system and idle time spent on per jiffies | |
352 | granularity. | |
353 | ||
354 | If unsure, say Y. | |
355 | ||
abf917cd | 356 | config VIRT_CPU_ACCOUNTING_NATIVE |
b952741c | 357 | bool "Deterministic task and CPU time accounting" |
c58b0df1 | 358 | depends on HAVE_VIRT_CPU_ACCOUNTING && !NO_HZ_FULL |
abf917cd | 359 | select VIRT_CPU_ACCOUNTING |
b952741c FW |
360 | help |
361 | Select this option to enable more accurate task and CPU time | |
362 | accounting. This is done by reading a CPU counter on each | |
363 | kernel entry and exit and on transitions within the kernel | |
364 | between system, softirq and hardirq state, so there is a | |
365 | small performance impact. In the case of s390 or IBM POWER > 5, | |
366 | this also enables accounting of stolen time on logically-partitioned | |
367 | systems. | |
368 | ||
abf917cd FW |
369 | config VIRT_CPU_ACCOUNTING_GEN |
370 | bool "Full dynticks CPU time accounting" | |
ff3fb254 | 371 | depends on HAVE_CONTEXT_TRACKING |
554b0004 | 372 | depends on HAVE_VIRT_CPU_ACCOUNTING_GEN |
abf917cd FW |
373 | select VIRT_CPU_ACCOUNTING |
374 | select CONTEXT_TRACKING | |
375 | help | |
376 | Select this option to enable task and CPU time accounting on full | |
377 | dynticks systems. This accounting is implemented by watching every | |
378 | kernel-user boundaries using the context tracking subsystem. | |
379 | The accounting is thus performed at the expense of some significant | |
380 | overhead. | |
381 | ||
382 | For now this is only useful if you are working on the full | |
383 | dynticks subsystem development. | |
384 | ||
385 | If unsure, say N. | |
386 | ||
b58c3584 RR |
387 | endchoice |
388 | ||
fdf9c356 FW |
389 | config IRQ_TIME_ACCOUNTING |
390 | bool "Fine granularity task level IRQ time accounting" | |
b58c3584 | 391 | depends on HAVE_IRQ_TIME_ACCOUNTING && !VIRT_CPU_ACCOUNTING_NATIVE |
fdf9c356 FW |
392 | help |
393 | Select this option to enable fine granularity task irq time | |
394 | accounting. This is done by reading a timestamp on each | |
395 | transitions between softirq and hardirq state, so there can be a | |
396 | small performance impact. | |
397 | ||
398 | If in doubt, say N here. | |
399 | ||
1da177e4 LT |
400 | config BSD_PROCESS_ACCT |
401 | bool "BSD Process Accounting" | |
2813893f | 402 | depends on MULTIUSER |
1da177e4 LT |
403 | help |
404 | If you say Y here, a user level program will be able to instruct the | |
405 | kernel (via a special system call) to write process accounting | |
406 | information to a file: whenever a process exits, information about | |
407 | that process will be appended to the file by the kernel. The | |
408 | information includes things such as creation time, owning user, | |
409 | command name, memory usage, controlling terminal etc. (the complete | |
410 | list is in the struct acct in <file:include/linux/acct.h>). It is | |
411 | up to the user level program to do useful things with this | |
412 | information. This is generally a good idea, so say Y. | |
413 | ||
414 | config BSD_PROCESS_ACCT_V3 | |
415 | bool "BSD Process Accounting version 3 file format" | |
416 | depends on BSD_PROCESS_ACCT | |
417 | default n | |
418 | help | |
419 | If you say Y here, the process accounting information is written | |
420 | in a new file format that also logs the process IDs of each | |
421 | process and it's parent. Note that this file format is incompatible | |
422 | with previous v0/v1/v2 file formats, so you will need updated tools | |
423 | for processing it. A preliminary version of these tools is available | |
37a4c940 | 424 | at <http://www.gnu.org/software/acct/>. |
1da177e4 | 425 | |
c757249a | 426 | config TASKSTATS |
19c92399 | 427 | bool "Export task/process statistics through netlink" |
c757249a | 428 | depends on NET |
2813893f | 429 | depends on MULTIUSER |
c757249a SN |
430 | default n |
431 | help | |
432 | Export selected statistics for tasks/processes through the | |
433 | generic netlink interface. Unlike BSD process accounting, the | |
434 | statistics are available during the lifetime of tasks/processes as | |
435 | responses to commands. Like BSD accounting, they are sent to user | |
436 | space on task exit. | |
437 | ||
438 | Say N if unsure. | |
439 | ||
ca74e92b | 440 | config TASK_DELAY_ACCT |
19c92399 | 441 | bool "Enable per-task delay accounting" |
6f44993f | 442 | depends on TASKSTATS |
f6db8347 | 443 | select SCHED_INFO |
ca74e92b SN |
444 | help |
445 | Collect information on time spent by a task waiting for system | |
446 | resources like cpu, synchronous block I/O completion and swapping | |
447 | in pages. Such statistics can help in setting a task's priorities | |
448 | relative to other tasks for cpu, io, rss limits etc. | |
449 | ||
450 | Say N if unsure. | |
451 | ||
18f705f4 | 452 | config TASK_XACCT |
19c92399 | 453 | bool "Enable extended accounting over taskstats" |
18f705f4 AD |
454 | depends on TASKSTATS |
455 | help | |
456 | Collect extended task accounting data and send the data | |
457 | to userland for processing over the taskstats interface. | |
458 | ||
459 | Say N if unsure. | |
460 | ||
461 | config TASK_IO_ACCOUNTING | |
19c92399 | 462 | bool "Enable per-task storage I/O accounting" |
18f705f4 AD |
463 | depends on TASK_XACCT |
464 | help | |
465 | Collect information on the number of bytes of storage I/O which this | |
466 | task has caused. | |
467 | ||
468 | Say N if unsure. | |
469 | ||
391dc69c | 470 | endmenu # "CPU/Task time and stats accounting" |
d9817ebe | 471 | |
c903ff83 MT |
472 | menu "RCU Subsystem" |
473 | ||
c903ff83 | 474 | config TREE_RCU |
e72aeafc PK |
475 | bool |
476 | default y if !PREEMPT && SMP | |
c903ff83 MT |
477 | help |
478 | This option selects the RCU implementation that is | |
479 | designed for very large SMP system with hundreds or | |
c17ef453 PM |
480 | thousands of CPUs. It also scales down nicely to |
481 | smaller systems. | |
c903ff83 | 482 | |
28f6569a | 483 | config PREEMPT_RCU |
e72aeafc PK |
484 | bool |
485 | default y if PREEMPT | |
f41d911f PM |
486 | help |
487 | This option selects the RCU implementation that is | |
488 | designed for very large SMP systems with hundreds or | |
489 | thousands of CPUs, but for which real-time response | |
bbe3eae8 PM |
490 | is also required. It also scales down nicely to |
491 | smaller systems. | |
f41d911f | 492 | |
9fc52d83 PM |
493 | Select this option if you are unsure. |
494 | ||
9b1d82fa | 495 | config TINY_RCU |
e72aeafc PK |
496 | bool |
497 | default y if !PREEMPT && !SMP | |
9b1d82fa PM |
498 | help |
499 | This option selects the RCU implementation that is | |
500 | designed for UP systems from which real-time response | |
501 | is not required. This option greatly reduces the | |
502 | memory footprint of RCU. | |
503 | ||
78cae10b PM |
504 | config RCU_EXPERT |
505 | bool "Make expert-level adjustments to RCU configuration" | |
506 | default n | |
507 | help | |
508 | This option needs to be enabled if you wish to make | |
509 | expert-level adjustments to RCU configuration. By default, | |
510 | no such adjustments can be made, which has the often-beneficial | |
511 | side-effect of preventing "make oldconfig" from asking you all | |
512 | sorts of detailed questions about how you would like numerous | |
513 | obscure RCU options to be set up. | |
514 | ||
515 | Say Y if you need to make expert-level adjustments to RCU. | |
516 | ||
517 | Say N if you are unsure. | |
518 | ||
83fe27ea PK |
519 | config SRCU |
520 | bool | |
521 | help | |
522 | This option selects the sleepable version of RCU. This version | |
523 | permits arbitrary sleeping or blocking within RCU read-side critical | |
524 | sections. | |
525 | ||
8315f422 | 526 | config TASKS_RCU |
82d0f4c0 | 527 | bool |
8315f422 | 528 | default n |
570dd3c7 | 529 | depends on !UML |
83fe27ea | 530 | select SRCU |
8315f422 PM |
531 | help |
532 | This option enables a task-based RCU implementation that uses | |
533 | only voluntary context switch (not preemption!), idle, and | |
534 | user-mode execution as quiescent states. | |
535 | ||
6bfc09e2 | 536 | config RCU_STALL_COMMON |
28f6569a | 537 | def_bool ( TREE_RCU || PREEMPT_RCU || RCU_TRACE ) |
6bfc09e2 PM |
538 | help |
539 | This option enables RCU CPU stall code that is common between | |
540 | the TINY and TREE variants of RCU. The purpose is to allow | |
541 | the tiny variants to disable RCU CPU stall warnings, while | |
542 | making these warnings mandatory for the tree variants. | |
543 | ||
91d1aa43 FW |
544 | config CONTEXT_TRACKING |
545 | bool | |
546 | ||
91d1aa43 FW |
547 | config CONTEXT_TRACKING_FORCE |
548 | bool "Force context tracking" | |
549 | depends on CONTEXT_TRACKING | |
d84d27a4 | 550 | default y if !NO_HZ_FULL |
1fd2b442 | 551 | help |
d84d27a4 FW |
552 | The major pre-requirement for full dynticks to work is to |
553 | support the context tracking subsystem. But there are also | |
554 | other dependencies to provide in order to make the full | |
555 | dynticks working. | |
556 | ||
557 | This option stands for testing when an arch implements the | |
558 | context tracking backend but doesn't yet fullfill all the | |
559 | requirements to make the full dynticks feature working. | |
560 | Without the full dynticks, there is no way to test the support | |
561 | for context tracking and the subsystems that rely on it: RCU | |
562 | userspace extended quiescent state and tickless cputime | |
563 | accounting. This option copes with the absence of the full | |
564 | dynticks subsystem by forcing the context tracking on all | |
565 | CPUs in the system. | |
566 | ||
99c8b1ea | 567 | Say Y only if you're working on the development of an |
d84d27a4 FW |
568 | architecture backend for the context tracking. |
569 | ||
570 | Say N otherwise, this option brings an overhead that you | |
571 | don't want in production. | |
572 | ||
d677124b | 573 | |
c903ff83 MT |
574 | config RCU_FANOUT |
575 | int "Tree-based hierarchical RCU fanout value" | |
576 | range 2 64 if 64BIT | |
577 | range 2 32 if !64BIT | |
05c5df31 | 578 | depends on (TREE_RCU || PREEMPT_RCU) && RCU_EXPERT |
c903ff83 MT |
579 | default 64 if 64BIT |
580 | default 32 if !64BIT | |
581 | help | |
582 | This option controls the fanout of hierarchical implementations | |
583 | of RCU, allowing RCU to work efficiently on machines with | |
4d87ffad PM |
584 | large numbers of CPUs. This value must be at least the fourth |
585 | root of NR_CPUS, which allows NR_CPUS to be insanely large. | |
586 | The default value of RCU_FANOUT should be used for production | |
587 | systems, but if you are stress-testing the RCU implementation | |
588 | itself, small RCU_FANOUT values allow you to test large-system | |
589 | code paths on small(er) systems. | |
c903ff83 MT |
590 | |
591 | Select a specific number if testing RCU itself. | |
592 | Take the default if unsure. | |
593 | ||
8932a63d PM |
594 | config RCU_FANOUT_LEAF |
595 | int "Tree-based hierarchical RCU leaf-level fanout value" | |
8739c5cb PM |
596 | range 2 64 if 64BIT |
597 | range 2 32 if !64BIT | |
47d631af | 598 | depends on (TREE_RCU || PREEMPT_RCU) && RCU_EXPERT |
8932a63d PM |
599 | default 16 |
600 | help | |
601 | This option controls the leaf-level fanout of hierarchical | |
602 | implementations of RCU, and allows trading off cache misses | |
603 | against lock contention. Systems that synchronize their | |
604 | scheduling-clock interrupts for energy-efficiency reasons will | |
605 | want the default because the smaller leaf-level fanout keeps | |
606 | lock contention levels acceptably low. Very large systems | |
607 | (hundreds or thousands of CPUs) will instead want to set this | |
608 | value to the maximum value possible in order to reduce the | |
609 | number of cache misses incurred during RCU's grace-period | |
610 | initialization. These systems tend to run CPU-bound, and thus | |
611 | are not helped by synchronized interrupts, and thus tend to | |
612 | skew them, which reduces lock contention enough that large | |
613 | leaf-level fanouts work well. | |
614 | ||
615 | Select a specific number if testing RCU itself. | |
616 | ||
617 | Select the maximum permissible value for large systems. | |
618 | ||
619 | Take the default if unsure. | |
620 | ||
8bd93a2c PM |
621 | config RCU_FAST_NO_HZ |
622 | bool "Accelerate last non-dyntick-idle CPU's grace periods" | |
78cae10b | 623 | depends on NO_HZ_COMMON && SMP && RCU_EXPERT |
8bd93a2c PM |
624 | default n |
625 | help | |
c0f4dfd4 PM |
626 | This option permits CPUs to enter dynticks-idle state even if |
627 | they have RCU callbacks queued, and prevents RCU from waking | |
628 | these CPUs up more than roughly once every four jiffies (by | |
629 | default, you can adjust this using the rcutree.rcu_idle_gp_delay | |
630 | parameter), thus improving energy efficiency. On the other | |
631 | hand, this option increases the duration of RCU grace periods, | |
632 | for example, slowing down synchronize_rcu(). | |
ba49df47 | 633 | |
c0f4dfd4 PM |
634 | Say Y if energy efficiency is critically important, and you |
635 | don't care about increased grace-period durations. | |
8bd93a2c PM |
636 | |
637 | Say N if you are unsure. | |
638 | ||
c903ff83 | 639 | config TREE_RCU_TRACE |
28f6569a | 640 | def_bool RCU_TRACE && ( TREE_RCU || PREEMPT_RCU ) |
c903ff83 MT |
641 | select DEBUG_FS |
642 | help | |
f41d911f | 643 | This option provides tracing for the TREE_RCU and |
28f6569a | 644 | PREEMPT_RCU implementations, permitting Makefile to |
f41d911f | 645 | trivially select kernel/rcutree_trace.c. |
c903ff83 | 646 | |
24278d14 PM |
647 | config RCU_BOOST |
648 | bool "Enable RCU priority boosting" | |
78cae10b | 649 | depends on RT_MUTEXES && PREEMPT_RCU && RCU_EXPERT |
24278d14 PM |
650 | default n |
651 | help | |
652 | This option boosts the priority of preempted RCU readers that | |
653 | block the current preemptible RCU grace period for too long. | |
654 | This option also prevents heavy loads from blocking RCU | |
655 | callback invocation for all flavors of RCU. | |
656 | ||
657 | Say Y here if you are working with real-time apps or heavy loads | |
658 | Say N here if you are unsure. | |
659 | ||
21871d7e CW |
660 | config RCU_KTHREAD_PRIO |
661 | int "Real-time priority to use for RCU worker threads" | |
a94844b2 PM |
662 | range 1 99 if RCU_BOOST |
663 | range 0 99 if !RCU_BOOST | |
664 | default 1 if RCU_BOOST | |
665 | default 0 if !RCU_BOOST | |
26730f55 | 666 | depends on RCU_EXPERT |
24278d14 | 667 | help |
21871d7e CW |
668 | This option specifies the SCHED_FIFO priority value that will be |
669 | assigned to the rcuc/n and rcub/n threads and is also the value | |
670 | used for RCU_BOOST (if enabled). If you are working with a | |
671 | real-time application that has one or more CPU-bound threads | |
672 | running at a real-time priority level, you should set | |
673 | RCU_KTHREAD_PRIO to a priority higher than the highest-priority | |
674 | real-time CPU-bound application thread. The default RCU_KTHREAD_PRIO | |
675 | value of 1 is appropriate in the common case, which is real-time | |
c9336643 PM |
676 | applications that do not have any CPU-bound threads. |
677 | ||
678 | Some real-time applications might not have a single real-time | |
679 | thread that saturates a given CPU, but instead might have | |
680 | multiple real-time threads that, taken together, fully utilize | |
21871d7e | 681 | that CPU. In this case, you should set RCU_KTHREAD_PRIO to |
c9336643 PM |
682 | a priority higher than the lowest-priority thread that is |
683 | conspiring to prevent the CPU from running any non-real-time | |
684 | tasks. For example, if one thread at priority 10 and another | |
685 | thread at priority 5 are between themselves fully consuming | |
21871d7e | 686 | the CPU time on a given CPU, then RCU_KTHREAD_PRIO should be |
c9336643 | 687 | set to priority 6 or higher. |
24278d14 PM |
688 | |
689 | Specify the real-time priority, or take the default if unsure. | |
690 | ||
691 | config RCU_BOOST_DELAY | |
692 | int "Milliseconds to delay boosting after RCU grace-period start" | |
693 | range 0 3000 | |
694 | depends on RCU_BOOST | |
695 | default 500 | |
696 | help | |
697 | This option specifies the time to wait after the beginning of | |
698 | a given grace period before priority-boosting preempted RCU | |
699 | readers blocking that grace period. Note that any RCU reader | |
700 | blocking an expedited RCU grace period is boosted immediately. | |
701 | ||
702 | Accept the default if unsure. | |
703 | ||
3fbfbf7a | 704 | config RCU_NOCB_CPU |
9a5739d7 | 705 | bool "Offload RCU callback processing from boot-selected CPUs" |
28f6569a | 706 | depends on TREE_RCU || PREEMPT_RCU |
be55fa2a | 707 | depends on RCU_EXPERT || NO_HZ_FULL |
3fbfbf7a PM |
708 | default n |
709 | help | |
710 | Use this option to reduce OS jitter for aggressive HPC or | |
711 | real-time workloads. It can also be used to offload RCU | |
712 | callback invocation to energy-efficient CPUs in battery-powered | |
713 | asymmetric multiprocessors. | |
714 | ||
715 | This option offloads callback invocation from the set of | |
716 | CPUs specified at boot time by the rcu_nocbs parameter. | |
a4889858 PM |
717 | For each such CPU, a kthread ("rcuox/N") will be created to |
718 | invoke callbacks, where the "N" is the CPU being offloaded, | |
719 | and where the "x" is "b" for RCU-bh, "p" for RCU-preempt, and | |
720 | "s" for RCU-sched. Nothing prevents this kthread from running | |
721 | on the specified CPUs, but (1) the kthreads may be preempted | |
722 | between each callback, and (2) affinity or cgroups can be used | |
723 | to force the kthreads to run on whatever set of CPUs is desired. | |
3fbfbf7a | 724 | |
34ed6246 | 725 | Say Y here if you want to help to debug reduced OS jitter. |
3fbfbf7a PM |
726 | Say N here if you are unsure. |
727 | ||
911af505 PM |
728 | choice |
729 | prompt "Build-forced no-CBs CPUs" | |
730 | default RCU_NOCB_CPU_NONE | |
4568779f | 731 | depends on RCU_NOCB_CPU |
911af505 | 732 | help |
676c3dc2 PM |
733 | This option allows no-CBs CPUs (whose RCU callbacks are invoked |
734 | from kthreads rather than from softirq context) to be specified | |
735 | at build time. Additional no-CBs CPUs may be specified by | |
736 | the rcu_nocbs= boot parameter. | |
911af505 PM |
737 | |
738 | config RCU_NOCB_CPU_NONE | |
739 | bool "No build_forced no-CBs CPUs" | |
911af505 PM |
740 | help |
741 | This option does not force any of the CPUs to be no-CBs CPUs. | |
742 | Only CPUs designated by the rcu_nocbs= boot parameter will be | |
676c3dc2 PM |
743 | no-CBs CPUs, whose RCU callbacks will be invoked by per-CPU |
744 | kthreads whose names begin with "rcuo". All other CPUs will | |
745 | invoke their own RCU callbacks in softirq context. | |
746 | ||
747 | Select this option if you want to choose no-CBs CPUs at | |
748 | boot time, for example, to allow testing of different no-CBs | |
749 | configurations without having to rebuild the kernel each time. | |
911af505 PM |
750 | |
751 | config RCU_NOCB_CPU_ZERO | |
752 | bool "CPU 0 is a build_forced no-CBs CPU" | |
911af505 | 753 | help |
676c3dc2 PM |
754 | This option forces CPU 0 to be a no-CBs CPU, so that its RCU |
755 | callbacks are invoked by a per-CPU kthread whose name begins | |
756 | with "rcuo". Additional CPUs may be designated as no-CBs | |
757 | CPUs using the rcu_nocbs= boot parameter will be no-CBs CPUs. | |
758 | All other CPUs will invoke their own RCU callbacks in softirq | |
759 | context. | |
911af505 PM |
760 | |
761 | Select this if CPU 0 needs to be a no-CBs CPU for real-time | |
676c3dc2 PM |
762 | or energy-efficiency reasons, but the real reason it exists |
763 | is to ensure that randconfig testing covers mixed systems. | |
911af505 PM |
764 | |
765 | config RCU_NOCB_CPU_ALL | |
766 | bool "All CPUs are build_forced no-CBs CPUs" | |
911af505 PM |
767 | help |
768 | This option forces all CPUs to be no-CBs CPUs. The rcu_nocbs= | |
676c3dc2 PM |
769 | boot parameter will be ignored. All CPUs' RCU callbacks will |
770 | be executed in the context of per-CPU rcuo kthreads created for | |
771 | this purpose. Assuming that the kthreads whose names start with | |
772 | "rcuo" are bound to "housekeeping" CPUs, this reduces OS jitter | |
773 | on the remaining CPUs, but might decrease memory locality during | |
774 | RCU-callback invocation, thus potentially degrading throughput. | |
911af505 PM |
775 | |
776 | Select this if all CPUs need to be no-CBs CPUs for real-time | |
777 | or energy-efficiency reasons. | |
778 | ||
779 | endchoice | |
780 | ||
ee42571f PM |
781 | config RCU_EXPEDITE_BOOT |
782 | bool | |
783 | default n | |
784 | help | |
785 | This option enables expedited grace periods at boot time, | |
786 | as if rcu_expedite_gp() had been invoked early in boot. | |
787 | The corresponding rcu_unexpedite_gp() is invoked from | |
788 | rcu_end_inkernel_boot(), which is intended to be invoked | |
789 | at the end of the kernel-only boot sequence, just before | |
790 | init is exec'ed. | |
791 | ||
792 | Accept the default if unsure. | |
793 | ||
c903ff83 MT |
794 | endmenu # "RCU Subsystem" |
795 | ||
de5b56ba VG |
796 | config BUILD_BIN2C |
797 | bool | |
798 | default n | |
799 | ||
1da177e4 | 800 | config IKCONFIG |
f2443ab6 | 801 | tristate "Kernel .config support" |
de5b56ba | 802 | select BUILD_BIN2C |
1da177e4 LT |
803 | ---help--- |
804 | This option enables the complete Linux kernel ".config" file | |
805 | contents to be saved in the kernel. It provides documentation | |
806 | of which kernel options are used in a running kernel or in an | |
807 | on-disk kernel. This information can be extracted from the kernel | |
808 | image file with the script scripts/extract-ikconfig and used as | |
809 | input to rebuild the current kernel or to build another kernel. | |
810 | It can also be extracted from a running kernel by reading | |
811 | /proc/config.gz if enabled (below). | |
812 | ||
813 | config IKCONFIG_PROC | |
814 | bool "Enable access to .config through /proc/config.gz" | |
815 | depends on IKCONFIG && PROC_FS | |
816 | ---help--- | |
817 | This option enables access to the kernel configuration file | |
818 | through /proc/config.gz. | |
819 | ||
794543a2 AJS |
820 | config LOG_BUF_SHIFT |
821 | int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" | |
fb39f98d | 822 | range 12 25 |
f17a32e9 | 823 | default 17 |
361e9dfb | 824 | depends on PRINTK |
794543a2 | 825 | help |
23b2899f LR |
826 | Select the minimal kernel log buffer size as a power of 2. |
827 | The final size is affected by LOG_CPU_MAX_BUF_SHIFT config | |
828 | parameter, see below. Any higher size also might be forced | |
829 | by "log_buf_len" boot parameter. | |
830 | ||
f17a32e9 | 831 | Examples: |
23b2899f | 832 | 17 => 128 KB |
f17a32e9 | 833 | 16 => 64 KB |
23b2899f LR |
834 | 15 => 32 KB |
835 | 14 => 16 KB | |
794543a2 AJS |
836 | 13 => 8 KB |
837 | 12 => 4 KB | |
838 | ||
23b2899f LR |
839 | config LOG_CPU_MAX_BUF_SHIFT |
840 | int "CPU kernel log buffer size contribution (13 => 8 KB, 17 => 128KB)" | |
2240a31d | 841 | depends on SMP |
23b2899f LR |
842 | range 0 21 |
843 | default 12 if !BASE_SMALL | |
844 | default 0 if BASE_SMALL | |
361e9dfb | 845 | depends on PRINTK |
23b2899f LR |
846 | help |
847 | This option allows to increase the default ring buffer size | |
848 | according to the number of CPUs. The value defines the contribution | |
849 | of each CPU as a power of 2. The used space is typically only few | |
850 | lines however it might be much more when problems are reported, | |
851 | e.g. backtraces. | |
852 | ||
853 | The increased size means that a new buffer has to be allocated and | |
854 | the original static one is unused. It makes sense only on systems | |
855 | with more CPUs. Therefore this value is used only when the sum of | |
856 | contributions is greater than the half of the default kernel ring | |
857 | buffer as defined by LOG_BUF_SHIFT. The default values are set | |
858 | so that more than 64 CPUs are needed to trigger the allocation. | |
859 | ||
860 | Also this option is ignored when "log_buf_len" kernel parameter is | |
861 | used as it forces an exact (power of two) size of the ring buffer. | |
862 | ||
863 | The number of possible CPUs is used for this computation ignoring | |
5e0d8d59 GU |
864 | hotplugging making the computation optimal for the worst case |
865 | scenario while allowing a simple algorithm to be used from bootup. | |
23b2899f LR |
866 | |
867 | Examples shift values and their meaning: | |
868 | 17 => 128 KB for each CPU | |
869 | 16 => 64 KB for each CPU | |
870 | 15 => 32 KB for each CPU | |
871 | 14 => 16 KB for each CPU | |
872 | 13 => 8 KB for each CPU | |
873 | 12 => 4 KB for each CPU | |
874 | ||
427934b8 PM |
875 | config NMI_LOG_BUF_SHIFT |
876 | int "Temporary per-CPU NMI log buffer size (12 => 4KB, 13 => 8KB)" | |
877 | range 10 21 | |
878 | default 13 | |
879 | depends on PRINTK_NMI | |
880 | help | |
881 | Select the size of a per-CPU buffer where NMI messages are temporary | |
882 | stored. They are copied to the main log buffer in a safe context | |
883 | to avoid a deadlock. The value defines the size as a power of 2. | |
884 | ||
885 | NMI messages are rare and limited. The largest one is when | |
886 | a backtrace is printed. It usually fits into 4KB. Select | |
887 | 8KB if you want to be on the safe side. | |
888 | ||
889 | Examples: | |
890 | 17 => 128 KB for each CPU | |
891 | 16 => 64 KB for each CPU | |
892 | 15 => 32 KB for each CPU | |
893 | 14 => 16 KB for each CPU | |
894 | 13 => 8 KB for each CPU | |
895 | 12 => 4 KB for each CPU | |
896 | ||
a5574cf6 IM |
897 | # |
898 | # Architectures with an unreliable sched_clock() should select this: | |
899 | # | |
900 | config HAVE_UNSTABLE_SCHED_CLOCK | |
901 | bool | |
902 | ||
38ff87f7 SB |
903 | config GENERIC_SCHED_CLOCK |
904 | bool | |
905 | ||
be3a7284 AA |
906 | # |
907 | # For architectures that want to enable the support for NUMA-affine scheduler | |
908 | # balancing logic: | |
909 | # | |
910 | config ARCH_SUPPORTS_NUMA_BALANCING | |
911 | bool | |
912 | ||
72b252ae MG |
913 | # |
914 | # For architectures that prefer to flush all TLBs after a number of pages | |
915 | # are unmapped instead of sending one IPI per page to flush. The architecture | |
916 | # must provide guarantees on what happens if a clean TLB cache entry is | |
917 | # written after the unmap. Details are in mm/rmap.c near the check for | |
918 | # should_defer_flush. The architecture should also consider if the full flush | |
919 | # and the refill costs are offset by the savings of sending fewer IPIs. | |
920 | config ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH | |
921 | bool | |
922 | ||
be5e610c PZ |
923 | # |
924 | # For architectures that know their GCC __int128 support is sound | |
925 | # | |
926 | config ARCH_SUPPORTS_INT128 | |
927 | bool | |
928 | ||
be3a7284 AA |
929 | # For architectures that (ab)use NUMA to represent different memory regions |
930 | # all cpu-local but of different latencies, such as SuperH. | |
931 | # | |
932 | config ARCH_WANT_NUMA_VARIABLE_LOCALITY | |
933 | bool | |
934 | ||
be3a7284 AA |
935 | config NUMA_BALANCING |
936 | bool "Memory placement aware NUMA scheduler" | |
be3a7284 AA |
937 | depends on ARCH_SUPPORTS_NUMA_BALANCING |
938 | depends on !ARCH_WANT_NUMA_VARIABLE_LOCALITY | |
939 | depends on SMP && NUMA && MIGRATION | |
940 | help | |
941 | This option adds support for automatic NUMA aware memory/task placement. | |
942 | The mechanism is quite primitive and is based on migrating memory when | |
6d56a410 | 943 | it has references to the node the task is running on. |
be3a7284 AA |
944 | |
945 | This system will be inactive on UMA systems. | |
946 | ||
6f7c97e8 AK |
947 | config NUMA_BALANCING_DEFAULT_ENABLED |
948 | bool "Automatically enable NUMA aware memory/task placement" | |
949 | default y | |
950 | depends on NUMA_BALANCING | |
951 | help | |
952 | If set, automatic NUMA balancing will be enabled if running on a NUMA | |
953 | machine. | |
954 | ||
23964d2d | 955 | menuconfig CGROUPS |
6341e62b | 956 | bool "Control Group support" |
2bd59d48 | 957 | select KERNFS |
5cdc38f9 | 958 | help |
23964d2d | 959 | This option adds support for grouping sets of processes together, for |
5cdc38f9 KH |
960 | use with process control subsystems such as Cpusets, CFS, memory |
961 | controls or device isolation. | |
962 | See | |
5cdc38f9 | 963 | - Documentation/scheduler/sched-design-CFS.txt (CFS) |
9991a9c8 | 964 | - Documentation/cgroup-v1/ (features for grouping, isolation |
45ce80fb | 965 | and resource control) |
5cdc38f9 KH |
966 | |
967 | Say N if unsure. | |
968 | ||
23964d2d LZ |
969 | if CGROUPS |
970 | ||
3e32cb2e JW |
971 | config PAGE_COUNTER |
972 | bool | |
973 | ||
c255a458 | 974 | config MEMCG |
a0166ec4 | 975 | bool "Memory controller" |
3e32cb2e | 976 | select PAGE_COUNTER |
79bd9814 | 977 | select EVENTFD |
00f0b825 | 978 | help |
a0166ec4 | 979 | Provides control over the memory footprint of tasks in a cgroup. |
00f0b825 | 980 | |
c255a458 | 981 | config MEMCG_SWAP |
a0166ec4 | 982 | bool "Swap controller" |
c255a458 | 983 | depends on MEMCG && SWAP |
c077719b | 984 | help |
a0166ec4 JW |
985 | Provides control over the swap space consumed by tasks in a cgroup. |
986 | ||
c255a458 | 987 | config MEMCG_SWAP_ENABLED |
a0166ec4 | 988 | bool "Swap controller enabled by default" |
c255a458 | 989 | depends on MEMCG_SWAP |
a42c390c MH |
990 | default y |
991 | help | |
992 | Memory Resource Controller Swap Extension comes with its price in | |
993 | a bigger memory consumption. General purpose distribution kernels | |
43d547f9 | 994 | which want to enable the feature but keep it disabled by default |
07555ac1 | 995 | and let the user enable it by swapaccount=1 boot command line |
a42c390c MH |
996 | parameter should have this option unselected. |
997 | For those who want to have the feature enabled by default should | |
998 | select this option (if, for some reason, they need to disable it | |
00a66d29 | 999 | then swapaccount=0 does the trick). |
c077719b | 1000 | |
6bf024e6 JW |
1001 | config BLK_CGROUP |
1002 | bool "IO controller" | |
1003 | depends on BLOCK | |
2bc64a20 | 1004 | default n |
6bf024e6 JW |
1005 | ---help--- |
1006 | Generic block IO controller cgroup interface. This is the common | |
1007 | cgroup interface which should be used by various IO controlling | |
1008 | policies. | |
2bc64a20 | 1009 | |
6bf024e6 JW |
1010 | Currently, CFQ IO scheduler uses it to recognize task groups and |
1011 | control disk bandwidth allocation (proportional time slice allocation) | |
1012 | to such task groups. It is also used by bio throttling logic in | |
1013 | block layer to implement upper limit in IO rates on a device. | |
e5d1367f | 1014 | |
6bf024e6 JW |
1015 | This option only enables generic Block IO controller infrastructure. |
1016 | One needs to also enable actual IO controlling logic/policy. For | |
1017 | enabling proportional weight division of disk bandwidth in CFQ, set | |
1018 | CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set | |
1019 | CONFIG_BLK_DEV_THROTTLING=y. | |
1020 | ||
9991a9c8 | 1021 | See Documentation/cgroup-v1/blkio-controller.txt for more information. |
6bf024e6 JW |
1022 | |
1023 | config DEBUG_BLK_CGROUP | |
1024 | bool "IO controller debugging" | |
1025 | depends on BLK_CGROUP | |
1026 | default n | |
1027 | ---help--- | |
1028 | Enable some debugging help. Currently it exports additional stat | |
1029 | files in a cgroup which can be useful for debugging. | |
1030 | ||
1031 | config CGROUP_WRITEBACK | |
1032 | bool | |
1033 | depends on MEMCG && BLK_CGROUP | |
1034 | default y | |
e5d1367f | 1035 | |
7c941438 | 1036 | menuconfig CGROUP_SCHED |
a0166ec4 | 1037 | bool "CPU controller" |
7c941438 DG |
1038 | default n |
1039 | help | |
1040 | This feature lets CPU scheduler recognize task groups and control CPU | |
1041 | bandwidth allocation to such task groups. It uses cgroups to group | |
1042 | tasks. | |
1043 | ||
1044 | if CGROUP_SCHED | |
1045 | config FAIR_GROUP_SCHED | |
1046 | bool "Group scheduling for SCHED_OTHER" | |
1047 | depends on CGROUP_SCHED | |
1048 | default CGROUP_SCHED | |
1049 | ||
ab84d31e PT |
1050 | config CFS_BANDWIDTH |
1051 | bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED" | |
ab84d31e PT |
1052 | depends on FAIR_GROUP_SCHED |
1053 | default n | |
1054 | help | |
1055 | This option allows users to define CPU bandwidth rates (limits) for | |
1056 | tasks running within the fair group scheduler. Groups with no limit | |
1057 | set are considered to be unconstrained and will run with no | |
1058 | restriction. | |
1059 | See tip/Documentation/scheduler/sched-bwc.txt for more information. | |
1060 | ||
7c941438 DG |
1061 | config RT_GROUP_SCHED |
1062 | bool "Group scheduling for SCHED_RR/FIFO" | |
7c941438 DG |
1063 | depends on CGROUP_SCHED |
1064 | default n | |
1065 | help | |
1066 | This feature lets you explicitly allocate real CPU bandwidth | |
32bd7eb5 | 1067 | to task groups. If enabled, it will also make it impossible to |
7c941438 DG |
1068 | schedule realtime tasks for non-root users until you allocate |
1069 | realtime bandwidth for them. | |
1070 | See Documentation/scheduler/sched-rt-group.txt for more information. | |
1071 | ||
1072 | endif #CGROUP_SCHED | |
1073 | ||
6bf024e6 JW |
1074 | config CGROUP_PIDS |
1075 | bool "PIDs controller" | |
1076 | help | |
1077 | Provides enforcement of process number limits in the scope of a | |
1078 | cgroup. Any attempt to fork more processes than is allowed in the | |
1079 | cgroup will fail. PIDs are fundamentally a global resource because it | |
1080 | is fairly trivial to reach PID exhaustion before you reach even a | |
1081 | conservative kmemcg limit. As a result, it is possible to grind a | |
1082 | system to halt without being limited by other cgroup policies. The | |
6cc578df | 1083 | PIDs controller is designed to stop this from happening. |
6bf024e6 JW |
1084 | |
1085 | It should be noted that organisational operations (such as attaching | |
6cc578df | 1086 | to a cgroup hierarchy will *not* be blocked by the PIDs controller), |
6bf024e6 JW |
1087 | since the PIDs limit only affects a process's ability to fork, not to |
1088 | attach to a cgroup. | |
1089 | ||
1090 | config CGROUP_FREEZER | |
1091 | bool "Freezer controller" | |
1092 | help | |
1093 | Provides a way to freeze and unfreeze all tasks in a | |
1094 | cgroup. | |
1095 | ||
489c2a20 JW |
1096 | This option affects the ORIGINAL cgroup interface. The cgroup2 memory |
1097 | controller includes important in-kernel memory consumers per default. | |
1098 | ||
1099 | If you're using cgroup2, say N. | |
1100 | ||
6bf024e6 JW |
1101 | config CGROUP_HUGETLB |
1102 | bool "HugeTLB controller" | |
1103 | depends on HUGETLB_PAGE | |
1104 | select PAGE_COUNTER | |
afc24d49 | 1105 | default n |
6bf024e6 JW |
1106 | help |
1107 | Provides a cgroup controller for HugeTLB pages. | |
1108 | When you enable this, you can put a per cgroup limit on HugeTLB usage. | |
1109 | The limit is enforced during page fault. Since HugeTLB doesn't | |
1110 | support page reclaim, enforcing the limit at page fault time implies | |
1111 | that, the application will get SIGBUS signal if it tries to access | |
1112 | HugeTLB pages beyond its limit. This requires the application to know | |
1113 | beforehand how much HugeTLB pages it would require for its use. The | |
1114 | control group is tracked in the third page lru pointer. This means | |
1115 | that we cannot use the controller with huge page less than 3 pages. | |
afc24d49 | 1116 | |
6bf024e6 JW |
1117 | config CPUSETS |
1118 | bool "Cpuset controller" | |
1119 | help | |
1120 | This option will let you create and manage CPUSETs which | |
1121 | allow dynamically partitioning a system into sets of CPUs and | |
1122 | Memory Nodes and assigning tasks to run only within those sets. | |
1123 | This is primarily useful on large SMP or NUMA systems. | |
afc24d49 | 1124 | |
6bf024e6 | 1125 | Say N if unsure. |
afc24d49 | 1126 | |
6bf024e6 JW |
1127 | config PROC_PID_CPUSET |
1128 | bool "Include legacy /proc/<pid>/cpuset file" | |
1129 | depends on CPUSETS | |
1130 | default y | |
afc24d49 | 1131 | |
6bf024e6 JW |
1132 | config CGROUP_DEVICE |
1133 | bool "Device controller" | |
1134 | help | |
1135 | Provides a cgroup controller implementing whitelists for | |
1136 | devices which a process in the cgroup can mknod or open. | |
1137 | ||
1138 | config CGROUP_CPUACCT | |
1139 | bool "Simple CPU accounting controller" | |
1140 | help | |
1141 | Provides a simple controller for monitoring the | |
1142 | total CPU consumed by the tasks in a cgroup. | |
1143 | ||
1144 | config CGROUP_PERF | |
1145 | bool "Perf controller" | |
1146 | depends on PERF_EVENTS | |
1147 | help | |
1148 | This option extends the perf per-cpu mode to restrict monitoring | |
1149 | to threads which belong to the cgroup specified and run on the | |
1150 | designated cpu. | |
1151 | ||
1152 | Say N if unsure. | |
1153 | ||
1154 | config CGROUP_DEBUG | |
1155 | bool "Example controller" | |
afc24d49 | 1156 | default n |
6bf024e6 JW |
1157 | help |
1158 | This option enables a simple controller that exports | |
1159 | debugging information about the cgroups framework. | |
afc24d49 | 1160 | |
6bf024e6 | 1161 | Say N. |
89e9b9e0 | 1162 | |
23964d2d | 1163 | endif # CGROUPS |
c077719b | 1164 | |
067bce1a CG |
1165 | config CHECKPOINT_RESTORE |
1166 | bool "Checkpoint/restore support" if EXPERT | |
2e13ba54 | 1167 | select PROC_CHILDREN |
067bce1a CG |
1168 | default n |
1169 | help | |
1170 | Enables additional kernel features in a sake of checkpoint/restore. | |
1171 | In particular it adds auxiliary prctl codes to setup process text, | |
1172 | data and heap segment sizes, and a few additional /proc filesystem | |
1173 | entries. | |
1174 | ||
1175 | If unsure, say N here. | |
1176 | ||
8dd2a82c | 1177 | menuconfig NAMESPACES |
6a108a14 | 1178 | bool "Namespaces support" if EXPERT |
2813893f | 1179 | depends on MULTIUSER |
6a108a14 | 1180 | default !EXPERT |
c5289a69 PE |
1181 | help |
1182 | Provides the way to make tasks work with different objects using | |
1183 | the same id. For example same IPC id may refer to different objects | |
1184 | or same user id or pid may refer to different tasks when used in | |
1185 | different namespaces. | |
1186 | ||
8dd2a82c DL |
1187 | if NAMESPACES |
1188 | ||
58bfdd6d PE |
1189 | config UTS_NS |
1190 | bool "UTS namespace" | |
17a6d441 | 1191 | default y |
58bfdd6d PE |
1192 | help |
1193 | In this namespace tasks see different info provided with the | |
1194 | uname() system call | |
1195 | ||
ae5e1b22 PE |
1196 | config IPC_NS |
1197 | bool "IPC namespace" | |
8dd2a82c | 1198 | depends on (SYSVIPC || POSIX_MQUEUE) |
17a6d441 | 1199 | default y |
ae5e1b22 PE |
1200 | help |
1201 | In this namespace tasks work with IPC ids which correspond to | |
614b84cf | 1202 | different IPC objects in different namespaces. |
ae5e1b22 | 1203 | |
aee16ce7 | 1204 | config USER_NS |
19c92399 | 1205 | bool "User namespace" |
5673a94c | 1206 | default n |
aee16ce7 PE |
1207 | help |
1208 | This allows containers, i.e. vservers, to use user namespaces | |
1209 | to provide different user info for different servers. | |
e11f0ae3 EB |
1210 | |
1211 | When user namespaces are enabled in the kernel it is | |
d886f4e4 JW |
1212 | recommended that the MEMCG option also be enabled and that |
1213 | user-space use the memory control groups to limit the amount | |
1214 | of memory a memory unprivileged users can use. | |
e11f0ae3 | 1215 | |
aee16ce7 PE |
1216 | If unsure, say N. |
1217 | ||
74bd59bb | 1218 | config PID_NS |
9bd38c2c | 1219 | bool "PID Namespaces" |
17a6d441 | 1220 | default y |
74bd59bb | 1221 | help |
12d2b8f9 | 1222 | Support process id namespaces. This allows having multiple |
692105b8 | 1223 | processes with the same pid as long as they are in different |
74bd59bb PE |
1224 | pid namespaces. This is a building block of containers. |
1225 | ||
d6eb633f MH |
1226 | config NET_NS |
1227 | bool "Network namespace" | |
8dd2a82c | 1228 | depends on NET |
17a6d441 | 1229 | default y |
d6eb633f MH |
1230 | help |
1231 | Allow user space to create what appear to be multiple instances | |
1232 | of the network stack. | |
1233 | ||
8dd2a82c DL |
1234 | endif # NAMESPACES |
1235 | ||
5091faa4 MG |
1236 | config SCHED_AUTOGROUP |
1237 | bool "Automatic process group scheduling" | |
5091faa4 MG |
1238 | select CGROUPS |
1239 | select CGROUP_SCHED | |
1240 | select FAIR_GROUP_SCHED | |
1241 | help | |
1242 | This option optimizes the scheduler for common desktop workloads by | |
1243 | automatically creating and populating task groups. This separation | |
1244 | of workloads isolates aggressive CPU burners (like build jobs) from | |
1245 | desktop applications. Task group autogeneration is currently based | |
1246 | upon task session. | |
1247 | ||
7af37bec | 1248 | config SYSFS_DEPRECATED |
5d6a4ea5 | 1249 | bool "Enable deprecated sysfs features to support old userspace tools" |
7af37bec DL |
1250 | depends on SYSFS |
1251 | default n | |
1252 | help | |
1253 | This option adds code that switches the layout of the "block" class | |
1254 | devices, to not show up in /sys/class/block/, but only in | |
1255 | /sys/block/. | |
1256 | ||
1257 | This switch is only active when the sysfs.deprecated=1 boot option is | |
1258 | passed or the SYSFS_DEPRECATED_V2 option is set. | |
1259 | ||
1260 | This option allows new kernels to run on old distributions and tools, | |
1261 | which might get confused by /sys/class/block/. Since 2007/2008 all | |
1262 | major distributions and tools handle this just fine. | |
1263 | ||
1264 | Recent distributions and userspace tools after 2009/2010 depend on | |
1265 | the existence of /sys/class/block/, and will not work with this | |
1266 | option enabled. | |
1267 | ||
1268 | Only if you are using a new kernel on an old distribution, you might | |
1269 | need to say Y here. | |
1270 | ||
1271 | config SYSFS_DEPRECATED_V2 | |
5d6a4ea5 | 1272 | bool "Enable deprecated sysfs features by default" |
7af37bec DL |
1273 | default n |
1274 | depends on SYSFS | |
1275 | depends on SYSFS_DEPRECATED | |
1276 | help | |
1277 | Enable deprecated sysfs by default. | |
1278 | ||
1279 | See the CONFIG_SYSFS_DEPRECATED option for more details about this | |
1280 | option. | |
1281 | ||
1282 | Only if you are using a new kernel on an old distribution, you might | |
1283 | need to say Y here. Even then, odds are you would not need it | |
1284 | enabled, you can always pass the boot option if absolutely necessary. | |
1285 | ||
1286 | config RELAY | |
1287 | bool "Kernel->user space relay support (formerly relayfs)" | |
1288 | help | |
1289 | This option enables support for relay interface support in | |
1290 | certain file systems (such as debugfs). | |
1291 | It is designed to provide an efficient mechanism for tools and | |
1292 | facilities to relay large amounts of data from kernel space to | |
1293 | user space. | |
1294 | ||
1295 | If unsure, say N. | |
1296 | ||
f991633d DG |
1297 | config BLK_DEV_INITRD |
1298 | bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support" | |
1299 | depends on BROKEN || !FRV | |
1300 | help | |
1301 | The initial RAM filesystem is a ramfs which is loaded by the | |
1302 | boot loader (loadlin or lilo) and that is mounted as root | |
1303 | before the normal boot procedure. It is typically used to | |
1304 | load modules needed to mount the "real" root file system, | |
1305 | etc. See <file:Documentation/initrd.txt> for details. | |
1306 | ||
1307 | If RAM disk support (BLK_DEV_RAM) is also included, this | |
1308 | also enables initial RAM disk (initrd) support and adds | |
1309 | 15 Kbytes (more on some other architectures) to the kernel size. | |
1310 | ||
1311 | If unsure say Y. | |
1312 | ||
c33df4ea JPS |
1313 | if BLK_DEV_INITRD |
1314 | ||
dbec4866 SR |
1315 | source "usr/Kconfig" |
1316 | ||
c33df4ea JPS |
1317 | endif |
1318 | ||
877417e6 AB |
1319 | choice |
1320 | prompt "Compiler optimization level" | |
1321 | default CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE | |
1322 | ||
1323 | config CC_OPTIMIZE_FOR_PERFORMANCE | |
1324 | bool "Optimize for performance" | |
1325 | help | |
1326 | This is the default optimization level for the kernel, building | |
1327 | with the "-O2" compiler flag for best performance and most | |
1328 | helpful compile-time warnings. | |
1329 | ||
c45b4f1f | 1330 | config CC_OPTIMIZE_FOR_SIZE |
96fffeb4 | 1331 | bool "Optimize for size" |
c45b4f1f | 1332 | help |
31a4af7f MY |
1333 | Enabling this option will pass "-Os" instead of "-O2" to |
1334 | your compiler resulting in a smaller kernel. | |
c45b4f1f | 1335 | |
3a55fb0d | 1336 | If unsure, say N. |
c45b4f1f | 1337 | |
877417e6 AB |
1338 | endchoice |
1339 | ||
0847062a RD |
1340 | config SYSCTL |
1341 | bool | |
1342 | ||
b943c460 RD |
1343 | config ANON_INODES |
1344 | bool | |
1345 | ||
657a5209 MF |
1346 | config HAVE_UID16 |
1347 | bool | |
1348 | ||
1349 | config SYSCTL_EXCEPTION_TRACE | |
1350 | bool | |
1351 | help | |
1352 | Enable support for /proc/sys/debug/exception-trace. | |
1353 | ||
1354 | config SYSCTL_ARCH_UNALIGN_NO_WARN | |
1355 | bool | |
1356 | help | |
1357 | Enable support for /proc/sys/kernel/ignore-unaligned-usertrap | |
1358 | Allows arch to define/use @no_unaligned_warning to possibly warn | |
1359 | about unaligned access emulation going on under the hood. | |
1360 | ||
1361 | config SYSCTL_ARCH_UNALIGN_ALLOW | |
1362 | bool | |
1363 | help | |
1364 | Enable support for /proc/sys/kernel/unaligned-trap | |
1365 | Allows arches to define/use @unaligned_enabled to runtime toggle | |
1366 | the unaligned access emulation. | |
1367 | see arch/parisc/kernel/unaligned.c for reference | |
1368 | ||
657a5209 MF |
1369 | config HAVE_PCSPKR_PLATFORM |
1370 | bool | |
1371 | ||
f89b7755 AS |
1372 | # interpreter that classic socket filters depend on |
1373 | config BPF | |
1374 | bool | |
1375 | ||
6a108a14 DR |
1376 | menuconfig EXPERT |
1377 | bool "Configure standard kernel features (expert users)" | |
f505c553 JT |
1378 | # Unhide debug options, to make the on-by-default options visible |
1379 | select DEBUG_KERNEL | |
1da177e4 LT |
1380 | help |
1381 | This option allows certain base kernel options and settings | |
1382 | to be disabled or tweaked. This is for specialized | |
1383 | environments which can tolerate a "non-standard" kernel. | |
1384 | Only use this if you really know what you are doing. | |
1385 | ||
ae81f9e3 | 1386 | config UID16 |
6a108a14 | 1387 | bool "Enable 16-bit UID system calls" if EXPERT |
2813893f | 1388 | depends on HAVE_UID16 && MULTIUSER |
ae81f9e3 CE |
1389 | default y |
1390 | help | |
1391 | This enables the legacy 16-bit UID syscall wrappers. | |
1392 | ||
2813893f IM |
1393 | config MULTIUSER |
1394 | bool "Multiple users, groups and capabilities support" if EXPERT | |
1395 | default y | |
1396 | help | |
1397 | This option enables support for non-root users, groups and | |
1398 | capabilities. | |
1399 | ||
1400 | If you say N here, all processes will run with UID 0, GID 0, and all | |
1401 | possible capabilities. Saying N here also compiles out support for | |
1402 | system calls related to UIDs, GIDs, and capabilities, such as setuid, | |
1403 | setgid, and capset. | |
1404 | ||
1405 | If unsure, say Y here. | |
1406 | ||
f6187769 FF |
1407 | config SGETMASK_SYSCALL |
1408 | bool "sgetmask/ssetmask syscalls support" if EXPERT | |
1409 | def_bool PARISC || MN10300 || BLACKFIN || M68K || PPC || MIPS || X86 || SPARC || CRIS || MICROBLAZE || SUPERH | |
1410 | ---help--- | |
1411 | sys_sgetmask and sys_ssetmask are obsolete system calls | |
1412 | no longer supported in libc but still enabled by default in some | |
1413 | architectures. | |
1414 | ||
1415 | If unsure, leave the default option here. | |
1416 | ||
6af9f7bf FF |
1417 | config SYSFS_SYSCALL |
1418 | bool "Sysfs syscall support" if EXPERT | |
1419 | default y | |
1420 | ---help--- | |
1421 | sys_sysfs is an obsolete system call no longer supported in libc. | |
1422 | Note that disabling this option is more secure but might break | |
1423 | compatibility with some systems. | |
1424 | ||
1425 | If unsure say Y here. | |
1426 | ||
b89a8171 | 1427 | config SYSCTL_SYSCALL |
6a108a14 | 1428 | bool "Sysctl syscall support" if EXPERT |
26a7034b | 1429 | depends on PROC_SYSCTL |
c736de60 | 1430 | default n |
b89a8171 | 1431 | select SYSCTL |
ae81f9e3 | 1432 | ---help--- |
13bb7e37 EB |
1433 | sys_sysctl uses binary paths that have been found challenging |
1434 | to properly maintain and use. The interface in /proc/sys | |
1435 | using paths with ascii names is now the primary path to this | |
1436 | information. | |
b89a8171 | 1437 | |
13bb7e37 EB |
1438 | Almost nothing using the binary sysctl interface so if you are |
1439 | trying to save some space it is probably safe to disable this, | |
1440 | making your kernel marginally smaller. | |
b89a8171 | 1441 | |
c736de60 | 1442 | If unsure say N here. |
ae81f9e3 | 1443 | |
1da177e4 | 1444 | config KALLSYMS |
6a108a14 | 1445 | bool "Load all symbols for debugging/ksymoops" if EXPERT |
1da177e4 LT |
1446 | default y |
1447 | help | |
1448 | Say Y here to let the kernel print out symbolic crash information and | |
1449 | symbolic stack backtraces. This increases the size of the kernel | |
1450 | somewhat, as all symbols have to be loaded into the kernel image. | |
1451 | ||
1452 | config KALLSYMS_ALL | |
1453 | bool "Include all symbols in kallsyms" | |
1454 | depends on DEBUG_KERNEL && KALLSYMS | |
1455 | help | |
71a83ec7 AB |
1456 | Normally kallsyms only contains the symbols of functions for nicer |
1457 | OOPS messages and backtraces (i.e., symbols from the text and inittext | |
1458 | sections). This is sufficient for most cases. And only in very rare | |
1459 | cases (e.g., when a debugger is used) all symbols are required (e.g., | |
1460 | names of variables from the data sections, etc). | |
1461 | ||
1462 | This option makes sure that all symbols are loaded into the kernel | |
1463 | image (i.e., symbols from all sections) in cost of increased kernel | |
1464 | size (depending on the kernel configuration, it may be 300KiB or | |
1465 | something like this). | |
1466 | ||
1467 | Say N unless you really need all symbols. | |
d59745ce | 1468 | |
4d5d5664 AB |
1469 | config KALLSYMS_ABSOLUTE_PERCPU |
1470 | bool | |
076501ff | 1471 | depends on KALLSYMS |
4d5d5664 AB |
1472 | default X86_64 && SMP |
1473 | ||
2213e9a6 AB |
1474 | config KALLSYMS_BASE_RELATIVE |
1475 | bool | |
1476 | depends on KALLSYMS | |
1477 | default !IA64 && !(TILE && 64BIT) | |
1478 | help | |
1479 | Instead of emitting them as absolute values in the native word size, | |
1480 | emit the symbol references in the kallsyms table as 32-bit entries, | |
1481 | each containing a relative value in the range [base, base + U32_MAX] | |
1482 | or, when KALLSYMS_ABSOLUTE_PERCPU is in effect, each containing either | |
1483 | an absolute value in the range [0, S32_MAX] or a relative value in the | |
1484 | range [base, base + S32_MAX], where base is the lowest relative symbol | |
1485 | address encountered in the image. | |
1486 | ||
1487 | On 64-bit builds, this reduces the size of the address table by 50%, | |
1488 | but more importantly, it results in entries whose values are build | |
1489 | time constants, and no relocation pass is required at runtime to fix | |
1490 | up the entries based on the runtime load address of the kernel. | |
1491 | ||
d59745ce MM |
1492 | config PRINTK |
1493 | default y | |
6a108a14 | 1494 | bool "Enable support for printk" if EXPERT |
74876a98 | 1495 | select IRQ_WORK |
d59745ce MM |
1496 | help |
1497 | This option enables normal printk support. Removing it | |
1498 | eliminates most of the message strings from the kernel image | |
1499 | and makes the kernel more or less silent. As this makes it | |
1500 | very difficult to diagnose system problems, saying N here is | |
1501 | strongly discouraged. | |
1502 | ||
42a0bb3f PM |
1503 | config PRINTK_NMI |
1504 | def_bool y | |
1505 | depends on PRINTK | |
1506 | depends on HAVE_NMI | |
1507 | ||
c8538a7a | 1508 | config BUG |
6a108a14 | 1509 | bool "BUG() support" if EXPERT |
c8538a7a MM |
1510 | default y |
1511 | help | |
1512 | Disabling this option eliminates support for BUG and WARN, reducing | |
1513 | the size of your kernel image and potentially quietly ignoring | |
1514 | numerous fatal conditions. You should only consider disabling this | |
1515 | option for embedded systems with no facilities for reporting errors. | |
1516 | Just say Y. | |
1517 | ||
708e9a79 | 1518 | config ELF_CORE |
046d662f | 1519 | depends on COREDUMP |
708e9a79 | 1520 | default y |
6a108a14 | 1521 | bool "Enable ELF core dumps" if EXPERT |
708e9a79 MM |
1522 | help |
1523 | Enable support for generating core dumps. Disabling saves about 4k. | |
1524 | ||
8761f1ab | 1525 | |
e5e1d3cb | 1526 | config PCSPKR_PLATFORM |
6a108a14 | 1527 | bool "Enable PC-Speaker support" if EXPERT |
8761f1ab | 1528 | depends on HAVE_PCSPKR_PLATFORM |
15f304b6 | 1529 | select I8253_LOCK |
e5e1d3cb SS |
1530 | default y |
1531 | help | |
1532 | This option allows to disable the internal PC-Speaker | |
1533 | support, saving some memory. | |
1534 | ||
1da177e4 LT |
1535 | config BASE_FULL |
1536 | default y | |
6a108a14 | 1537 | bool "Enable full-sized data structures for core" if EXPERT |
1da177e4 LT |
1538 | help |
1539 | Disabling this option reduces the size of miscellaneous core | |
1540 | kernel data structures. This saves memory on small machines, | |
1541 | but may reduce performance. | |
1542 | ||
1543 | config FUTEX | |
6a108a14 | 1544 | bool "Enable futex support" if EXPERT |
1da177e4 | 1545 | default y |
23f78d4a | 1546 | select RT_MUTEXES |
1da177e4 LT |
1547 | help |
1548 | Disabling this option will cause the kernel to be built without | |
1549 | support for "fast userspace mutexes". The resulting kernel may not | |
1550 | run glibc-based applications correctly. | |
1551 | ||
03b8c7b6 HC |
1552 | config HAVE_FUTEX_CMPXCHG |
1553 | bool | |
62b4d204 | 1554 | depends on FUTEX |
03b8c7b6 HC |
1555 | help |
1556 | Architectures should select this if futex_atomic_cmpxchg_inatomic() | |
1557 | is implemented and always working. This removes a couple of runtime | |
1558 | checks. | |
1559 | ||
1da177e4 | 1560 | config EPOLL |
6a108a14 | 1561 | bool "Enable eventpoll support" if EXPERT |
1da177e4 | 1562 | default y |
448e3cee | 1563 | select ANON_INODES |
1da177e4 LT |
1564 | help |
1565 | Disabling this option will cause the kernel to be built without | |
1566 | support for epoll family of system calls. | |
1567 | ||
fba2afaa | 1568 | config SIGNALFD |
6a108a14 | 1569 | bool "Enable signalfd() system call" if EXPERT |
448e3cee | 1570 | select ANON_INODES |
fba2afaa DL |
1571 | default y |
1572 | help | |
1573 | Enable the signalfd() system call that allows to receive signals | |
1574 | on a file descriptor. | |
1575 | ||
1576 | If unsure, say Y. | |
1577 | ||
b215e283 | 1578 | config TIMERFD |
6a108a14 | 1579 | bool "Enable timerfd() system call" if EXPERT |
448e3cee | 1580 | select ANON_INODES |
b215e283 DL |
1581 | default y |
1582 | help | |
1583 | Enable the timerfd() system call that allows to receive timer | |
1584 | events on a file descriptor. | |
1585 | ||
1586 | If unsure, say Y. | |
1587 | ||
e1ad7468 | 1588 | config EVENTFD |
6a108a14 | 1589 | bool "Enable eventfd() system call" if EXPERT |
448e3cee | 1590 | select ANON_INODES |
e1ad7468 DL |
1591 | default y |
1592 | help | |
1593 | Enable the eventfd() system call that allows to receive both | |
1594 | kernel notification (ie. KAIO) or userspace notifications. | |
1595 | ||
1596 | If unsure, say Y. | |
1597 | ||
f89b7755 AS |
1598 | # syscall, maps, verifier |
1599 | config BPF_SYSCALL | |
e1abf2cc | 1600 | bool "Enable bpf() system call" |
f89b7755 AS |
1601 | select ANON_INODES |
1602 | select BPF | |
1603 | default n | |
1604 | help | |
1605 | Enable the bpf() system call that allows to manipulate eBPF | |
1606 | programs and maps via file descriptors. | |
1607 | ||
1da177e4 | 1608 | config SHMEM |
6a108a14 | 1609 | bool "Use full shmem filesystem" if EXPERT |
1da177e4 LT |
1610 | default y |
1611 | depends on MMU | |
1612 | help | |
1613 | The shmem is an internal filesystem used to manage shared memory. | |
1614 | It is backed by swap and manages resource limits. It is also exported | |
1615 | to userspace as tmpfs if TMPFS is enabled. Disabling this | |
1616 | option replaces shmem and tmpfs with the much simpler ramfs code, | |
1617 | which may be appropriate on small systems without swap. | |
1618 | ||
ebf3f09c | 1619 | config AIO |
6a108a14 | 1620 | bool "Enable AIO support" if EXPERT |
ebf3f09c TP |
1621 | default y |
1622 | help | |
1623 | This option enables POSIX asynchronous I/O which may by used | |
657a5209 MF |
1624 | by some high performance threaded applications. Disabling |
1625 | this option saves about 7k. | |
1626 | ||
d3ac21ca JT |
1627 | config ADVISE_SYSCALLS |
1628 | bool "Enable madvise/fadvise syscalls" if EXPERT | |
1629 | default y | |
1630 | help | |
1631 | This option enables the madvise and fadvise syscalls, used by | |
1632 | applications to advise the kernel about their future memory or file | |
1633 | usage, improving performance. If building an embedded system where no | |
1634 | applications use these syscalls, you can disable this option to save | |
1635 | space. | |
1636 | ||
a14c151e AA |
1637 | config USERFAULTFD |
1638 | bool "Enable userfaultfd() system call" | |
1639 | select ANON_INODES | |
a14c151e AA |
1640 | depends on MMU |
1641 | help | |
1642 | Enable the userfaultfd() system call that allows to intercept and | |
1643 | handle page faults in userland. | |
1644 | ||
657a5209 MF |
1645 | config PCI_QUIRKS |
1646 | default y | |
1647 | bool "Enable PCI quirk workarounds" if EXPERT | |
1648 | depends on PCI | |
1649 | help | |
1650 | This enables workarounds for various PCI chipset | |
1651 | bugs/quirks. Disable this only if your target machine is | |
1652 | unaffected by PCI quirks. | |
ebf3f09c | 1653 | |
5b25b13a MD |
1654 | config MEMBARRIER |
1655 | bool "Enable membarrier() system call" if EXPERT | |
1656 | default y | |
1657 | help | |
1658 | Enable the membarrier() system call that allows issuing memory | |
1659 | barriers across all running threads, which can be used to distribute | |
1660 | the cost of user-space memory barriers asymmetrically by transforming | |
1661 | pairs of memory barriers into pairs consisting of membarrier() and a | |
1662 | compiler barrier. | |
1663 | ||
1664 | If unsure, say Y. | |
1665 | ||
6befe5f6 RD |
1666 | config EMBEDDED |
1667 | bool "Embedded system" | |
5d2acfc7 | 1668 | option allnoconfig_y |
6befe5f6 RD |
1669 | select EXPERT |
1670 | help | |
1671 | This option should be enabled if compiling the kernel for | |
1672 | an embedded system so certain expert options are available | |
1673 | for configuration. | |
1674 | ||
cdd6c482 | 1675 | config HAVE_PERF_EVENTS |
0793a61d | 1676 | bool |
018df72d MF |
1677 | help |
1678 | See tools/perf/design.txt for details. | |
0793a61d | 1679 | |
906010b2 PZ |
1680 | config PERF_USE_VMALLOC |
1681 | bool | |
1682 | help | |
1683 | See tools/perf/design.txt for details | |
1684 | ||
57c0c15b | 1685 | menu "Kernel Performance Events And Counters" |
0793a61d | 1686 | |
cdd6c482 | 1687 | config PERF_EVENTS |
57c0c15b | 1688 | bool "Kernel performance events and counters" |
392d65a9 | 1689 | default y if PROFILING |
cdd6c482 | 1690 | depends on HAVE_PERF_EVENTS |
4c59e467 | 1691 | select ANON_INODES |
e360adbe | 1692 | select IRQ_WORK |
83fe27ea | 1693 | select SRCU |
0793a61d | 1694 | help |
57c0c15b IM |
1695 | Enable kernel support for various performance events provided |
1696 | by software and hardware. | |
0793a61d | 1697 | |
dd77038d | 1698 | Software events are supported either built-in or via the |
57c0c15b | 1699 | use of generic tracepoints. |
0793a61d | 1700 | |
57c0c15b IM |
1701 | Most modern CPUs support performance events via performance |
1702 | counter registers. These registers count the number of certain | |
0793a61d TG |
1703 | types of hw events: such as instructions executed, cachemisses |
1704 | suffered, or branches mis-predicted - without slowing down the | |
1705 | kernel or applications. These registers can also trigger interrupts | |
1706 | when a threshold number of events have passed - and can thus be | |
1707 | used to profile the code that runs on that CPU. | |
1708 | ||
57c0c15b | 1709 | The Linux Performance Event subsystem provides an abstraction of |
dd77038d | 1710 | these software and hardware event capabilities, available via a |
57c0c15b | 1711 | system call and used by the "perf" utility in tools/perf/. It |
0793a61d TG |
1712 | provides per task and per CPU counters, and it provides event |
1713 | capabilities on top of those. | |
1714 | ||
1715 | Say Y if unsure. | |
1716 | ||
906010b2 PZ |
1717 | config DEBUG_PERF_USE_VMALLOC |
1718 | default n | |
1719 | bool "Debug: use vmalloc to back perf mmap() buffers" | |
cb307113 | 1720 | depends on PERF_EVENTS && DEBUG_KERNEL && !PPC |
906010b2 PZ |
1721 | select PERF_USE_VMALLOC |
1722 | help | |
1723 | Use vmalloc memory to back perf mmap() buffers. | |
1724 | ||
1725 | Mostly useful for debugging the vmalloc code on platforms | |
1726 | that don't require it. | |
1727 | ||
1728 | Say N if unsure. | |
1729 | ||
0793a61d TG |
1730 | endmenu |
1731 | ||
f8891e5e CL |
1732 | config VM_EVENT_COUNTERS |
1733 | default y | |
6a108a14 | 1734 | bool "Enable VM event counters for /proc/vmstat" if EXPERT |
f8891e5e | 1735 | help |
2aea4fb6 PJ |
1736 | VM event counters are needed for event counts to be shown. |
1737 | This option allows the disabling of the VM event counters | |
6a108a14 | 1738 | on EXPERT systems. /proc/vmstat will only show page counts |
2aea4fb6 | 1739 | if VM event counters are disabled. |
f8891e5e | 1740 | |
41ecc55b CL |
1741 | config SLUB_DEBUG |
1742 | default y | |
6a108a14 | 1743 | bool "Enable SLUB debugging support" if EXPERT |
f6acb635 | 1744 | depends on SLUB && SYSFS |
41ecc55b CL |
1745 | help |
1746 | SLUB has extensive debug support features. Disabling these can | |
1747 | result in significant savings in code size. This also disables | |
1748 | SLUB sysfs support. /sys/slab will not exist and there will be | |
1749 | no support for cache validation etc. | |
1750 | ||
b943c460 RD |
1751 | config COMPAT_BRK |
1752 | bool "Disable heap randomization" | |
1753 | default y | |
1754 | help | |
1755 | Randomizing heap placement makes heap exploits harder, but it | |
1756 | also breaks ancient binaries (including anything libc5 based). | |
1757 | This option changes the bootup default to heap randomization | |
692105b8 | 1758 | disabled, and can be overridden at runtime by setting |
b943c460 RD |
1759 | /proc/sys/kernel/randomize_va_space to 2. |
1760 | ||
1761 | On non-ancient distros (post-2000 ones) N is usually a safe choice. | |
1762 | ||
81819f0f CL |
1763 | choice |
1764 | prompt "Choose SLAB allocator" | |
a0acd820 | 1765 | default SLUB |
81819f0f CL |
1766 | help |
1767 | This option allows to select a slab allocator. | |
1768 | ||
1769 | config SLAB | |
1770 | bool "SLAB" | |
04385fc5 | 1771 | select HAVE_HARDENED_USERCOPY_ALLOCATOR |
81819f0f CL |
1772 | help |
1773 | The regular slab allocator that is established and known to work | |
34013886 | 1774 | well in all environments. It organizes cache hot objects in |
02f56210 | 1775 | per cpu and per node queues. |
81819f0f CL |
1776 | |
1777 | config SLUB | |
81819f0f | 1778 | bool "SLUB (Unqueued Allocator)" |
ed18adc1 | 1779 | select HAVE_HARDENED_USERCOPY_ALLOCATOR |
81819f0f CL |
1780 | help |
1781 | SLUB is a slab allocator that minimizes cache line usage | |
1782 | instead of managing queues of cached objects (SLAB approach). | |
1783 | Per cpu caching is realized using slabs of objects instead | |
1784 | of queues of objects. SLUB can use memory efficiently | |
02f56210 SA |
1785 | and has enhanced diagnostics. SLUB is the default choice for |
1786 | a slab allocator. | |
81819f0f CL |
1787 | |
1788 | config SLOB | |
6a108a14 | 1789 | depends on EXPERT |
81819f0f CL |
1790 | bool "SLOB (Simple Allocator)" |
1791 | help | |
37291458 MM |
1792 | SLOB replaces the stock allocator with a drastically simpler |
1793 | allocator. SLOB is generally more space efficient but | |
1794 | does not perform as well on large systems. | |
81819f0f CL |
1795 | |
1796 | endchoice | |
1797 | ||
c7ce4f60 TG |
1798 | config SLAB_FREELIST_RANDOM |
1799 | default n | |
210e7a43 | 1800 | depends on SLAB || SLUB |
c7ce4f60 TG |
1801 | bool "SLAB freelist randomization" |
1802 | help | |
210e7a43 | 1803 | Randomizes the freelist order used on creating new pages. This |
c7ce4f60 TG |
1804 | security feature reduces the predictability of the kernel slab |
1805 | allocator against heap overflows. | |
1806 | ||
345c905d JK |
1807 | config SLUB_CPU_PARTIAL |
1808 | default y | |
b39ffbf8 | 1809 | depends on SLUB && SMP |
345c905d JK |
1810 | bool "SLUB per cpu partial cache" |
1811 | help | |
1812 | Per cpu partial caches accellerate objects allocation and freeing | |
1813 | that is local to a processor at the price of more indeterminism | |
1814 | in the latency of the free. On overflow these caches will be cleared | |
1815 | which requires the taking of locks that may cause latency spikes. | |
1816 | Typically one would choose no for a realtime system. | |
1817 | ||
ea637639 JZ |
1818 | config MMAP_ALLOW_UNINITIALIZED |
1819 | bool "Allow mmapped anonymous memory to be uninitialized" | |
6a108a14 | 1820 | depends on EXPERT && !MMU |
ea637639 JZ |
1821 | default n |
1822 | help | |
1823 | Normally, and according to the Linux spec, anonymous memory obtained | |
1824 | from mmap() has it's contents cleared before it is passed to | |
1825 | userspace. Enabling this config option allows you to request that | |
1826 | mmap() skip that if it is given an MAP_UNINITIALIZED flag, thus | |
1827 | providing a huge performance boost. If this option is not enabled, | |
1828 | then the flag will be ignored. | |
1829 | ||
1830 | This is taken advantage of by uClibc's malloc(), and also by | |
1831 | ELF-FDPIC binfmt's brk and stack allocator. | |
1832 | ||
1833 | Because of the obvious security issues, this option should only be | |
1834 | enabled on embedded devices where you control what is run in | |
1835 | userspace. Since that isn't generally a problem on no-MMU systems, | |
1836 | it is normally safe to say Y here. | |
1837 | ||
1838 | See Documentation/nommu-mmap.txt for more information. | |
1839 | ||
091f6e26 DH |
1840 | config SYSTEM_DATA_VERIFICATION |
1841 | def_bool n | |
1842 | select SYSTEM_TRUSTED_KEYRING | |
1843 | select KEYS | |
1844 | select CRYPTO | |
d43de6c7 | 1845 | select CRYPTO_RSA |
091f6e26 DH |
1846 | select ASYMMETRIC_KEY_TYPE |
1847 | select ASYMMETRIC_PUBLIC_KEY_SUBTYPE | |
091f6e26 DH |
1848 | select ASN1 |
1849 | select OID_REGISTRY | |
1850 | select X509_CERTIFICATE_PARSER | |
1851 | select PKCS7_MESSAGE_PARSER | |
82c04ff8 | 1852 | help |
091f6e26 DH |
1853 | Provide PKCS#7 message verification using the contents of the system |
1854 | trusted keyring to provide public keys. This then can be used for | |
1855 | module verification, kexec image verification and firmware blob | |
1856 | verification. | |
82c04ff8 | 1857 | |
125e5645 | 1858 | config PROFILING |
b309a294 | 1859 | bool "Profiling support" |
125e5645 MD |
1860 | help |
1861 | Say Y here to enable the extended profiling support mechanisms used | |
1862 | by profilers such as OProfile. | |
1863 | ||
5f87f112 IM |
1864 | # |
1865 | # Place an empty function call at each tracepoint site. Can be | |
1866 | # dynamically changed for a probe function. | |
1867 | # | |
97e1c18e | 1868 | config TRACEPOINTS |
5f87f112 | 1869 | bool |
97e1c18e | 1870 | |
fb32e03f MD |
1871 | source "arch/Kconfig" |
1872 | ||
1da177e4 LT |
1873 | endmenu # General setup |
1874 | ||
ee7e5516 DES |
1875 | config HAVE_GENERIC_DMA_COHERENT |
1876 | bool | |
1877 | default n | |
1878 | ||
158a9624 LT |
1879 | config SLABINFO |
1880 | bool | |
1881 | depends on PROC_FS | |
0f389ec6 | 1882 | depends on SLAB || SLUB_DEBUG |
158a9624 LT |
1883 | default y |
1884 | ||
ae81f9e3 | 1885 | config RT_MUTEXES |
6341e62b | 1886 | bool |
ae81f9e3 | 1887 | |
1da177e4 LT |
1888 | config BASE_SMALL |
1889 | int | |
1890 | default 0 if BASE_FULL | |
1891 | default 1 if !BASE_FULL | |
1892 | ||
66da5733 | 1893 | menuconfig MODULES |
1da177e4 | 1894 | bool "Enable loadable module support" |
11097a03 | 1895 | option modules |
1da177e4 LT |
1896 | help |
1897 | Kernel modules are small pieces of compiled code which can | |
1898 | be inserted in the running kernel, rather than being | |
1899 | permanently built into the kernel. You use the "modprobe" | |
1900 | tool to add (and sometimes remove) them. If you say Y here, | |
1901 | many parts of the kernel can be built as modules (by | |
1902 | answering M instead of Y where indicated): this is most | |
1903 | useful for infrequently used options which are not required | |
1904 | for booting. For more information, see the man pages for | |
1905 | modprobe, lsmod, modinfo, insmod and rmmod. | |
1906 | ||
1907 | If you say Y here, you will need to run "make | |
1908 | modules_install" to put the modules under /lib/modules/ | |
1909 | where modprobe can find them (you may need to be root to do | |
1910 | this). | |
1911 | ||
1912 | If unsure, say Y. | |
1913 | ||
0b0de144 RD |
1914 | if MODULES |
1915 | ||
826e4506 LT |
1916 | config MODULE_FORCE_LOAD |
1917 | bool "Forced module loading" | |
826e4506 LT |
1918 | default n |
1919 | help | |
91e37a79 RR |
1920 | Allow loading of modules without version information (ie. modprobe |
1921 | --force). Forced module loading sets the 'F' (forced) taint flag and | |
1922 | is usually a really bad idea. | |
826e4506 | 1923 | |
1da177e4 LT |
1924 | config MODULE_UNLOAD |
1925 | bool "Module unloading" | |
1da177e4 LT |
1926 | help |
1927 | Without this option you will not be able to unload any | |
1928 | modules (note that some modules may not be unloadable | |
f7f5b675 DV |
1929 | anyway), which makes your kernel smaller, faster |
1930 | and simpler. If unsure, say Y. | |
1da177e4 LT |
1931 | |
1932 | config MODULE_FORCE_UNLOAD | |
1933 | bool "Forced module unloading" | |
19c92399 | 1934 | depends on MODULE_UNLOAD |
1da177e4 LT |
1935 | help |
1936 | This option allows you to force a module to unload, even if the | |
1937 | kernel believes it is unsafe: the kernel will remove the module | |
1938 | without waiting for anyone to stop using it (using the -f option to | |
1939 | rmmod). This is mainly for kernel developers and desperate users. | |
1940 | If unsure, say N. | |
1941 | ||
1da177e4 | 1942 | config MODVERSIONS |
0d541643 | 1943 | bool "Module versioning support" |
1da177e4 LT |
1944 | help |
1945 | Usually, you have to use modules compiled with your kernel. | |
1946 | Saying Y here makes it sometimes possible to use modules | |
1947 | compiled for different kernels, by adding enough information | |
1948 | to the modules to (hopefully) spot any changes which would | |
1949 | make them incompatible with the kernel you are running. If | |
1950 | unsure, say N. | |
1951 | ||
1952 | config MODULE_SRCVERSION_ALL | |
1953 | bool "Source checksum for all modules" | |
1da177e4 LT |
1954 | help |
1955 | Modules which contain a MODULE_VERSION get an extra "srcversion" | |
1956 | field inserted into their modinfo section, which contains a | |
1957 | sum of the source files which made it. This helps maintainers | |
1958 | see exactly which source was used to build a module (since | |
1959 | others sometimes change the module source without updating | |
1960 | the version). With this option, such a "srcversion" field | |
1961 | will be created for all modules. If unsure, say N. | |
1962 | ||
106a4ee2 RR |
1963 | config MODULE_SIG |
1964 | bool "Module signature verification" | |
1965 | depends on MODULES | |
091f6e26 | 1966 | select SYSTEM_DATA_VERIFICATION |
106a4ee2 RR |
1967 | help |
1968 | Check modules for valid signatures upon load: the signature | |
1969 | is simply appended to the module. For more information see | |
1970 | Documentation/module-signing.txt. | |
1971 | ||
228c37ff DH |
1972 | Note that this option adds the OpenSSL development packages as a |
1973 | kernel build dependency so that the signing tool can use its crypto | |
1974 | library. | |
1975 | ||
ea0b6dcf DH |
1976 | !!!WARNING!!! If you enable this option, you MUST make sure that the |
1977 | module DOES NOT get stripped after being signed. This includes the | |
1978 | debuginfo strip done by some packagers (such as rpmbuild) and | |
1979 | inclusion into an initramfs that wants the module size reduced. | |
1980 | ||
106a4ee2 RR |
1981 | config MODULE_SIG_FORCE |
1982 | bool "Require modules to be validly signed" | |
1983 | depends on MODULE_SIG | |
1984 | help | |
1985 | Reject unsigned modules or signed modules for which we don't have a | |
1986 | key. Without this, such modules will simply taint the kernel. | |
ea0b6dcf | 1987 | |
d9d8d7ed MM |
1988 | config MODULE_SIG_ALL |
1989 | bool "Automatically sign all modules" | |
1990 | default y | |
1991 | depends on MODULE_SIG | |
1992 | help | |
1993 | Sign all modules during make modules_install. Without this option, | |
1994 | modules must be signed manually, using the scripts/sign-file tool. | |
1995 | ||
1996 | comment "Do not forget to sign required modules with scripts/sign-file" | |
1997 | depends on MODULE_SIG_FORCE && !MODULE_SIG_ALL | |
1998 | ||
ea0b6dcf DH |
1999 | choice |
2000 | prompt "Which hash algorithm should modules be signed with?" | |
2001 | depends on MODULE_SIG | |
2002 | help | |
2003 | This determines which sort of hashing algorithm will be used during | |
2004 | signature generation. This algorithm _must_ be built into the kernel | |
2005 | directly so that signature verification can take place. It is not | |
2006 | possible to load a signed module containing the algorithm to check | |
2007 | the signature on that module. | |
2008 | ||
2009 | config MODULE_SIG_SHA1 | |
2010 | bool "Sign modules with SHA-1" | |
2011 | select CRYPTO_SHA1 | |
2012 | ||
2013 | config MODULE_SIG_SHA224 | |
2014 | bool "Sign modules with SHA-224" | |
2015 | select CRYPTO_SHA256 | |
2016 | ||
2017 | config MODULE_SIG_SHA256 | |
2018 | bool "Sign modules with SHA-256" | |
2019 | select CRYPTO_SHA256 | |
2020 | ||
2021 | config MODULE_SIG_SHA384 | |
2022 | bool "Sign modules with SHA-384" | |
2023 | select CRYPTO_SHA512 | |
2024 | ||
2025 | config MODULE_SIG_SHA512 | |
2026 | bool "Sign modules with SHA-512" | |
2027 | select CRYPTO_SHA512 | |
2028 | ||
2029 | endchoice | |
2030 | ||
22753674 MM |
2031 | config MODULE_SIG_HASH |
2032 | string | |
2033 | depends on MODULE_SIG | |
2034 | default "sha1" if MODULE_SIG_SHA1 | |
2035 | default "sha224" if MODULE_SIG_SHA224 | |
2036 | default "sha256" if MODULE_SIG_SHA256 | |
2037 | default "sha384" if MODULE_SIG_SHA384 | |
2038 | default "sha512" if MODULE_SIG_SHA512 | |
2039 | ||
beb50df3 BJ |
2040 | config MODULE_COMPRESS |
2041 | bool "Compress modules on installation" | |
2042 | depends on MODULES | |
2043 | help | |
beb50df3 | 2044 | |
b6c09b51 RR |
2045 | Compresses kernel modules when 'make modules_install' is run; gzip or |
2046 | xz depending on "Compression algorithm" below. | |
beb50df3 | 2047 | |
b6c09b51 | 2048 | module-init-tools MAY support gzip, and kmod MAY support gzip and xz. |
beb50df3 | 2049 | |
b6c09b51 RR |
2050 | Out-of-tree kernel modules installed using Kbuild will also be |
2051 | compressed upon installation. | |
beb50df3 | 2052 | |
b6c09b51 RR |
2053 | Note: for modules inside an initrd or initramfs, it's more efficient |
2054 | to compress the whole initrd or initramfs instead. | |
beb50df3 | 2055 | |
b6c09b51 RR |
2056 | Note: This is fully compatible with signed modules. |
2057 | ||
2058 | If in doubt, say N. | |
beb50df3 BJ |
2059 | |
2060 | choice | |
2061 | prompt "Compression algorithm" | |
2062 | depends on MODULE_COMPRESS | |
2063 | default MODULE_COMPRESS_GZIP | |
2064 | help | |
2065 | This determines which sort of compression will be used during | |
2066 | 'make modules_install'. | |
2067 | ||
2068 | GZIP (default) and XZ are supported. | |
2069 | ||
2070 | config MODULE_COMPRESS_GZIP | |
2071 | bool "GZIP" | |
2072 | ||
2073 | config MODULE_COMPRESS_XZ | |
2074 | bool "XZ" | |
2075 | ||
2076 | endchoice | |
2077 | ||
dbacb0ef NP |
2078 | config TRIM_UNUSED_KSYMS |
2079 | bool "Trim unused exported kernel symbols" | |
2080 | depends on MODULES && !UNUSED_SYMBOLS | |
2081 | help | |
2082 | The kernel and some modules make many symbols available for | |
2083 | other modules to use via EXPORT_SYMBOL() and variants. Depending | |
2084 | on the set of modules being selected in your kernel configuration, | |
2085 | many of those exported symbols might never be used. | |
2086 | ||
2087 | This option allows for unused exported symbols to be dropped from | |
2088 | the build. In turn, this provides the compiler more opportunities | |
2089 | (especially when using LTO) for optimizing the code and reducing | |
2090 | binary size. This might have some security advantages as well. | |
2091 | ||
f1cb637e | 2092 | If unsure, or if you need to build out-of-tree modules, say N. |
dbacb0ef | 2093 | |
0b0de144 RD |
2094 | endif # MODULES |
2095 | ||
6c9692e2 PZ |
2096 | config MODULES_TREE_LOOKUP |
2097 | def_bool y | |
2098 | depends on PERF_EVENTS || TRACING | |
2099 | ||
98a79d6a RR |
2100 | config INIT_ALL_POSSIBLE |
2101 | bool | |
2102 | help | |
5f054e31 RR |
2103 | Back when each arch used to define their own cpu_online_mask and |
2104 | cpu_possible_mask, some of them chose to initialize cpu_possible_mask | |
98a79d6a RR |
2105 | with all 1s, and others with all 0s. When they were centralised, |
2106 | it was better to provide this option than to break all the archs | |
692105b8 | 2107 | and have several arch maintainers pursuing me down dark alleys. |
98a79d6a | 2108 | |
3a65dfe8 | 2109 | source "block/Kconfig" |
e98c3202 AK |
2110 | |
2111 | config PREEMPT_NOTIFIERS | |
2112 | bool | |
e260be67 | 2113 | |
16295bec SK |
2114 | config PADATA |
2115 | depends on SMP | |
2116 | bool | |
2117 | ||
754b7b63 AK |
2118 | # Can be selected by architectures with broken toolchains |
2119 | # that get confused by correct const<->read_only section | |
2120 | # mappings | |
2121 | config BROKEN_RODATA | |
2122 | bool | |
2123 | ||
4520c6a4 DH |
2124 | config ASN1 |
2125 | tristate | |
2126 | help | |
2127 | Build a simple ASN.1 grammar compiler that produces a bytecode output | |
2128 | that can be interpreted by the ASN.1 stream decoder and used to | |
2129 | inform it as to what tags are to be expected in a stream and what | |
2130 | functions to call on what tags. | |
2131 | ||
6beb0009 | 2132 | source "kernel/Kconfig.locks" |