1# SPDX-License-Identifier: GPL-2.0-only 2 3source "scripts/Kconfig.toolchain" 4 5config CONSTRUCTORS 6 bool 7 8config IRQ_WORK 9 def_bool y if SMP 10 11config BUILDTIME_TABLE_SORT 12 bool 13 14config THREAD_INFO_IN_TASK 15 bool 16 help 17 Select this to move thread_info off the stack into task_struct. To 18 make this work, an arch will need to remove all thread_info fields 19 except flags and fix any runtime bugs. 20 21 One subtle change that will be needed is to use try_get_task_stack() 22 and put_task_stack() in save_thread_stack_tsk() and get_wchan(). 23 24menu "General setup" 25 26config BROKEN 27 bool 28 help 29 This option allows you to choose whether you want to try to 30 compile (and fix) old drivers that haven't been updated to 31 new infrastructure. 32 33config BROKEN_ON_SMP 34 bool 35 depends on BROKEN || !SMP 36 default y 37 38config INIT_ENV_ARG_LIMIT 39 int 40 default 32 if !UML 41 default 128 if UML 42 help 43 Maximum of each of the number of arguments and environment 44 variables passed to init from the kernel command line. 45 46config COMPILE_TEST 47 bool "Compile also drivers which will not load" 48 depends on HAS_IOMEM 49 help 50 Some drivers can be compiled on a different platform than they are 51 intended to be run on. Despite they cannot be loaded there (or even 52 when they load they cannot be used due to missing HW support), 53 developers still, opposing to distributors, might want to build such 54 drivers to compile-test them. 55 56 If you are a developer and want to build everything available, say Y 57 here. If you are a user/distributor, say N here to exclude useless 58 drivers to be distributed. 59 60config WERROR 61 bool "Compile the kernel with warnings as errors" 62 default COMPILE_TEST 63 help 64 A kernel build should not cause any compiler warnings, and this 65 enables the '-Werror' (for C) and '-Dwarnings' (for Rust) flags 66 to enforce that rule by default. Certain warnings from other tools 67 such as the linker may be upgraded to errors with this option as 68 well. 69 70 However, if you have a new (or very old) compiler or linker with odd 71 and unusual warnings, or you have some architecture with problems, 72 you may need to disable this config option in order to 73 successfully build the kernel. 74 75 If in doubt, say Y. 76 77config UAPI_HEADER_TEST 78 bool "Compile test UAPI headers" 79 depends on HEADERS_INSTALL 80 help 81 Compile test headers exported to user-space to ensure they are 82 self-contained, i.e. compilable as standalone units. 83 84 If you are a developer or tester and want to ensure the exported 85 headers are self-contained, say Y here. Otherwise, choose N. 86 87config LOCALVERSION 88 string "Local version - append to kernel release" 89 help 90 Append an extra string to the end of your kernel version. 91 This will show up when you type uname, for example. 92 The string you set here will be appended after the contents of 93 any files with a filename matching localversion* in your 94 object and source tree, in that order. Your total string can 95 be a maximum of 64 characters. 96 97config LOCALVERSION_AUTO 98 bool "Automatically append version information to the version string" 99 default y 100 depends on !COMPILE_TEST 101 help 102 This will try to automatically determine if the current tree is a 103 release tree by looking for git tags that belong to the current 104 top of tree revision. 105 106 A string of the format -gxxxxxxxx will be added to the localversion 107 if a git-based tree is found. The string generated by this will be 108 appended after any matching localversion* files, and after the value 109 set in CONFIG_LOCALVERSION. 110 111 (The actual string used here is the first 12 characters produced 112 by running the command: 113 114 $ git rev-parse --verify HEAD 115 116 which is done within the script "scripts/setlocalversion".) 117 118config BUILD_SALT 119 string "Build ID Salt" 120 default "" 121 help 122 The build ID is used to link binaries and their debug info. Setting 123 this option will use the value in the calculation of the build id. 124 This is mostly useful for distributions which want to ensure the 125 build is unique between builds. It's safe to leave the default. 126 127config HAVE_KERNEL_GZIP 128 bool 129 130config HAVE_KERNEL_BZIP2 131 bool 132 133config HAVE_KERNEL_LZMA 134 bool 135 136config HAVE_KERNEL_XZ 137 bool 138 139config HAVE_KERNEL_LZO 140 bool 141 142config HAVE_KERNEL_LZ4 143 bool 144 145config HAVE_KERNEL_ZSTD 146 bool 147 148config HAVE_KERNEL_UNCOMPRESSED 149 bool 150 151choice 152 prompt "Kernel compression mode" 153 default KERNEL_GZIP 154 depends on HAVE_KERNEL_GZIP || HAVE_KERNEL_BZIP2 || HAVE_KERNEL_LZMA || HAVE_KERNEL_XZ || HAVE_KERNEL_LZO || HAVE_KERNEL_LZ4 || HAVE_KERNEL_ZSTD || HAVE_KERNEL_UNCOMPRESSED 155 help 156 The linux kernel is a kind of self-extracting executable. 157 Several compression algorithms are available, which differ 158 in efficiency, compression and decompression speed. 159 Compression speed is only relevant when building a kernel. 160 Decompression speed is relevant at each boot. 161 162 If you have any problems with bzip2 or lzma compressed 163 kernels, mail me (Alain Knaff) <alain@knaff.lu>. (An older 164 version of this functionality (bzip2 only), for 2.4, was 165 supplied by Christian Ludwig) 166 167 High compression options are mostly useful for users, who 168 are low on disk space (embedded systems), but for whom ram 169 size matters less. 170 171 If in doubt, select 'gzip' 172 173config KERNEL_GZIP 174 bool "Gzip" 175 depends on HAVE_KERNEL_GZIP 176 help 177 The old and tried gzip compression. It provides a good balance 178 between compression ratio and decompression speed. 179 180config KERNEL_BZIP2 181 bool "Bzip2" 182 depends on HAVE_KERNEL_BZIP2 183 help 184 Its compression ratio and speed is intermediate. 185 Decompression speed is slowest among the choices. The kernel 186 size is about 10% smaller with bzip2, in comparison to gzip. 187 Bzip2 uses a large amount of memory. For modern kernels you 188 will need at least 8MB RAM or more for booting. 189 190config KERNEL_LZMA 191 bool "LZMA" 192 depends on HAVE_KERNEL_LZMA 193 help 194 This compression algorithm's ratio is best. Decompression speed 195 is between gzip and bzip2. Compression is slowest. 196 The kernel size is about 33% smaller with LZMA in comparison to gzip. 197 198config KERNEL_XZ 199 bool "XZ" 200 depends on HAVE_KERNEL_XZ 201 help 202 XZ uses the LZMA2 algorithm and instruction set specific 203 BCJ filters which can improve compression ratio of executable 204 code. The size of the kernel is about 30% smaller with XZ in 205 comparison to gzip. On architectures for which there is a BCJ 206 filter (i386, x86_64, ARM, ARM64, RISC-V, big endian PowerPC, 207 and SPARC), XZ will create a few percent smaller kernel than 208 plain LZMA. 209 210 The speed is about the same as with LZMA: The decompression 211 speed of XZ is better than that of bzip2 but worse than gzip 212 and LZO. Compression is slow. 213 214config KERNEL_LZO 215 bool "LZO" 216 depends on HAVE_KERNEL_LZO 217 help 218 Its compression ratio is the poorest among the choices. The kernel 219 size is about 10% bigger than gzip; however its speed 220 (both compression and decompression) is the fastest. 221 222config KERNEL_LZ4 223 bool "LZ4" 224 depends on HAVE_KERNEL_LZ4 225 help 226 LZ4 is an LZ77-type compressor with a fixed, byte-oriented encoding. 227 A preliminary version of LZ4 de/compression tool is available at 228 <https://code.google.com/p/lz4/>. 229 230 Its compression ratio is worse than LZO. The size of the kernel 231 is about 8% bigger than LZO. But the decompression speed is 232 faster than LZO. 233 234config KERNEL_ZSTD 235 bool "ZSTD" 236 depends on HAVE_KERNEL_ZSTD 237 help 238 ZSTD is a compression algorithm targeting intermediate compression 239 with fast decompression speed. It will compress better than GZIP and 240 decompress around the same speed as LZO, but slower than LZ4. You 241 will need at least 192 KB RAM or more for booting. The zstd command 242 line tool is required for compression. 243 244config KERNEL_UNCOMPRESSED 245 bool "None" 246 depends on HAVE_KERNEL_UNCOMPRESSED 247 help 248 Produce uncompressed kernel image. This option is usually not what 249 you want. It is useful for debugging the kernel in slow simulation 250 environments, where decompressing and moving the kernel is awfully 251 slow. This option allows early boot code to skip the decompressor 252 and jump right at uncompressed kernel image. 253 254endchoice 255 256config DEFAULT_INIT 257 string "Default init path" 258 default "" 259 help 260 This option determines the default init for the system if no init= 261 option is passed on the kernel command line. If the requested path is 262 not present, we will still then move on to attempting further 263 locations (e.g. /sbin/init, etc). If this is empty, we will just use 264 the fallback list when init= is not passed. 265 266config DEFAULT_HOSTNAME 267 string "Default hostname" 268 default "(none)" 269 help 270 This option determines the default system hostname before userspace 271 calls sethostname(2). The kernel traditionally uses "(none)" here, 272 but you may wish to use a different default here to make a minimal 273 system more usable with less configuration. 274 275config SYSVIPC 276 bool "System V IPC" 277 help 278 Inter Process Communication is a suite of library functions and 279 system calls which let processes (running programs) synchronize and 280 exchange information. It is generally considered to be a good thing, 281 and some programs won't run unless you say Y here. In particular, if 282 you want to run the DOS emulator dosemu under Linux (read the 283 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>), 284 you'll need to say Y here. 285 286 You can find documentation about IPC with "info ipc" and also in 287 section 6.4 of the Linux Programmer's Guide, available from 288 <http://www.tldp.org/guides.html>. 289 290config SYSVIPC_SYSCTL 291 bool 292 depends on SYSVIPC 293 depends on SYSCTL 294 default y 295 296config SYSVIPC_COMPAT 297 def_bool y 298 depends on COMPAT && SYSVIPC 299 300config POSIX_MQUEUE 301 bool "POSIX Message Queues" 302 depends on NET 303 help 304 POSIX variant of message queues is a part of IPC. In POSIX message 305 queues every message has a priority which decides about succession 306 of receiving it by a process. If you want to compile and run 307 programs written e.g. for Solaris with use of its POSIX message 308 queues (functions mq_*) say Y here. 309 310 POSIX message queues are visible as a filesystem called 'mqueue' 311 and can be mounted somewhere if you want to do filesystem 312 operations on message queues. 313 314 If unsure, say Y. 315 316config POSIX_MQUEUE_SYSCTL 317 bool 318 depends on POSIX_MQUEUE 319 depends on SYSCTL 320 default y 321 322config WATCH_QUEUE 323 bool "General notification queue" 324 default n 325 help 326 327 This is a general notification queue for the kernel to pass events to 328 userspace by splicing them into pipes. It can be used in conjunction 329 with watches for key/keyring change notifications and device 330 notifications. 331 332 See Documentation/core-api/watch_queue.rst 333 334config CROSS_MEMORY_ATTACH 335 bool "Enable process_vm_readv/writev syscalls" 336 depends on MMU 337 default y 338 help 339 Enabling this option adds the system calls process_vm_readv and 340 process_vm_writev which allow a process with the correct privileges 341 to directly read from or write to another process' address space. 342 See the man page for more details. 343 344config AUDIT 345 bool "Auditing support" 346 depends on NET 347 help 348 Enable auditing infrastructure that can be used with another 349 kernel subsystem, such as SELinux (which requires this for 350 logging of avc messages output). System call auditing is included 351 on architectures which support it. 352 353config HAVE_ARCH_AUDITSYSCALL 354 bool 355 356config AUDITSYSCALL 357 def_bool y 358 depends on AUDIT && HAVE_ARCH_AUDITSYSCALL 359 select FSNOTIFY 360 361source "kernel/irq/Kconfig" 362source "kernel/time/Kconfig" 363source "kernel/bpf/Kconfig" 364source "kernel/Kconfig.preempt" 365 366menu "CPU/Task time and stats accounting" 367 368config VIRT_CPU_ACCOUNTING 369 bool 370 371choice 372 prompt "Cputime accounting" 373 default VIRT_CPU_ACCOUNTING_GEN if NO_HZ_FULL 374 default TICK_CPU_ACCOUNTING 375 376# Kind of a stub config for the pure tick based cputime accounting 377config TICK_CPU_ACCOUNTING 378 bool "Simple tick based cputime accounting" 379 depends on !S390 && !NO_HZ_FULL 380 help 381 This is the basic tick based cputime accounting that maintains 382 statistics about user, system and idle time spent on per jiffies 383 granularity. 384 385 If unsure, say Y. 386 387config VIRT_CPU_ACCOUNTING_NATIVE 388 bool "Deterministic task and CPU time accounting" 389 depends on HAVE_VIRT_CPU_ACCOUNTING && !NO_HZ_FULL 390 select VIRT_CPU_ACCOUNTING 391 help 392 Select this option to enable more accurate task and CPU time 393 accounting. This is done by reading a CPU counter on each 394 kernel entry and exit and on transitions within the kernel 395 between system, softirq and hardirq state, so there is a 396 small performance impact. In the case of s390 or IBM POWER > 5, 397 this also enables accounting of stolen time on logically-partitioned 398 systems. 399 400config VIRT_CPU_ACCOUNTING_GEN 401 bool "Full dynticks CPU time accounting" 402 depends on HAVE_CONTEXT_TRACKING_USER 403 depends on HAVE_VIRT_CPU_ACCOUNTING_GEN 404 depends on GENERIC_CLOCKEVENTS 405 select VIRT_CPU_ACCOUNTING 406 select CONTEXT_TRACKING_USER 407 help 408 Select this option to enable task and CPU time accounting on full 409 dynticks systems. This accounting is implemented by watching every 410 kernel-user boundaries using the context tracking subsystem. 411 The accounting is thus performed at the expense of some significant 412 overhead. 413 414 For now this is only useful if you are working on the full 415 dynticks subsystem development. 416 417 If unsure, say N. 418 419endchoice 420 421config IRQ_TIME_ACCOUNTING 422 bool "Fine granularity task level IRQ time accounting" 423 depends on HAVE_IRQ_TIME_ACCOUNTING && !VIRT_CPU_ACCOUNTING_NATIVE 424 help 425 Select this option to enable fine granularity task irq time 426 accounting. This is done by reading a timestamp on each 427 transitions between softirq and hardirq state, so there can be a 428 small performance impact. 429 430 If in doubt, say N here. 431 432config HAVE_SCHED_AVG_IRQ 433 def_bool y 434 depends on IRQ_TIME_ACCOUNTING || PARAVIRT_TIME_ACCOUNTING 435 depends on SMP 436 437config SCHED_HW_PRESSURE 438 bool 439 default y if ARM && ARM_CPU_TOPOLOGY 440 default y if ARM64 441 depends on SMP 442 depends on CPU_FREQ_THERMAL 443 help 444 Select this option to enable HW pressure accounting in the 445 scheduler. HW pressure is the value conveyed to the scheduler 446 that reflects the reduction in CPU compute capacity resulted from 447 HW throttling. HW throttling occurs when the performance of 448 a CPU is capped due to high operating temperatures as an example. 449 450 If selected, the scheduler will be able to balance tasks accordingly, 451 i.e. put less load on throttled CPUs than on non/less throttled ones. 452 453 This requires the architecture to implement 454 arch_update_hw_pressure() and arch_scale_thermal_pressure(). 455 456config BSD_PROCESS_ACCT 457 bool "BSD Process Accounting (DEPRECATED)" 458 depends on MULTIUSER 459 default n 460 help 461 If you say Y here, a user level program will be able to instruct the 462 kernel (via a special system call) to write process accounting 463 information to a file: whenever a process exits, information about 464 that process will be appended to the file by the kernel. The 465 information includes things such as creation time, owning user, 466 command name, memory usage, controlling terminal etc. (the complete 467 list is in the struct acct in <file:include/linux/acct.h>). It is 468 up to the user level program to do useful things with this 469 information. This mechanism is antiquated and has significant 470 scalability issues. You probably want to use eBPF instead. Say 471 N unless you really need this. 472 473config BSD_PROCESS_ACCT_V3 474 bool "BSD Process Accounting version 3 file format" 475 depends on BSD_PROCESS_ACCT 476 default n 477 help 478 If you say Y here, the process accounting information is written 479 in a new file format that also logs the process IDs of each 480 process and its parent. Note that this file format is incompatible 481 with previous v0/v1/v2 file formats, so you will need updated tools 482 for processing it. A preliminary version of these tools is available 483 at <http://www.gnu.org/software/acct/>. 484 485config TASKSTATS 486 bool "Export task/process statistics through netlink" 487 depends on NET 488 depends on MULTIUSER 489 default n 490 help 491 Export selected statistics for tasks/processes through the 492 generic netlink interface. Unlike BSD process accounting, the 493 statistics are available during the lifetime of tasks/processes as 494 responses to commands. Like BSD accounting, they are sent to user 495 space on task exit. 496 497 Say N if unsure. 498 499config TASK_DELAY_ACCT 500 bool "Enable per-task delay accounting" 501 depends on TASKSTATS 502 select SCHED_INFO 503 help 504 Collect information on time spent by a task waiting for system 505 resources like cpu, synchronous block I/O completion and swapping 506 in pages. Such statistics can help in setting a task's priorities 507 relative to other tasks for cpu, io, rss limits etc. 508 509 Say N if unsure. 510 511config TASK_XACCT 512 bool "Enable extended accounting over taskstats" 513 depends on TASKSTATS 514 help 515 Collect extended task accounting data and send the data 516 to userland for processing over the taskstats interface. 517 518 Say N if unsure. 519 520config TASK_IO_ACCOUNTING 521 bool "Enable per-task storage I/O accounting" 522 depends on TASK_XACCT 523 help 524 Collect information on the number of bytes of storage I/O which this 525 task has caused. 526 527 Say N if unsure. 528 529config PSI 530 bool "Pressure stall information tracking" 531 select KERNFS 532 help 533 Collect metrics that indicate how overcommitted the CPU, memory, 534 and IO capacity are in the system. 535 536 If you say Y here, the kernel will create /proc/pressure/ with the 537 pressure statistics files cpu, memory, and io. These will indicate 538 the share of walltime in which some or all tasks in the system are 539 delayed due to contention of the respective resource. 540 541 In kernels with cgroup support, cgroups (cgroup2 only) will 542 have cpu.pressure, memory.pressure, and io.pressure files, 543 which aggregate pressure stalls for the grouped tasks only. 544 545 For more details see Documentation/accounting/psi.rst. 546 547 Say N if unsure. 548 549config PSI_DEFAULT_DISABLED 550 bool "Require boot parameter to enable pressure stall information tracking" 551 default n 552 depends on PSI 553 help 554 If set, pressure stall information tracking will be disabled 555 per default but can be enabled through passing psi=1 on the 556 kernel commandline during boot. 557 558 This feature adds some code to the task wakeup and sleep 559 paths of the scheduler. The overhead is too low to affect 560 common scheduling-intense workloads in practice (such as 561 webservers, memcache), but it does show up in artificial 562 scheduler stress tests, such as hackbench. 563 564 If you are paranoid and not sure what the kernel will be 565 used for, say Y. 566 567 Say N if unsure. 568 569endmenu # "CPU/Task time and stats accounting" 570 571config CPU_ISOLATION 572 bool "CPU isolation" 573 depends on SMP 574 default y 575 help 576 Make sure that CPUs running critical tasks are not disturbed by 577 any source of "noise" such as unbound workqueues, timers, kthreads... 578 Unbound jobs get offloaded to housekeeping CPUs. This is driven by 579 the "isolcpus=" boot parameter. 580 581 Say Y if unsure. 582 583source "kernel/rcu/Kconfig" 584 585config IKCONFIG 586 tristate "Kernel .config support" 587 help 588 This option enables the complete Linux kernel ".config" file 589 contents to be saved in the kernel. It provides documentation 590 of which kernel options are used in a running kernel or in an 591 on-disk kernel. This information can be extracted from the kernel 592 image file with the script scripts/extract-ikconfig and used as 593 input to rebuild the current kernel or to build another kernel. 594 It can also be extracted from a running kernel by reading 595 /proc/config.gz if enabled (below). 596 597config IKCONFIG_PROC 598 bool "Enable access to .config through /proc/config.gz" 599 depends on IKCONFIG && PROC_FS 600 help 601 This option enables access to the kernel configuration file 602 through /proc/config.gz. 603 604config IKHEADERS 605 tristate "Enable kernel headers through /sys/kernel/kheaders.tar.xz" 606 depends on SYSFS 607 help 608 This option enables access to the in-kernel headers that are generated during 609 the build process. These can be used to build eBPF tracing programs, 610 or similar programs. If you build the headers as a module, a module called 611 kheaders.ko is built which can be loaded on-demand to get access to headers. 612 613config LOG_BUF_SHIFT 614 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" 615 range 12 25 616 default 17 617 depends on PRINTK 618 help 619 Select the minimal kernel log buffer size as a power of 2. 620 The final size is affected by LOG_CPU_MAX_BUF_SHIFT config 621 parameter, see below. Any higher size also might be forced 622 by "log_buf_len" boot parameter. 623 624 Examples: 625 17 => 128 KB 626 16 => 64 KB 627 15 => 32 KB 628 14 => 16 KB 629 13 => 8 KB 630 12 => 4 KB 631 632config LOG_CPU_MAX_BUF_SHIFT 633 int "CPU kernel log buffer size contribution (13 => 8 KB, 17 => 128KB)" 634 depends on SMP 635 range 0 21 636 default 0 if BASE_SMALL 637 default 12 638 depends on PRINTK 639 help 640 This option allows to increase the default ring buffer size 641 according to the number of CPUs. The value defines the contribution 642 of each CPU as a power of 2. The used space is typically only few 643 lines however it might be much more when problems are reported, 644 e.g. backtraces. 645 646 The increased size means that a new buffer has to be allocated and 647 the original static one is unused. It makes sense only on systems 648 with more CPUs. Therefore this value is used only when the sum of 649 contributions is greater than the half of the default kernel ring 650 buffer as defined by LOG_BUF_SHIFT. The default values are set 651 so that more than 16 CPUs are needed to trigger the allocation. 652 653 Also this option is ignored when "log_buf_len" kernel parameter is 654 used as it forces an exact (power of two) size of the ring buffer. 655 656 The number of possible CPUs is used for this computation ignoring 657 hotplugging making the computation optimal for the worst case 658 scenario while allowing a simple algorithm to be used from bootup. 659 660 Examples shift values and their meaning: 661 17 => 128 KB for each CPU 662 16 => 64 KB for each CPU 663 15 => 32 KB for each CPU 664 14 => 16 KB for each CPU 665 13 => 8 KB for each CPU 666 12 => 4 KB for each CPU 667 668config PRINTK_INDEX 669 bool "Printk indexing debugfs interface" 670 depends on PRINTK && DEBUG_FS 671 help 672 Add support for indexing of all printk formats known at compile time 673 at <debugfs>/printk/index/<module>. 674 675 This can be used as part of maintaining daemons which monitor 676 /dev/kmsg, as it permits auditing the printk formats present in a 677 kernel, allowing detection of cases where monitored printks are 678 changed or no longer present. 679 680 There is no additional runtime cost to printk with this enabled. 681 682# 683# Architectures with an unreliable sched_clock() should select this: 684# 685config HAVE_UNSTABLE_SCHED_CLOCK 686 bool 687 688config GENERIC_SCHED_CLOCK 689 bool 690 691menu "Scheduler features" 692 693config UCLAMP_TASK 694 bool "Enable utilization clamping for RT/FAIR tasks" 695 depends on CPU_FREQ_GOV_SCHEDUTIL 696 help 697 This feature enables the scheduler to track the clamped utilization 698 of each CPU based on RUNNABLE tasks scheduled on that CPU. 699 700 With this option, the user can specify the min and max CPU 701 utilization allowed for RUNNABLE tasks. The max utilization defines 702 the maximum frequency a task should use while the min utilization 703 defines the minimum frequency it should use. 704 705 Both min and max utilization clamp values are hints to the scheduler, 706 aiming at improving its frequency selection policy, but they do not 707 enforce or grant any specific bandwidth for tasks. 708 709 If in doubt, say N. 710 711config UCLAMP_BUCKETS_COUNT 712 int "Number of supported utilization clamp buckets" 713 range 5 20 714 default 5 715 depends on UCLAMP_TASK 716 help 717 Defines the number of clamp buckets to use. The range of each bucket 718 will be SCHED_CAPACITY_SCALE/UCLAMP_BUCKETS_COUNT. The higher the 719 number of clamp buckets the finer their granularity and the higher 720 the precision of clamping aggregation and tracking at run-time. 721 722 For example, with the minimum configuration value we will have 5 723 clamp buckets tracking 20% utilization each. A 25% boosted tasks will 724 be refcounted in the [20..39]% bucket and will set the bucket clamp 725 effective value to 25%. 726 If a second 30% boosted task should be co-scheduled on the same CPU, 727 that task will be refcounted in the same bucket of the first task and 728 it will boost the bucket clamp effective value to 30%. 729 The clamp effective value of a bucket is reset to its nominal value 730 (20% in the example above) when there are no more tasks refcounted in 731 that bucket. 732 733 An additional boost/capping margin can be added to some tasks. In the 734 example above the 25% task will be boosted to 30% until it exits the 735 CPU. If that should be considered not acceptable on certain systems, 736 it's always possible to reduce the margin by increasing the number of 737 clamp buckets to trade off used memory for run-time tracking 738 precision. 739 740 If in doubt, use the default value. 741 742config SCHED_PROXY_EXEC 743 bool "Proxy Execution" 744 # Avoid some build failures w/ PREEMPT_RT until it can be fixed 745 depends on !PREEMPT_RT 746 # Not particularly useful until we get to multi-rq proxying 747 depends on EXPERT 748 help 749 This option enables proxy execution, a mechanism for mutex-owning 750 tasks to inherit the scheduling context of higher priority waiters. 751 752endmenu 753 754# 755# For architectures that support present-but-inaccessible (PROT_NONE) page 756# table entries detectable via pte_protnone() / pmd_protnone(): 757# 758config ARCH_HAS_PTE_PROTNONE 759 bool 760 761# 762# For architectures that want to enable the support for NUMA-affine scheduler 763# balancing logic: 764# 765config ARCH_SUPPORTS_NUMA_BALANCING 766 bool 767 768# 769# For architectures that prefer to flush all TLBs after a number of pages 770# are unmapped instead of sending one IPI per page to flush. The architecture 771# must provide guarantees on what happens if a clean TLB cache entry is 772# written after the unmap. Details are in mm/rmap.c near the check for 773# should_defer_flush. The architecture should also consider if the full flush 774# and the refill costs are offset by the savings of sending fewer IPIs. 775config ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH 776 bool 777 778config CC_HAS_INT128 779 def_bool !$(cc-option,$(m64-flag) -D__SIZEOF_INT128__=0) && 64BIT 780 781config CC_IMPLICIT_FALLTHROUGH 782 string 783 default "-Wimplicit-fallthrough=5" if CC_IS_GCC && $(cc-option,-Wimplicit-fallthrough=5) 784 default "-Wimplicit-fallthrough" if CC_IS_CLANG && $(cc-option,-Wunreachable-code-fallthrough) 785 786config CC_MS_EXTENSIONS 787 string 788 default "-fms-anonymous-structs" if $(cc-option,-fms-anonymous-structs) 789 default "-fms-extensions" 790 791# Currently, disable gcc-10+ array-bounds globally. 792# It's still broken in gcc-13, so no upper bound yet. 793config GCC10_NO_ARRAY_BOUNDS 794 def_bool y 795 796config CC_NO_ARRAY_BOUNDS 797 bool 798 default y if CC_IS_GCC && GCC_VERSION >= 90000 && GCC10_NO_ARRAY_BOUNDS 799 800# Currently, disable -Wstringop-overflow for GCC globally. 801config GCC_NO_STRINGOP_OVERFLOW 802 def_bool y 803 804config CC_NO_STRINGOP_OVERFLOW 805 bool 806 default y if CC_IS_GCC && GCC_NO_STRINGOP_OVERFLOW 807 808config CC_STRINGOP_OVERFLOW 809 bool 810 default y if CC_IS_GCC && !CC_NO_STRINGOP_OVERFLOW 811 812# 813# For architectures that know their GCC __int128 support is sound 814# 815config ARCH_SUPPORTS_INT128 816 bool 817 818config NUMA_BALANCING 819 bool "Memory placement aware NUMA scheduler" 820 depends on ARCH_SUPPORTS_NUMA_BALANCING 821 depends on ARCH_HAS_PTE_PROTNONE 822 depends on SMP && NUMA_MIGRATION && !PREEMPT_RT 823 help 824 This option adds support for automatic NUMA aware memory/task placement. 825 The mechanism is quite primitive and is based on migrating memory when 826 it has references to the node the task is running on. 827 828 This system will be inactive on UMA systems. 829 830config SCHED_CACHE 831 bool "Cache aware load balance" 832 default y 833 depends on SMP 834 help 835 When enabled, the scheduler will attempt to aggregate tasks from 836 the same process onto a single Last Level Cache (LLC) domain when 837 possible. This improves cache locality by keeping tasks that share 838 resources within the same cache domain, reducing cache misses and 839 lowering data access latency. 840 841config NUMA_BALANCING_DEFAULT_ENABLED 842 bool "Automatically enable NUMA aware memory/task placement" 843 default y 844 depends on NUMA_BALANCING 845 help 846 If set, automatic NUMA balancing will be enabled if running on a NUMA 847 machine. 848 849config SLAB_OBJ_EXT 850 bool 851 852menuconfig CGROUPS 853 bool "Control Group support" 854 select KERNFS 855 help 856 This option adds support for grouping sets of processes together, for 857 use with process control subsystems such as Cpusets, CFS, memory 858 controls or device isolation. 859 See 860 - Documentation/scheduler/sched-design-CFS.rst (CFS) 861 - Documentation/admin-guide/cgroup-v1/ (features for grouping, isolation 862 and resource control) 863 864 Say N if unsure. 865 866if CGROUPS 867 868config PAGE_COUNTER 869 bool 870 871config CGROUP_FAVOR_DYNMODS 872 bool "Favor dynamic modification latency reduction by default" 873 help 874 This option enables the "favordynmods" mount option by default 875 which reduces the latencies of dynamic cgroup modifications such 876 as task migrations and controller on/offs at the cost of making 877 hot path operations such as forks and exits more expensive. 878 879 Say N if unsure. 880 881config MEMCG 882 bool "Memory controller" 883 select PAGE_COUNTER 884 select EVENTFD 885 select SLAB_OBJ_EXT 886 select VM_EVENT_COUNTERS 887 select BLK_CGROUP if BLOCK 888 help 889 Provides control over the memory footprint of tasks in a cgroup. 890 891config MEMCG_NMI_UNSAFE 892 bool 893 depends on MEMCG 894 depends on HAVE_NMI 895 depends on !ARCH_HAS_NMI_SAFE_THIS_CPU_OPS && !ARCH_HAVE_NMI_SAFE_CMPXCHG 896 default y 897 898config MEMCG_NMI_SAFETY_REQUIRES_ATOMIC 899 bool 900 depends on MEMCG 901 depends on HAVE_NMI 902 depends on !ARCH_HAS_NMI_SAFE_THIS_CPU_OPS && ARCH_HAVE_NMI_SAFE_CMPXCHG 903 default y 904 905config MEMCG_V1 906 bool "Legacy cgroup v1 memory controller" 907 depends on MEMCG 908 default n 909 help 910 Legacy cgroup v1 memory controller which has been deprecated by 911 cgroup v2 implementation. The v1 is there for legacy applications 912 which haven't migrated to the new cgroup v2 interface yet. If you 913 do not have any such application then you are completely fine leaving 914 this option disabled. 915 916 Please note that feature set of the legacy memory controller is likely 917 going to shrink due to deprecation process. New deployments with v1 918 controller are highly discouraged. 919 920 Say N if unsure. 921 922config BLK_CGROUP 923 bool "IO controller" 924 depends on BLOCK 925 default n 926 help 927 Generic block IO controller cgroup interface. This is the common 928 cgroup interface which should be used by various IO controlling 929 policies. 930 931 Currently, CFQ IO scheduler uses it to recognize task groups and 932 control disk bandwidth allocation (proportional time slice allocation) 933 to such task groups. It is also used by bio throttling logic in 934 block layer to implement upper limit in IO rates on a device. 935 936 This option only enables generic Block IO controller infrastructure. 937 One needs to also enable actual IO controlling logic/policy. For 938 enabling proportional weight division of disk bandwidth in CFQ, set 939 CONFIG_BFQ_GROUP_IOSCHED=y; for enabling throttling policy, set 940 CONFIG_BLK_DEV_THROTTLING=y. 941 942 See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information. 943 944config CGROUP_WRITEBACK 945 bool 946 depends on MEMCG && BLK_CGROUP 947 default y 948 949menuconfig CGROUP_SCHED 950 bool "CPU controller" 951 default n 952 help 953 This feature lets CPU scheduler recognize task groups and control CPU 954 bandwidth allocation to such task groups. It uses cgroups to group 955 tasks. 956 957if CGROUP_SCHED 958config GROUP_SCHED_WEIGHT 959 def_bool n 960 961config GROUP_SCHED_BANDWIDTH 962 def_bool n 963 964config FAIR_GROUP_SCHED 965 bool "Group scheduling for SCHED_OTHER" 966 depends on CGROUP_SCHED 967 select GROUP_SCHED_WEIGHT 968 default CGROUP_SCHED 969 970config CFS_BANDWIDTH 971 bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED" 972 depends on FAIR_GROUP_SCHED 973 select GROUP_SCHED_BANDWIDTH 974 default n 975 help 976 This option allows users to define CPU bandwidth rates (limits) for 977 tasks running within the fair group scheduler. Groups with no limit 978 set are considered to be unconstrained and will run with no 979 restriction. 980 See Documentation/scheduler/sched-bwc.rst for more information. 981 982config RT_GROUP_SCHED 983 bool "Group scheduling for SCHED_RR/FIFO" 984 depends on CGROUP_SCHED 985 default n 986 help 987 This feature lets you explicitly allocate real CPU bandwidth 988 to task groups. If enabled, it will also make it impossible to 989 schedule realtime tasks for non-root users until you allocate 990 realtime bandwidth for them. 991 See Documentation/scheduler/sched-rt-group.rst for more information. 992 993config RT_GROUP_SCHED_DEFAULT_DISABLED 994 bool "Require boot parameter to enable group scheduling for SCHED_RR/FIFO" 995 depends on RT_GROUP_SCHED 996 default n 997 help 998 When set, the RT group scheduling is disabled by default. The option 999 is in inverted form so that mere RT_GROUP_SCHED enables the group 1000 scheduling. 1001 1002 Say N if unsure. 1003 1004config EXT_GROUP_SCHED 1005 bool 1006 depends on SCHED_CLASS_EXT && CGROUP_SCHED 1007 select GROUP_SCHED_WEIGHT 1008 select GROUP_SCHED_BANDWIDTH 1009 default y 1010 1011endif #CGROUP_SCHED 1012 1013config EXT_SUB_SCHED 1014 def_bool y 1015 depends on SCHED_CLASS_EXT && CGROUPS 1016 1017config SCHED_MM_CID 1018 def_bool y 1019 depends on SMP && RSEQ 1020 1021config UCLAMP_TASK_GROUP 1022 bool "Utilization clamping per group of tasks" 1023 depends on CGROUP_SCHED 1024 depends on UCLAMP_TASK 1025 default n 1026 help 1027 This feature enables the scheduler to track the clamped utilization 1028 of each CPU based on RUNNABLE tasks currently scheduled on that CPU. 1029 1030 When this option is enabled, the user can specify a min and max 1031 CPU bandwidth which is allowed for each single task in a group. 1032 The max bandwidth allows to clamp the maximum frequency a task 1033 can use, while the min bandwidth allows to define a minimum 1034 frequency a task will always use. 1035 1036 When task group based utilization clamping is enabled, an eventually 1037 specified task-specific clamp value is constrained by the cgroup 1038 specified clamp value. Both minimum and maximum task clamping cannot 1039 be bigger than the corresponding clamping defined at task group level. 1040 1041 If in doubt, say N. 1042 1043config CGROUP_PIDS 1044 bool "PIDs controller" 1045 help 1046 Provides enforcement of process number limits in the scope of a 1047 cgroup. Any attempt to fork more processes than is allowed in the 1048 cgroup will fail. PIDs are fundamentally a global resource because it 1049 is fairly trivial to reach PID exhaustion before you reach even a 1050 conservative kmemcg limit. As a result, it is possible to grind a 1051 system to halt without being limited by other cgroup policies. The 1052 PIDs controller is designed to stop this from happening. 1053 1054 It should be noted that organisational operations (such as attaching 1055 to a cgroup hierarchy) will *not* be blocked by the PIDs controller, 1056 since the PIDs limit only affects a process's ability to fork, not to 1057 attach to a cgroup. 1058 1059config CGROUP_RDMA 1060 bool "RDMA controller" 1061 help 1062 Provides enforcement of RDMA resources defined by IB stack. 1063 It is fairly easy for consumers to exhaust RDMA resources, which 1064 can result into resource unavailability to other consumers. 1065 RDMA controller is designed to stop this from happening. 1066 Attaching processes with active RDMA resources to the cgroup 1067 hierarchy is allowed even if can cross the hierarchy's limit. 1068 1069config CGROUP_DMEM 1070 bool "Device memory controller (DMEM)" 1071 select PAGE_COUNTER 1072 help 1073 The DMEM controller allows compatible devices to restrict device 1074 memory usage based on the cgroup hierarchy. 1075 1076 As an example, it allows you to restrict VRAM usage for applications 1077 in the DRM subsystem. 1078 1079config CGROUP_FREEZER 1080 bool "Freezer controller" 1081 help 1082 Provides a way to freeze and unfreeze all tasks in a 1083 cgroup. 1084 1085 This option affects the ORIGINAL cgroup interface. The cgroup2 memory 1086 controller includes important in-kernel memory consumers per default. 1087 1088 If you're using cgroup2, say N. 1089 1090config CGROUP_HUGETLB 1091 bool "HugeTLB controller" 1092 depends on HUGETLB_PAGE 1093 select PAGE_COUNTER 1094 default n 1095 help 1096 Provides a cgroup controller for HugeTLB pages. 1097 When you enable this, you can put a per cgroup limit on HugeTLB usage. 1098 The limit is enforced during page fault. Since HugeTLB doesn't 1099 support page reclaim, enforcing the limit at page fault time implies 1100 that, the application will get SIGBUS signal if it tries to access 1101 HugeTLB pages beyond its limit. This requires the application to know 1102 beforehand how much HugeTLB pages it would require for its use. The 1103 control group is tracked in the third page lru pointer. This means 1104 that we cannot use the controller with huge page less than 3 pages. 1105 1106config CPUSETS 1107 bool "Cpuset controller" 1108 depends on SMP 1109 select UNION_FIND 1110 select CPU_ISOLATION 1111 help 1112 This option will let you create and manage CPUSETs which 1113 allow dynamically partitioning a system into sets of CPUs and 1114 Memory Nodes and assigning tasks to run only within those sets. 1115 This is primarily useful on large SMP or NUMA systems. 1116 1117 Say N if unsure. 1118 1119config CPUSETS_V1 1120 bool "Legacy cgroup v1 cpusets controller" 1121 depends on CPUSETS 1122 default n 1123 help 1124 Legacy cgroup v1 cpusets controller which has been deprecated by 1125 cgroup v2 implementation. The v1 is there for legacy applications 1126 which haven't migrated to the new cgroup v2 interface yet. Legacy 1127 interface includes cpuset filesystem and /proc/<pid>/cpuset. If you 1128 do not have any such application then you are completely fine leaving 1129 this option disabled. 1130 1131 Say N if unsure. 1132 1133config PROC_PID_CPUSET 1134 bool "Include legacy /proc/<pid>/cpuset file" 1135 depends on CPUSETS_V1 1136 default y 1137 1138config CGROUP_DEVICE 1139 bool "Device controller" 1140 help 1141 Provides a cgroup controller implementing whitelists for 1142 devices which a process in the cgroup can mknod or open. 1143 1144config CGROUP_CPUACCT 1145 bool "Simple CPU accounting controller" 1146 help 1147 Provides a simple controller for monitoring the 1148 total CPU consumed by the tasks in a cgroup. 1149 1150config CGROUP_PERF 1151 bool "Perf controller" 1152 depends on PERF_EVENTS 1153 help 1154 This option extends the perf per-cpu mode to restrict monitoring 1155 to threads which belong to the cgroup specified and run on the 1156 designated cpu. Or this can be used to have cgroup ID in samples 1157 so that it can monitor performance events among cgroups. 1158 1159 Say N if unsure. 1160 1161config CGROUP_BPF 1162 bool "Support for eBPF programs attached to cgroups" 1163 depends on BPF_SYSCALL 1164 select SOCK_CGROUP_DATA 1165 help 1166 Allow attaching eBPF programs to a cgroup using the bpf(2) 1167 syscall command BPF_PROG_ATTACH. 1168 1169 In which context these programs are accessed depends on the type 1170 of attachment. For instance, programs that are attached using 1171 BPF_CGROUP_INET_INGRESS will be executed on the ingress path of 1172 inet sockets. 1173 1174config CGROUP_MISC 1175 bool "Misc resource controller" 1176 default n 1177 help 1178 Provides a controller for miscellaneous resources on a host. 1179 1180 Miscellaneous scalar resources are the resources on the host system 1181 which cannot be abstracted like the other cgroups. This controller 1182 tracks and limits the miscellaneous resources used by a process 1183 attached to a cgroup hierarchy. 1184 1185 For more information, please check misc cgroup section in 1186 /Documentation/admin-guide/cgroup-v2.rst. 1187 1188config CGROUP_DEBUG 1189 bool "Debug controller" 1190 default n 1191 depends on DEBUG_KERNEL 1192 help 1193 This option enables a simple controller that exports 1194 debugging information about the cgroups framework. This 1195 controller is for control cgroup debugging only. Its 1196 interfaces are not stable. 1197 1198 Say N. 1199 1200config SOCK_CGROUP_DATA 1201 bool 1202 default n 1203 1204endif # CGROUPS 1205 1206menuconfig NAMESPACES 1207 bool "Namespaces support" if EXPERT 1208 depends on MULTIUSER 1209 default !EXPERT 1210 help 1211 Provides the way to make tasks work with different objects using 1212 the same id. For example same IPC id may refer to different objects 1213 or same user id or pid may refer to different tasks when used in 1214 different namespaces. 1215 1216if NAMESPACES 1217 1218config UTS_NS 1219 bool "UTS namespace" 1220 default y 1221 help 1222 In this namespace tasks see different info provided with the 1223 uname() system call 1224 1225config TIME_NS 1226 bool "TIME namespace" 1227 default y 1228 help 1229 In this namespace boottime and monotonic clocks can be set. 1230 The time will keep going with the same pace. 1231 1232config TIME_NS_VDSO 1233 def_bool TIME_NS && GENERIC_GETTIMEOFDAY 1234 1235config IPC_NS 1236 bool "IPC namespace" 1237 depends on (SYSVIPC || POSIX_MQUEUE) 1238 default y 1239 help 1240 In this namespace tasks work with IPC ids which correspond to 1241 different IPC objects in different namespaces. 1242 1243config USER_NS 1244 bool "User namespace" 1245 default n 1246 help 1247 This allows containers, i.e. vservers, to use user namespaces 1248 to provide different user info for different servers. 1249 1250 When user namespaces are enabled in the kernel it is 1251 recommended that the MEMCG option also be enabled and that 1252 user-space use the memory control groups to limit the amount 1253 of memory a memory unprivileged users can use. 1254 1255 If unsure, say N. 1256 1257config USER_NS_MAP_KUNIT_TEST 1258 tristate "KUint test for user namespace map insertion" if !KUNIT_ALL_TESTS 1259 depends on USER_NS && KUNIT 1260 default KUNIT_ALL_TESTS 1261 help 1262 This builds the KUnit test for user namespace uid/gid map insertion. 1263 It validates map insertion, limits, dynamic allocation of the 1264 extended extents array, and mapping sorting functions. 1265 1266 If unsure, say N. 1267 1268config PID_NS 1269 bool "PID Namespaces" 1270 default y 1271 help 1272 Support process id namespaces. This allows having multiple 1273 processes with the same pid as long as they are in different 1274 pid namespaces. This is a building block of containers. 1275 1276config NET_NS 1277 bool "Network namespace" 1278 depends on NET 1279 default y 1280 help 1281 Allow user space to create what appear to be multiple instances 1282 of the network stack. 1283 1284endif # NAMESPACES 1285 1286config CHECKPOINT_RESTORE 1287 bool "Checkpoint/restore support" 1288 depends on PROC_FS 1289 select PROC_CHILDREN 1290 select KCMP 1291 default n 1292 help 1293 Enables additional kernel features in a sake of checkpoint/restore. 1294 In particular it adds auxiliary prctl codes to setup process text, 1295 data and heap segment sizes, and a few additional /proc filesystem 1296 entries. 1297 1298 If unsure, say N here. 1299 1300config SCHED_AUTOGROUP 1301 bool "Automatic process group scheduling" 1302 select CGROUPS 1303 select CGROUP_SCHED 1304 select FAIR_GROUP_SCHED 1305 help 1306 This option optimizes the scheduler for common desktop workloads by 1307 automatically creating and populating task groups. This separation 1308 of workloads isolates aggressive CPU burners (like build jobs) from 1309 desktop applications. Task group autogeneration is currently based 1310 upon task session. 1311 1312config RELAY 1313 bool "Kernel->user space relay support (formerly relayfs)" 1314 select IRQ_WORK 1315 help 1316 This option enables support for relay interface support in 1317 certain file systems (such as debugfs). 1318 It is designed to provide an efficient mechanism for tools and 1319 facilities to relay large amounts of data from kernel space to 1320 user space. 1321 1322 If unsure, say N. 1323 1324config BLK_DEV_INITRD 1325 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support" 1326 help 1327 The initial RAM filesystem is a ramfs which is loaded by the 1328 boot loader (loadlin or lilo) and that is mounted as root 1329 before the normal boot procedure. It is typically used to 1330 load modules needed to mount the "real" root file system, 1331 etc. See <file:Documentation/admin-guide/initrd.rst> for details. 1332 1333 If RAM disk support (BLK_DEV_RAM) is also included, this 1334 also enables initial RAM disk (initrd) support and adds 1335 15 Kbytes (more on some other architectures) to the kernel size. 1336 1337 If unsure say Y. 1338 1339if BLK_DEV_INITRD 1340 1341source "usr/Kconfig" 1342 1343endif 1344 1345config BOOT_CONFIG 1346 bool "Boot config support" 1347 select BLK_DEV_INITRD if !BOOT_CONFIG_EMBED 1348 help 1349 Extra boot config allows system admin to pass a config file as 1350 complemental extension of kernel cmdline when booting. 1351 The boot config file must be attached at the end of initramfs 1352 with checksum, size and magic word. 1353 See <file:Documentation/admin-guide/bootconfig.rst> for details. 1354 1355 If unsure, say Y. 1356 1357config BOOT_CONFIG_FORCE 1358 bool "Force unconditional bootconfig processing" 1359 depends on BOOT_CONFIG 1360 default y if BOOT_CONFIG_EMBED 1361 help 1362 With this Kconfig option set, BOOT_CONFIG processing is carried 1363 out even when the "bootconfig" kernel-boot parameter is omitted. 1364 In fact, with this Kconfig option set, there is no way to 1365 make the kernel ignore the BOOT_CONFIG-supplied kernel-boot 1366 parameters. 1367 1368 If unsure, say N. 1369 1370config BOOT_CONFIG_EMBED 1371 bool "Embed bootconfig file in the kernel" 1372 depends on BOOT_CONFIG 1373 help 1374 Embed a bootconfig file given by BOOT_CONFIG_EMBED_FILE in the 1375 kernel. Usually, the bootconfig file is loaded with the initrd 1376 image. But if the system doesn't support initrd, this option will 1377 help you by embedding a bootconfig file while building the kernel. 1378 1379 If unsure, say N. 1380 1381config BOOT_CONFIG_EMBED_FILE 1382 string "Embedded bootconfig file path" 1383 depends on BOOT_CONFIG_EMBED 1384 help 1385 Specify a bootconfig file which will be embedded to the kernel. 1386 This bootconfig will be used if there is no initrd or no other 1387 bootconfig in the initrd. 1388 1389config ARCH_SUPPORTS_CMDLINE_FROM_BOOTCONFIG 1390 bool 1391 help 1392 Silent symbol; no C code reads it directly. Architectures 1393 select it once their setup_arch() calls 1394 xbc_prepend_embedded_cmdline() before parse_early_param(). 1395 Its only role is to gate the user-visible 1396 CMDLINE_FROM_BOOTCONFIG option per-arch, the same 1397 ARCH_SUPPORTS_* idiom used by ARCH_SUPPORTS_CFI, etc. 1398 1399config CMDLINE_FROM_BOOTCONFIG 1400 bool "Render embedded bootconfig as kernel cmdline at build time" 1401 depends on BOOT_CONFIG_EMBED_FILE != "" 1402 depends on ARCH_SUPPORTS_CMDLINE_FROM_BOOTCONFIG 1403 depends on CMDLINE = "" 1404 default n 1405 help 1406 Render the "kernel" subtree of the embedded bootconfig file into a 1407 flat cmdline string at kernel build time and prepend it to 1408 boot_command_line during early architecture setup. This makes 1409 early_param() handlers (e.g. mem=, earlycon=, loglevel=) see the 1410 values supplied via the embedded bootconfig. 1411 1412 The runtime bootconfig parser is unaffected, so tree-structured 1413 consumers such as ftrace boot-time tracing keep working. 1414 1415 Note: when an initrd also carries a bootconfig, its "kernel" 1416 subtree is still parsed at runtime, but the embedded "kernel" 1417 keys remain in boot_command_line for parse_early_param() and 1418 end up later than the initrd keys in saved_command_line, so 1419 parse_args() last-wins favors the embedded values. If you need 1420 initrd to override embedded kernel.* keys, leave this option 1421 off. 1422 1423 If unsure, say N. 1424 1425config CMDLINE_LOG_WRAP_IDEAL_LEN 1426 int "Length to try to wrap the cmdline when logged at boot" 1427 default 1021 1428 range 0 1021 1429 help 1430 At boot time, the kernel command line is logged to the console. 1431 The log message will start with the prefix "Kernel command line: ". 1432 The log message will attempt to be wrapped (split into multiple log 1433 messages) at spaces based on CMDLINE_LOG_WRAP_IDEAL_LEN characters. 1434 If wrapping happens, each log message will start with the prefix and 1435 all but the last message will end with " \". Messages may exceed the 1436 ideal length if a place to wrap isn't found before the specified 1437 number of characters. 1438 1439 A value of 0 disables wrapping, though be warned that the maximum 1440 length of a log message (1021 characters) may cause the cmdline to 1441 be truncated. 1442 1443config INITRAMFS_PRESERVE_MTIME 1444 bool "Preserve cpio archive mtimes in initramfs" 1445 depends on BLK_DEV_INITRD 1446 default y 1447 help 1448 Each entry in an initramfs cpio archive carries an mtime value. When 1449 enabled, extracted cpio items take this mtime, with directory mtime 1450 setting deferred until after creation of any child entries. 1451 1452 If unsure, say Y. 1453 1454config INITRAMFS_TEST 1455 bool "Test initramfs cpio archive extraction" if !KUNIT_ALL_TESTS 1456 depends on BLK_DEV_INITRD && KUNIT=y 1457 default KUNIT_ALL_TESTS 1458 help 1459 Build KUnit tests for initramfs. See Documentation/dev-tools/kunit 1460 1461choice 1462 prompt "Compiler optimization level" 1463 default CC_OPTIMIZE_FOR_PERFORMANCE 1464 1465config CC_OPTIMIZE_FOR_PERFORMANCE 1466 bool "Optimize for performance (-O2)" 1467 help 1468 This is the default optimization level for the kernel, building 1469 with the "-O2" compiler flag for best performance and most 1470 helpful compile-time warnings. 1471 1472config CC_OPTIMIZE_FOR_SIZE 1473 bool "Optimize for size (-Os)" 1474 help 1475 Choosing this option will pass "-Os" to your compiler resulting 1476 in a smaller kernel. 1477 1478endchoice 1479 1480config HAVE_LD_DEAD_CODE_DATA_ELIMINATION 1481 bool 1482 help 1483 This requires that the arch annotates or otherwise protects 1484 its external entry points from being discarded. Linker scripts 1485 must also merge .text.*, .data.*, and .bss.* correctly into 1486 output sections. Care must be taken not to pull in unrelated 1487 sections (e.g., '.text.init'). Typically '.' in section names 1488 is used to distinguish them from label names / C identifiers. 1489 1490config LD_DEAD_CODE_DATA_ELIMINATION 1491 bool "Dead code and data elimination (EXPERIMENTAL)" 1492 depends on HAVE_LD_DEAD_CODE_DATA_ELIMINATION 1493 depends on EXPERT 1494 depends on $(cc-option,-ffunction-sections -fdata-sections) 1495 depends on $(ld-option,--gc-sections) 1496 help 1497 Enable this if you want to do dead code and data elimination with 1498 the linker by compiling with -ffunction-sections -fdata-sections, 1499 and linking with --gc-sections. 1500 1501 This can reduce on disk and in-memory size of the kernel 1502 code and static data, particularly for small configs and 1503 on small systems. This has the possibility of introducing 1504 silently broken kernel if the required annotations are not 1505 present. This option is not well tested yet, so use at your 1506 own risk. 1507 1508config LD_ORPHAN_WARN 1509 def_bool y 1510 depends on ARCH_WANT_LD_ORPHAN_WARN 1511 depends on $(ld-option,--orphan-handling=warn) 1512 depends on $(ld-option,--orphan-handling=error) 1513 1514config LD_ORPHAN_WARN_LEVEL 1515 string 1516 depends on LD_ORPHAN_WARN 1517 default "error" if WERROR 1518 default "warn" 1519 1520config HAVE_UID16 1521 bool 1522 1523config SYSCTL_EXCEPTION_TRACE 1524 bool 1525 help 1526 Enable support for /proc/sys/debug/exception-trace. 1527 1528config SYSCTL_ARCH_UNALIGN_NO_WARN 1529 bool 1530 help 1531 Enable support for /proc/sys/kernel/ignore-unaligned-usertrap 1532 Allows arch to define/use @no_unaligned_warning to possibly warn 1533 about unaligned access emulation going on under the hood. 1534 1535config SYSCTL_ARCH_UNALIGN_ALLOW 1536 bool 1537 help 1538 Enable support for /proc/sys/kernel/unaligned-trap 1539 Allows arches to define/use @unaligned_enabled to runtime toggle 1540 the unaligned access emulation. 1541 see arch/parisc/kernel/unaligned.c for reference 1542 1543config SYSFS_SYSCALL 1544 bool "Sysfs syscall support" 1545 default n 1546 help 1547 sys_sysfs is an obsolete system call no longer supported in libc. 1548 Note that disabling this option is more secure but might break 1549 compatibility with some systems. 1550 1551 If unsure say N here. 1552 1553config HAVE_PCSPKR_PLATFORM 1554 bool 1555 1556menuconfig EXPERT 1557 bool "Configure standard kernel features (expert users)" 1558 # Unhide debug options, to make the on-by-default options visible 1559 select DEBUG_KERNEL 1560 help 1561 This option allows certain base kernel options and settings 1562 to be disabled or tweaked. This is for specialized 1563 environments which can tolerate a "non-standard" kernel. 1564 Only use this if you really know what you are doing. 1565 1566config UID16 1567 bool "Enable 16-bit UID system calls" if EXPERT 1568 depends on HAVE_UID16 && MULTIUSER 1569 default y 1570 help 1571 This enables the legacy 16-bit UID syscall wrappers. 1572 1573config MULTIUSER 1574 bool "Multiple users, groups and capabilities support" if EXPERT 1575 default y 1576 help 1577 This option enables support for non-root users, groups and 1578 capabilities. 1579 1580 If you say N here, all processes will run with UID 0, GID 0, and all 1581 possible capabilities. Saying N here also compiles out support for 1582 system calls related to UIDs, GIDs, and capabilities, such as setuid, 1583 setgid, and capset. 1584 1585 If unsure, say Y here. 1586 1587config SGETMASK_SYSCALL 1588 bool "sgetmask/ssetmask syscalls support" if EXPERT 1589 default PARISC || M68K || PPC || MIPS || X86 || SPARC || MICROBLAZE || SUPERH 1590 help 1591 sys_sgetmask and sys_ssetmask are obsolete system calls 1592 no longer supported in libc but still enabled by default in some 1593 architectures. 1594 1595 If unsure, leave the default option here. 1596 1597config FHANDLE 1598 bool "open by fhandle syscalls" if EXPERT 1599 select EXPORTFS 1600 default y 1601 help 1602 If you say Y here, a user level program will be able to map 1603 file names to handle and then later use the handle for 1604 different file system operations. This is useful in implementing 1605 userspace file servers, which now track files using handles instead 1606 of names. The handle would remain the same even if file names 1607 get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2) 1608 syscalls. 1609 1610config POSIX_TIMERS 1611 bool "Posix Clocks & timers" if EXPERT 1612 default y 1613 help 1614 This includes native support for POSIX timers to the kernel. 1615 Some embedded systems have no use for them and therefore they 1616 can be configured out to reduce the size of the kernel image. 1617 1618 When this option is disabled, the following syscalls won't be 1619 available: timer_create, timer_gettime: timer_getoverrun, 1620 timer_settime, timer_delete, clock_adjtime, getitimer, 1621 setitimer, alarm. Furthermore, the clock_settime, clock_gettime, 1622 clock_getres and clock_nanosleep syscalls will be limited to 1623 CLOCK_REALTIME, CLOCK_MONOTONIC and CLOCK_BOOTTIME only. 1624 1625 If unsure say y. 1626 1627config PRINTK 1628 default y 1629 bool "Enable support for printk" if EXPERT 1630 select IRQ_WORK 1631 help 1632 This option enables normal printk support. Removing it 1633 eliminates most of the message strings from the kernel image 1634 and makes the kernel more or less silent. As this makes it 1635 very difficult to diagnose system problems, saying N here is 1636 strongly discouraged. 1637 1638config PRINTK_RINGBUFFER_KUNIT_TEST 1639 tristate "KUnit Test for the printk ringbuffer" if !KUNIT_ALL_TESTS 1640 depends on PRINTK && KUNIT 1641 default KUNIT_ALL_TESTS 1642 help 1643 This builds the printk ringbuffer KUnit test suite. 1644 1645 For more information on KUnit and unit tests in general, please refer 1646 to the KUnit documentation. 1647 1648 If unsure, say N. 1649 1650config BUG 1651 bool "BUG() support" if EXPERT 1652 default y 1653 help 1654 Disabling this option eliminates support for BUG and WARN, reducing 1655 the size of your kernel image and potentially quietly ignoring 1656 numerous fatal conditions. You should only consider disabling this 1657 option for embedded systems with no facilities for reporting errors. 1658 Just say Y. 1659 1660config ELF_CORE 1661 depends on COREDUMP 1662 default y 1663 bool "Enable ELF core dumps" if EXPERT 1664 help 1665 Enable support for generating core dumps. Disabling saves about 4k. 1666 1667 1668config PCSPKR_PLATFORM 1669 bool "Enable PC-Speaker support" if EXPERT 1670 depends on HAVE_PCSPKR_PLATFORM 1671 select I8253_LOCK 1672 default y 1673 help 1674 This option allows to disable the internal PC-Speaker 1675 support, saving some memory. 1676 1677config BASE_SMALL 1678 bool "Enable smaller-sized data structures for core" if EXPERT 1679 help 1680 Enabling this option reduces the size of miscellaneous core 1681 kernel data structures. This saves memory on small machines, 1682 but may reduce performance. 1683 1684config FUTEX 1685 bool "Enable futex support" if EXPERT 1686 depends on !(SPARC32 && SMP) 1687 default y 1688 imply RT_MUTEXES 1689 help 1690 Disabling this option will cause the kernel to be built without 1691 support for "fast userspace mutexes". The resulting kernel may not 1692 run glibc-based applications correctly. 1693 1694config FUTEX_PI 1695 bool 1696 depends on FUTEX && RT_MUTEXES 1697 default y 1698 1699config FUTEX_PRIVATE_HASH 1700 bool 1701 depends on FUTEX && !BASE_SMALL && MMU 1702 default y 1703 1704config FUTEX_MPOL 1705 bool 1706 depends on FUTEX && NUMA 1707 default y 1708 1709config HAVE_FUTEX_ROBUST_UNLOCK 1710 bool 1711 1712config FUTEX_ROBUST_UNLOCK 1713 def_bool FUTEX && GENERIC_IRQ_ENTRY && RSEQ && HAVE_FUTEX_ROBUST_UNLOCK 1714 1715config EPOLL 1716 bool "Enable eventpoll support" if EXPERT 1717 default y 1718 help 1719 Disabling this option will cause the kernel to be built without 1720 support for epoll family of system calls. 1721 1722config SIGNALFD 1723 bool "Enable signalfd() system call" if EXPERT 1724 default y 1725 help 1726 Enable the signalfd() system call that allows to receive signals 1727 on a file descriptor. 1728 1729 If unsure, say Y. 1730 1731config TIMERFD 1732 bool "Enable timerfd() system call" if EXPERT 1733 default y 1734 help 1735 Enable the timerfd() system call that allows to receive timer 1736 events on a file descriptor. 1737 1738 If unsure, say Y. 1739 1740config EVENTFD 1741 bool "Enable eventfd() system call" if EXPERT 1742 default y 1743 help 1744 Enable the eventfd() system call that allows to receive both 1745 kernel notification (ie. KAIO) or userspace notifications. 1746 1747 If unsure, say Y. 1748 1749config SHMEM 1750 bool "Use full shmem filesystem" if EXPERT 1751 default y 1752 depends on MMU 1753 help 1754 The shmem is an internal filesystem used to manage shared memory. 1755 It is backed by swap and manages resource limits. It is also exported 1756 to userspace as tmpfs if TMPFS is enabled. Disabling this 1757 option replaces shmem and tmpfs with the much simpler ramfs code, 1758 which may be appropriate on small systems without swap. 1759 1760config AIO 1761 bool "Enable AIO support" if EXPERT 1762 default y 1763 help 1764 This option enables POSIX asynchronous I/O which may by used 1765 by some high performance threaded applications. Disabling 1766 this option saves about 7k. 1767 1768config IO_URING 1769 bool "Enable IO uring support" if EXPERT 1770 select IO_WQ 1771 default y 1772 help 1773 This option enables support for the io_uring interface, enabling 1774 applications to submit and complete IO through submission and 1775 completion rings that are shared between the kernel and application. 1776 1777config GCOV_PROFILE_URING 1778 bool "Enable GCOV profiling on the io_uring subsystem" 1779 depends on IO_URING && GCOV_KERNEL 1780 help 1781 Enable GCOV profiling on the io_uring subsystem, to facilitate 1782 code coverage testing. 1783 1784 If unsure, say N. 1785 1786 Note that this will have a negative impact on the performance of 1787 the io_uring subsystem, hence this should only be enabled for 1788 specific test purposes. 1789 1790config IO_URING_MOCK_FILE 1791 tristate "Enable io_uring mock files (Experimental)" if EXPERT 1792 default n 1793 depends on IO_URING 1794 help 1795 Enable mock files for io_uring subsystem testing. The ABI might 1796 still change, so it's still experimental and should only be enabled 1797 for specific test purposes. 1798 1799 If unsure, say N. 1800 1801config ADVISE_SYSCALLS 1802 bool "Enable madvise/fadvise syscalls" if EXPERT 1803 default y 1804 help 1805 This option enables the madvise and fadvise syscalls, used by 1806 applications to advise the kernel about their future memory or file 1807 usage, improving performance. If building an embedded system where no 1808 applications use these syscalls, you can disable this option to save 1809 space. 1810 1811config MEMBARRIER 1812 bool "Enable membarrier() system call" if EXPERT 1813 default y 1814 help 1815 Enable the membarrier() system call that allows issuing memory 1816 barriers across all running threads, which can be used to distribute 1817 the cost of user-space memory barriers asymmetrically by transforming 1818 pairs of memory barriers into pairs consisting of membarrier() and a 1819 compiler barrier. 1820 1821 If unsure, say Y. 1822 1823config KCMP 1824 bool "Enable kcmp() system call" if EXPERT 1825 help 1826 Enable the kernel resource comparison system call. It provides 1827 user-space with the ability to compare two processes to see if they 1828 share a common resource, such as a file descriptor or even virtual 1829 memory space. 1830 1831 If unsure, say N. 1832 1833config RSEQ 1834 bool "Enable rseq() system call" if EXPERT 1835 default y 1836 depends on HAVE_RSEQ 1837 select MEMBARRIER 1838 help 1839 Enable the restartable sequences system call. It provides a 1840 user-space cache for the current CPU number value, which 1841 speeds up getting the current CPU number from user-space, 1842 as well as an ABI to speed up user-space operations on 1843 per-CPU data. 1844 1845 If unsure, say Y. 1846 1847config RSEQ_SLICE_EXTENSION 1848 bool "Enable rseq-based time slice extension mechanism" 1849 depends on RSEQ && HIGH_RES_TIMERS && GENERIC_ENTRY && HAVE_GENERIC_TIF_BITS 1850 help 1851 Allows userspace to request a limited time slice extension when 1852 returning from an interrupt to user space via the RSEQ shared 1853 data ABI. If granted, that allows to complete a critical section, 1854 so that other threads are not stuck on a conflicted resource, 1855 while the task is scheduled out. 1856 1857 If unsure, say N. 1858 1859config RSEQ_STATS 1860 default n 1861 bool "Enable lightweight statistics of restartable sequences" if EXPERT 1862 depends on RSEQ && DEBUG_FS 1863 help 1864 Enable lightweight counters which expose information about the 1865 frequency of RSEQ operations via debugfs. Mostly interesting for 1866 kernel debugging or performance analysis. While lightweight it's 1867 still adding code into the user/kernel mode transitions. 1868 1869 If unsure, say N. 1870 1871config RSEQ_DEBUG_DEFAULT_ENABLE 1872 default n 1873 bool "Enable restartable sequences debug mode by default" if EXPERT 1874 depends on RSEQ 1875 help 1876 This enables the static branch for debug mode of restartable 1877 sequences. 1878 1879 This also can be controlled on the kernel command line via the 1880 command line parameter "rseq_debug=0/1" and through debugfs. 1881 1882 If unsure, say N. 1883 1884config DEBUG_RSEQ 1885 default n 1886 bool "Enable debugging of rseq() system call" if EXPERT 1887 depends on RSEQ && DEBUG_KERNEL && !GENERIC_ENTRY 1888 select RSEQ_DEBUG_DEFAULT_ENABLE 1889 help 1890 Enable extra debugging checks for the rseq system call. 1891 1892 If unsure, say N. 1893 1894config CACHESTAT_SYSCALL 1895 bool "Enable cachestat() system call" if EXPERT 1896 default y 1897 help 1898 Enable the cachestat system call, which queries the page cache 1899 statistics of a file (number of cached pages, dirty pages, 1900 pages marked for writeback, (recently) evicted pages). 1901 1902 If unsure say Y here. 1903 1904config KALLSYMS 1905 bool "Load all symbols for debugging/ksymoops" if EXPERT 1906 default y 1907 help 1908 Say Y here to let the kernel print out symbolic crash information and 1909 symbolic stack backtraces. This increases the size of the kernel 1910 somewhat, as all symbols have to be loaded into the kernel image. 1911 1912config KALLSYMS_SELFTEST 1913 bool "Test the basic functions and performance of kallsyms" 1914 depends on KALLSYMS 1915 default n 1916 help 1917 Test the basic functions and performance of some interfaces, such as 1918 kallsyms_lookup_name. It also calculates the compression rate of the 1919 kallsyms compression algorithm for the current symbol set. 1920 1921 Start self-test automatically after system startup. Suggest executing 1922 "dmesg | grep kallsyms_selftest" to collect test results. "finish" is 1923 displayed in the last line, indicating that the test is complete. 1924 1925config KALLSYMS_ALL 1926 bool "Include all symbols in kallsyms" 1927 depends on DEBUG_KERNEL && KALLSYMS 1928 help 1929 Normally kallsyms only contains the symbols of functions for nicer 1930 OOPS messages and backtraces (i.e., symbols from the text and inittext 1931 sections). This is sufficient for most cases. And only if you want to 1932 enable kernel live patching, or other less common use cases (e.g., 1933 when a debugger is used) all symbols are required (i.e., names of 1934 variables from the data sections, etc). 1935 1936 This option makes sure that all symbols are loaded into the kernel 1937 image (i.e., symbols from all sections) in cost of increased kernel 1938 size (depending on the kernel configuration, it may be 300KiB or 1939 something like this). 1940 1941 Say N unless you really need all symbols, or kernel live patching. 1942 1943# end of the "standard kernel features (expert users)" menu 1944 1945config ARCH_HAS_MEMBARRIER_CALLBACKS 1946 bool 1947 1948config ARCH_HAS_MEMBARRIER_SYNC_CORE 1949 bool 1950 1951config ARCH_SUPPORTS_MSEAL_SYSTEM_MAPPINGS 1952 bool 1953 help 1954 Control MSEAL_SYSTEM_MAPPINGS access based on architecture. 1955 1956 A 64-bit kernel is required for the memory sealing feature. 1957 No specific hardware features from the CPU are needed. 1958 1959 To enable this feature, the architecture needs to update their 1960 special mappings calls to include the sealing flag and confirm 1961 that it doesn't unmap/remap system mappings during the life 1962 time of the process. The existence of this flag for an architecture 1963 implies that it does not require the remapping of the system 1964 mappings during process lifetime, so sealing these mappings is safe 1965 from a kernel perspective. 1966 1967 After the architecture enables this, a distribution can set 1968 CONFIG_MSEAL_SYSTEM_MAPPINGS to manage access to the feature. 1969 1970 For complete descriptions of memory sealing, please see 1971 Documentation/userspace-api/mseal.rst 1972 1973config HAVE_PERF_EVENTS 1974 bool 1975 help 1976 See tools/perf/design.txt for details. 1977 1978config GUEST_PERF_EVENTS 1979 bool 1980 depends on HAVE_PERF_EVENTS 1981 1982config PERF_GUEST_MEDIATED_PMU 1983 bool 1984 depends on GUEST_PERF_EVENTS 1985 1986config PERF_USE_VMALLOC 1987 bool 1988 help 1989 See tools/perf/design.txt for details 1990 1991menu "Kernel Performance Events And Counters" 1992 1993config PERF_EVENTS 1994 bool "Kernel performance events and counters" 1995 default y if PROFILING 1996 depends on HAVE_PERF_EVENTS 1997 select IRQ_WORK 1998 help 1999 Enable kernel support for various performance events provided 2000 by software and hardware. 2001 2002 Software events are supported either built-in or via the 2003 use of generic tracepoints. 2004 2005 Most modern CPUs support performance events via performance 2006 counter registers. These registers count the number of certain 2007 types of hw events: such as instructions executed, cachemisses 2008 suffered, or branches mis-predicted - without slowing down the 2009 kernel or applications. These registers can also trigger interrupts 2010 when a threshold number of events have passed - and can thus be 2011 used to profile the code that runs on that CPU. 2012 2013 The Linux Performance Event subsystem provides an abstraction of 2014 these software and hardware event capabilities, available via a 2015 system call and used by the "perf" utility in tools/perf/. It 2016 provides per task and per CPU counters, and it provides event 2017 capabilities on top of those. 2018 2019 Say Y if unsure. 2020 2021config DEBUG_PERF_USE_VMALLOC 2022 default n 2023 bool "Debug: use vmalloc to back perf mmap() buffers" 2024 depends on PERF_EVENTS && DEBUG_KERNEL && !PPC 2025 select PERF_USE_VMALLOC 2026 help 2027 Use vmalloc memory to back perf mmap() buffers. 2028 2029 Mostly useful for debugging the vmalloc code on platforms 2030 that don't require it. 2031 2032 Say N if unsure. 2033 2034endmenu 2035 2036config SYSTEM_DATA_VERIFICATION 2037 def_bool n 2038 select SYSTEM_TRUSTED_KEYRING 2039 select KEYS 2040 select CRYPTO 2041 select CRYPTO_RSA 2042 select ASYMMETRIC_KEY_TYPE 2043 select ASYMMETRIC_PUBLIC_KEY_SUBTYPE 2044 select ASN1 2045 select OID_REGISTRY 2046 select X509_CERTIFICATE_PARSER 2047 select PKCS7_MESSAGE_PARSER 2048 help 2049 Provide PKCS#7 message verification using the contents of the system 2050 trusted keyring to provide public keys. This then can be used for 2051 module verification, kexec image verification and firmware blob 2052 verification. 2053 2054config PROFILING 2055 bool "Profiling support" 2056 help 2057 Say Y here to enable the extended profiling support mechanisms used 2058 by profilers. 2059 2060config RUST 2061 bool "Rust support" 2062 depends on HAVE_RUST 2063 depends on RUST_IS_AVAILABLE 2064 select EXTENDED_MODVERSIONS if MODVERSIONS 2065 depends on !MODVERSIONS || GENDWARFKSYMS 2066 depends on !GCC_PLUGIN_RANDSTRUCT 2067 depends on !RANDSTRUCT 2068 depends on !DEBUG_INFO_BTF || (PAHOLE_HAS_LANG_EXCLUDE && !LTO) 2069 depends on !CFI || HAVE_CFI_ICALL_NORMALIZE_INTEGERS_RUSTC 2070 select CFI_ICALL_NORMALIZE_INTEGERS if CFI 2071 depends on !KASAN || CC_IS_CLANG 2072 depends on !KASAN_SW_TAGS || RUSTC_VERSION >= 109600 2073 help 2074 Enables Rust support in the kernel. 2075 2076 This allows other Rust-related options, like drivers written in Rust, 2077 to be selected. 2078 2079 It is also required to be able to load external kernel modules 2080 written in Rust. 2081 2082 See Documentation/rust/ for more information. 2083 2084 If unsure, say N. 2085 2086source "rust/kernel/Kconfig.test" 2087 2088config RUSTC_VERSION_TEXT 2089 string 2090 depends on RUST 2091 default "$(RUSTC_VERSION_TEXT)" 2092 help 2093 See `CC_VERSION_TEXT`. 2094 2095config BINDGEN_VERSION_TEXT 2096 string 2097 depends on RUST 2098 default "$(shell,$(BINDGEN) --version 2>/dev/null)" 2099 2100# 2101# Place an empty function call at each tracepoint site. Can be 2102# dynamically changed for a probe function. 2103# 2104config TRACEPOINTS 2105 bool 2106 select TASKS_TRACE_RCU 2107 2108source "kernel/Kconfig.kexec" 2109 2110source "kernel/liveupdate/Kconfig" 2111 2112endmenu # General setup 2113 2114source "arch/Kconfig" 2115 2116config RT_MUTEXES 2117 bool 2118 default y if PREEMPT_RT 2119 2120config MODULE_SIG_FORMAT 2121 def_bool n 2122 select SYSTEM_DATA_VERIFICATION 2123 2124source "kernel/module/Kconfig" 2125 2126config INIT_ALL_POSSIBLE 2127 bool 2128 help 2129 Back when each arch used to define their own cpu_online_mask and 2130 cpu_possible_mask, some of them chose to initialize cpu_possible_mask 2131 with all 1s, and others with all 0s. When they were centralised, 2132 it was better to provide this option than to break all the archs 2133 and have several arch maintainers pursuing me down dark alleys. 2134 2135source "block/Kconfig" 2136 2137config PREEMPT_NOTIFIERS 2138 bool 2139 2140config PADATA 2141 depends on SMP 2142 bool 2143 2144config ASN1 2145 tristate 2146 help 2147 Build a simple ASN.1 grammar compiler that produces a bytecode output 2148 that can be interpreted by the ASN.1 stream decoder and used to 2149 inform it as to what tags are to be expected in a stream and what 2150 functions to call on what tags. 2151 2152source "kernel/Kconfig.locks" 2153 2154config ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE 2155 bool 2156 2157config ARCH_HAS_PREPARE_SYNC_CORE_CMD 2158 bool 2159 2160config ARCH_HAS_SYNC_CORE_BEFORE_USERMODE 2161 bool 2162 2163# It may be useful for an architecture to override the definitions of the 2164# SYSCALL_DEFINE() and __SYSCALL_DEFINEx() macros in <linux/syscalls.h> 2165# and the COMPAT_ variants in <linux/compat.h>, in particular to use a 2166# different calling convention for syscalls. They can also override the 2167# macros for not-implemented syscalls in kernel/sys_ni.c and 2168# kernel/time/posix-stubs.c. All these overrides need to be available in 2169# <asm/syscall_wrapper.h>. 2170config ARCH_HAS_SYSCALL_WRAPPER 2171 def_bool n 2172