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