1 # SPDX-License-Identifier: GPL-2.0-only
4 default "$(CC_VERSION_TEXT)"
6 This is used in unclear ways:
8 - Re-run Kconfig when the compiler is updated
9 The 'default' property references the environment variable,
10 CC_VERSION_TEXT so it is recorded in include/config/auto.conf.cmd.
11 When the compiler is updated, Kconfig will be invoked.
13 - Ensure full rebuild when the compiler is updated
14 include/linux/compiler-version.h contains this option in the comment
15 line so fixdep adds include/config/CC_VERSION_TEXT into the
16 auto-generated dependency. When the compiler is updated, syncconfig
17 will touch it and then every file will be rebuilt.
20 def_bool $(success,test "$(cc-name)" = GCC)
24 default $(cc-version) if CC_IS_GCC
28 def_bool $(success,test "$(cc-name)" = Clang)
32 default $(cc-version) if CC_IS_CLANG
36 def_bool $(success,test "$(as-name)" = GNU)
39 def_bool $(success,test "$(as-name)" = LLVM)
43 # Use clang version if this is the integrated assembler
44 default CLANG_VERSION if AS_IS_LLVM
48 def_bool $(success,test "$(ld-name)" = BFD)
52 default $(ld-version) if LD_IS_BFD
56 def_bool $(success,test "$(ld-name)" = LLD)
60 default $(ld-version) if LD_IS_LLD
63 config RUST_IS_AVAILABLE
64 def_bool $(success,$(srctree)/scripts/rust_is_available.sh)
66 This shows whether a suitable Rust toolchain is available (found).
68 Please see Documentation/rust/quick-start.rst for instructions on how
69 to satisfy the build requirements of Rust support.
71 In particular, the Makefile target 'rustavailable' is useful to check
72 why the Rust toolchain is not being detected.
76 default $(success,$(srctree)/scripts/cc-can-link.sh $(CC) $(CLANG_FLAGS) $(USERCFLAGS) $(USERLDFLAGS) $(m64-flag)) if 64BIT
77 default $(success,$(srctree)/scripts/cc-can-link.sh $(CC) $(CLANG_FLAGS) $(USERCFLAGS) $(USERLDFLAGS) $(m32-flag))
79 config CC_CAN_LINK_STATIC
81 default $(success,$(srctree)/scripts/cc-can-link.sh $(CC) $(CLANG_FLAGS) $(USERCFLAGS) $(USERLDFLAGS) $(m64-flag) -static) if 64BIT
82 default $(success,$(srctree)/scripts/cc-can-link.sh $(CC) $(CLANG_FLAGS) $(USERCFLAGS) $(USERLDFLAGS) $(m32-flag) -static)
84 config CC_HAS_ASM_GOTO_OUTPUT
85 def_bool $(success,echo 'int foo(int x) { asm goto ("": "=r"(x) ::: bar); return x; bar: return 0; }' | $(CC) -x c - -c -o /dev/null)
87 config CC_HAS_ASM_GOTO_TIED_OUTPUT
88 depends on CC_HAS_ASM_GOTO_OUTPUT
89 # Detect buggy gcc and clang, fixed in gcc-11 clang-14.
90 def_bool $(success,echo 'int foo(int *x) { asm goto (".long (%l[bar]) - .": "+m"(*x) ::: bar); return *x; bar: return 0; }' | $CC -x c - -c -o /dev/null)
92 config GCC_ASM_GOTO_OUTPUT_WORKAROUND
94 depends on CC_IS_GCC && CC_HAS_ASM_GOTO_OUTPUT
95 # Fixed in GCC 14, 13.3, 12.4 and 11.5
96 # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113921
97 default y if GCC_VERSION < 110500
98 default y if GCC_VERSION >= 120000 && GCC_VERSION < 120400
99 default y if GCC_VERSION >= 130000 && GCC_VERSION < 130300
101 config TOOLS_SUPPORT_RELR
102 def_bool $(success,env "CC=$(CC)" "LD=$(LD)" "NM=$(NM)" "OBJCOPY=$(OBJCOPY)" $(srctree)/scripts/tools-support-relr.sh)
104 config CC_HAS_ASM_INLINE
105 def_bool $(success,echo 'void foo(void) { asm inline (""); }' | $(CC) -x c - -c -o /dev/null)
107 config CC_HAS_NO_PROFILE_FN_ATTR
108 def_bool $(success,echo '__attribute__((no_profile_instrument_function)) int x();' | $(CC) -x c - -c -o /dev/null -Werror)
110 config PAHOLE_VERSION
112 default $(shell,$(srctree)/scripts/pahole-version.sh $(PAHOLE))
120 config BUILDTIME_TABLE_SORT
123 config THREAD_INFO_IN_TASK
126 Select this to move thread_info off the stack into task_struct. To
127 make this work, an arch will need to remove all thread_info fields
128 except flags and fix any runtime bugs.
130 One subtle change that will be needed is to use try_get_task_stack()
131 and put_task_stack() in save_thread_stack_tsk() and get_wchan().
140 depends on BROKEN || !SMP
143 config INIT_ENV_ARG_LIMIT
148 Maximum of each of the number of arguments and environment
149 variables passed to init from the kernel command line.
152 bool "Compile also drivers which will not load"
155 Some drivers can be compiled on a different platform than they are
156 intended to be run on. Despite they cannot be loaded there (or even
157 when they load they cannot be used due to missing HW support),
158 developers still, opposing to distributors, might want to build such
159 drivers to compile-test them.
161 If you are a developer and want to build everything available, say Y
162 here. If you are a user/distributor, say N here to exclude useless
163 drivers to be distributed.
166 bool "Compile the kernel with warnings as errors"
169 A kernel build should not cause any compiler warnings, and this
170 enables the '-Werror' (for C) and '-Dwarnings' (for Rust) flags
171 to enforce that rule by default. Certain warnings from other tools
172 such as the linker may be upgraded to errors with this option as
175 However, if you have a new (or very old) compiler or linker with odd
176 and unusual warnings, or you have some architecture with problems,
177 you may need to disable this config option in order to
178 successfully build the kernel.
182 config UAPI_HEADER_TEST
183 bool "Compile test UAPI headers"
184 depends on HEADERS_INSTALL && CC_CAN_LINK
186 Compile test headers exported to user-space to ensure they are
187 self-contained, i.e. compilable as standalone units.
189 If you are a developer or tester and want to ensure the exported
190 headers are self-contained, say Y here. Otherwise, choose N.
193 string "Local version - append to kernel release"
195 Append an extra string to the end of your kernel version.
196 This will show up when you type uname, for example.
197 The string you set here will be appended after the contents of
198 any files with a filename matching localversion* in your
199 object and source tree, in that order. Your total string can
200 be a maximum of 64 characters.
202 config LOCALVERSION_AUTO
203 bool "Automatically append version information to the version string"
205 depends on !COMPILE_TEST
207 This will try to automatically determine if the current tree is a
208 release tree by looking for git tags that belong to the current
209 top of tree revision.
211 A string of the format -gxxxxxxxx will be added to the localversion
212 if a git-based tree is found. The string generated by this will be
213 appended after any matching localversion* files, and after the value
214 set in CONFIG_LOCALVERSION.
216 (The actual string used here is the first 12 characters produced
217 by running the command:
219 $ git rev-parse --verify HEAD
221 which is done within the script "scripts/setlocalversion".)
224 string "Build ID Salt"
227 The build ID is used to link binaries and their debug info. Setting
228 this option will use the value in the calculation of the build id.
229 This is mostly useful for distributions which want to ensure the
230 build is unique between builds. It's safe to leave the default.
232 config HAVE_KERNEL_GZIP
235 config HAVE_KERNEL_BZIP2
238 config HAVE_KERNEL_LZMA
241 config HAVE_KERNEL_XZ
244 config HAVE_KERNEL_LZO
247 config HAVE_KERNEL_LZ4
250 config HAVE_KERNEL_ZSTD
253 config HAVE_KERNEL_UNCOMPRESSED
257 prompt "Kernel compression mode"
259 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
261 The linux kernel is a kind of self-extracting executable.
262 Several compression algorithms are available, which differ
263 in efficiency, compression and decompression speed.
264 Compression speed is only relevant when building a kernel.
265 Decompression speed is relevant at each boot.
267 If you have any problems with bzip2 or lzma compressed
268 kernels, mail me (Alain Knaff) <alain@knaff.lu>. (An older
269 version of this functionality (bzip2 only), for 2.4, was
270 supplied by Christian Ludwig)
272 High compression options are mostly useful for users, who
273 are low on disk space (embedded systems), but for whom ram
276 If in doubt, select 'gzip'
280 depends on HAVE_KERNEL_GZIP
282 The old and tried gzip compression. It provides a good balance
283 between compression ratio and decompression speed.
287 depends on HAVE_KERNEL_BZIP2
289 Its compression ratio and speed is intermediate.
290 Decompression speed is slowest among the choices. The kernel
291 size is about 10% smaller with bzip2, in comparison to gzip.
292 Bzip2 uses a large amount of memory. For modern kernels you
293 will need at least 8MB RAM or more for booting.
297 depends on HAVE_KERNEL_LZMA
299 This compression algorithm's ratio is best. Decompression speed
300 is between gzip and bzip2. Compression is slowest.
301 The kernel size is about 33% smaller with LZMA in comparison to gzip.
305 depends on HAVE_KERNEL_XZ
307 XZ uses the LZMA2 algorithm and instruction set specific
308 BCJ filters which can improve compression ratio of executable
309 code. The size of the kernel is about 30% smaller with XZ in
310 comparison to gzip. On architectures for which there is a BCJ
311 filter (i386, x86_64, ARM, IA-64, PowerPC, and SPARC), XZ
312 will create a few percent smaller kernel than plain LZMA.
314 The speed is about the same as with LZMA: The decompression
315 speed of XZ is better than that of bzip2 but worse than gzip
316 and LZO. Compression is slow.
320 depends on HAVE_KERNEL_LZO
322 Its compression ratio is the poorest among the choices. The kernel
323 size is about 10% bigger than gzip; however its speed
324 (both compression and decompression) is the fastest.
328 depends on HAVE_KERNEL_LZ4
330 LZ4 is an LZ77-type compressor with a fixed, byte-oriented encoding.
331 A preliminary version of LZ4 de/compression tool is available at
332 <https://code.google.com/p/lz4/>.
334 Its compression ratio is worse than LZO. The size of the kernel
335 is about 8% bigger than LZO. But the decompression speed is
340 depends on HAVE_KERNEL_ZSTD
342 ZSTD is a compression algorithm targeting intermediate compression
343 with fast decompression speed. It will compress better than GZIP and
344 decompress around the same speed as LZO, but slower than LZ4. You
345 will need at least 192 KB RAM or more for booting. The zstd command
346 line tool is required for compression.
348 config KERNEL_UNCOMPRESSED
350 depends on HAVE_KERNEL_UNCOMPRESSED
352 Produce uncompressed kernel image. This option is usually not what
353 you want. It is useful for debugging the kernel in slow simulation
354 environments, where decompressing and moving the kernel is awfully
355 slow. This option allows early boot code to skip the decompressor
356 and jump right at uncompressed kernel image.
361 string "Default init path"
364 This option determines the default init for the system if no init=
365 option is passed on the kernel command line. If the requested path is
366 not present, we will still then move on to attempting further
367 locations (e.g. /sbin/init, etc). If this is empty, we will just use
368 the fallback list when init= is not passed.
370 config DEFAULT_HOSTNAME
371 string "Default hostname"
374 This option determines the default system hostname before userspace
375 calls sethostname(2). The kernel traditionally uses "(none)" here,
376 but you may wish to use a different default here to make a minimal
377 system more usable with less configuration.
382 Inter Process Communication is a suite of library functions and
383 system calls which let processes (running programs) synchronize and
384 exchange information. It is generally considered to be a good thing,
385 and some programs won't run unless you say Y here. In particular, if
386 you want to run the DOS emulator dosemu under Linux (read the
387 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
388 you'll need to say Y here.
390 You can find documentation about IPC with "info ipc" and also in
391 section 6.4 of the Linux Programmer's Guide, available from
392 <http://www.tldp.org/guides.html>.
394 config SYSVIPC_SYSCTL
400 config SYSVIPC_COMPAT
402 depends on COMPAT && SYSVIPC
405 bool "POSIX Message Queues"
408 POSIX variant of message queues is a part of IPC. In POSIX message
409 queues every message has a priority which decides about succession
410 of receiving it by a process. If you want to compile and run
411 programs written e.g. for Solaris with use of its POSIX message
412 queues (functions mq_*) say Y here.
414 POSIX message queues are visible as a filesystem called 'mqueue'
415 and can be mounted somewhere if you want to do filesystem
416 operations on message queues.
420 config POSIX_MQUEUE_SYSCTL
422 depends on POSIX_MQUEUE
427 bool "General notification queue"
431 This is a general notification queue for the kernel to pass events to
432 userspace by splicing them into pipes. It can be used in conjunction
433 with watches for key/keyring change notifications and device
436 See Documentation/core-api/watch_queue.rst
438 config CROSS_MEMORY_ATTACH
439 bool "Enable process_vm_readv/writev syscalls"
443 Enabling this option adds the system calls process_vm_readv and
444 process_vm_writev which allow a process with the correct privileges
445 to directly read from or write to another process' address space.
446 See the man page for more details.
449 bool "uselib syscall (for libc5 and earlier)"
450 default ALPHA || M68K || SPARC
452 This option enables the uselib syscall, a system call used in the
453 dynamic linker from libc5 and earlier. glibc does not use this
454 system call. If you intend to run programs built on libc5 or
455 earlier, you may need to enable this syscall. Current systems
456 running glibc can safely disable this.
459 bool "Auditing support"
462 Enable auditing infrastructure that can be used with another
463 kernel subsystem, such as SELinux (which requires this for
464 logging of avc messages output). System call auditing is included
465 on architectures which support it.
467 config HAVE_ARCH_AUDITSYSCALL
472 depends on AUDIT && HAVE_ARCH_AUDITSYSCALL
475 source "kernel/irq/Kconfig"
476 source "kernel/time/Kconfig"
477 source "kernel/bpf/Kconfig"
478 source "kernel/Kconfig.preempt"
480 menu "CPU/Task time and stats accounting"
482 config VIRT_CPU_ACCOUNTING
486 prompt "Cputime accounting"
487 default TICK_CPU_ACCOUNTING
489 # Kind of a stub config for the pure tick based cputime accounting
490 config TICK_CPU_ACCOUNTING
491 bool "Simple tick based cputime accounting"
492 depends on !S390 && !NO_HZ_FULL
494 This is the basic tick based cputime accounting that maintains
495 statistics about user, system and idle time spent on per jiffies
500 config VIRT_CPU_ACCOUNTING_NATIVE
501 bool "Deterministic task and CPU time accounting"
502 depends on HAVE_VIRT_CPU_ACCOUNTING && !NO_HZ_FULL
503 select VIRT_CPU_ACCOUNTING
505 Select this option to enable more accurate task and CPU time
506 accounting. This is done by reading a CPU counter on each
507 kernel entry and exit and on transitions within the kernel
508 between system, softirq and hardirq state, so there is a
509 small performance impact. In the case of s390 or IBM POWER > 5,
510 this also enables accounting of stolen time on logically-partitioned
513 config VIRT_CPU_ACCOUNTING_GEN
514 bool "Full dynticks CPU time accounting"
515 depends on HAVE_CONTEXT_TRACKING_USER
516 depends on HAVE_VIRT_CPU_ACCOUNTING_GEN
517 depends on GENERIC_CLOCKEVENTS
518 select VIRT_CPU_ACCOUNTING
519 select CONTEXT_TRACKING_USER
521 Select this option to enable task and CPU time accounting on full
522 dynticks systems. This accounting is implemented by watching every
523 kernel-user boundaries using the context tracking subsystem.
524 The accounting is thus performed at the expense of some significant
527 For now this is only useful if you are working on the full
528 dynticks subsystem development.
534 config IRQ_TIME_ACCOUNTING
535 bool "Fine granularity task level IRQ time accounting"
536 depends on HAVE_IRQ_TIME_ACCOUNTING && !VIRT_CPU_ACCOUNTING_NATIVE
538 Select this option to enable fine granularity task irq time
539 accounting. This is done by reading a timestamp on each
540 transitions between softirq and hardirq state, so there can be a
541 small performance impact.
543 If in doubt, say N here.
545 config HAVE_SCHED_AVG_IRQ
547 depends on IRQ_TIME_ACCOUNTING || PARAVIRT_TIME_ACCOUNTING
550 config SCHED_THERMAL_PRESSURE
552 default y if ARM && ARM_CPU_TOPOLOGY
555 depends on CPU_FREQ_THERMAL
557 Select this option to enable thermal pressure accounting in the
558 scheduler. Thermal pressure is the value conveyed to the scheduler
559 that reflects the reduction in CPU compute capacity resulted from
560 thermal throttling. Thermal throttling occurs when the performance of
561 a CPU is capped due to high operating temperatures.
563 If selected, the scheduler will be able to balance tasks accordingly,
564 i.e. put less load on throttled CPUs than on non/less throttled ones.
566 This requires the architecture to implement
567 arch_update_thermal_pressure() and arch_scale_thermal_pressure().
569 config BSD_PROCESS_ACCT
570 bool "BSD Process Accounting"
573 If you say Y here, a user level program will be able to instruct the
574 kernel (via a special system call) to write process accounting
575 information to a file: whenever a process exits, information about
576 that process will be appended to the file by the kernel. The
577 information includes things such as creation time, owning user,
578 command name, memory usage, controlling terminal etc. (the complete
579 list is in the struct acct in <file:include/linux/acct.h>). It is
580 up to the user level program to do useful things with this
581 information. This is generally a good idea, so say Y.
583 config BSD_PROCESS_ACCT_V3
584 bool "BSD Process Accounting version 3 file format"
585 depends on BSD_PROCESS_ACCT
588 If you say Y here, the process accounting information is written
589 in a new file format that also logs the process IDs of each
590 process and its parent. Note that this file format is incompatible
591 with previous v0/v1/v2 file formats, so you will need updated tools
592 for processing it. A preliminary version of these tools is available
593 at <http://www.gnu.org/software/acct/>.
596 bool "Export task/process statistics through netlink"
601 Export selected statistics for tasks/processes through the
602 generic netlink interface. Unlike BSD process accounting, the
603 statistics are available during the lifetime of tasks/processes as
604 responses to commands. Like BSD accounting, they are sent to user
609 config TASK_DELAY_ACCT
610 bool "Enable per-task delay accounting"
614 Collect information on time spent by a task waiting for system
615 resources like cpu, synchronous block I/O completion and swapping
616 in pages. Such statistics can help in setting a task's priorities
617 relative to other tasks for cpu, io, rss limits etc.
622 bool "Enable extended accounting over taskstats"
625 Collect extended task accounting data and send the data
626 to userland for processing over the taskstats interface.
630 config TASK_IO_ACCOUNTING
631 bool "Enable per-task storage I/O accounting"
632 depends on TASK_XACCT
634 Collect information on the number of bytes of storage I/O which this
640 bool "Pressure stall information tracking"
643 Collect metrics that indicate how overcommitted the CPU, memory,
644 and IO capacity are in the system.
646 If you say Y here, the kernel will create /proc/pressure/ with the
647 pressure statistics files cpu, memory, and io. These will indicate
648 the share of walltime in which some or all tasks in the system are
649 delayed due to contention of the respective resource.
651 In kernels with cgroup support, cgroups (cgroup2 only) will
652 have cpu.pressure, memory.pressure, and io.pressure files,
653 which aggregate pressure stalls for the grouped tasks only.
655 For more details see Documentation/accounting/psi.rst.
659 config PSI_DEFAULT_DISABLED
660 bool "Require boot parameter to enable pressure stall information tracking"
664 If set, pressure stall information tracking will be disabled
665 per default but can be enabled through passing psi=1 on the
666 kernel commandline during boot.
668 This feature adds some code to the task wakeup and sleep
669 paths of the scheduler. The overhead is too low to affect
670 common scheduling-intense workloads in practice (such as
671 webservers, memcache), but it does show up in artificial
672 scheduler stress tests, such as hackbench.
674 If you are paranoid and not sure what the kernel will be
679 endmenu # "CPU/Task time and stats accounting"
683 depends on SMP || COMPILE_TEST
686 Make sure that CPUs running critical tasks are not disturbed by
687 any source of "noise" such as unbound workqueues, timers, kthreads...
688 Unbound jobs get offloaded to housekeeping CPUs. This is driven by
689 the "isolcpus=" boot parameter.
693 source "kernel/rcu/Kconfig"
696 tristate "Kernel .config support"
698 This option enables the complete Linux kernel ".config" file
699 contents to be saved in the kernel. It provides documentation
700 of which kernel options are used in a running kernel or in an
701 on-disk kernel. This information can be extracted from the kernel
702 image file with the script scripts/extract-ikconfig and used as
703 input to rebuild the current kernel or to build another kernel.
704 It can also be extracted from a running kernel by reading
705 /proc/config.gz if enabled (below).
708 bool "Enable access to .config through /proc/config.gz"
709 depends on IKCONFIG && PROC_FS
711 This option enables access to the kernel configuration file
712 through /proc/config.gz.
715 tristate "Enable kernel headers through /sys/kernel/kheaders.tar.xz"
718 This option enables access to the in-kernel headers that are generated during
719 the build process. These can be used to build eBPF tracing programs,
720 or similar programs. If you build the headers as a module, a module called
721 kheaders.ko is built which can be loaded on-demand to get access to headers.
724 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
729 Select the minimal kernel log buffer size as a power of 2.
730 The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
731 parameter, see below. Any higher size also might be forced
732 by "log_buf_len" boot parameter.
742 config LOG_CPU_MAX_BUF_SHIFT
743 int "CPU kernel log buffer size contribution (13 => 8 KB, 17 => 128KB)"
746 default 12 if !BASE_SMALL
747 default 0 if BASE_SMALL
750 This option allows to increase the default ring buffer size
751 according to the number of CPUs. The value defines the contribution
752 of each CPU as a power of 2. The used space is typically only few
753 lines however it might be much more when problems are reported,
756 The increased size means that a new buffer has to be allocated and
757 the original static one is unused. It makes sense only on systems
758 with more CPUs. Therefore this value is used only when the sum of
759 contributions is greater than the half of the default kernel ring
760 buffer as defined by LOG_BUF_SHIFT. The default values are set
761 so that more than 16 CPUs are needed to trigger the allocation.
763 Also this option is ignored when "log_buf_len" kernel parameter is
764 used as it forces an exact (power of two) size of the ring buffer.
766 The number of possible CPUs is used for this computation ignoring
767 hotplugging making the computation optimal for the worst case
768 scenario while allowing a simple algorithm to be used from bootup.
770 Examples shift values and their meaning:
771 17 => 128 KB for each CPU
772 16 => 64 KB for each CPU
773 15 => 32 KB for each CPU
774 14 => 16 KB for each CPU
775 13 => 8 KB for each CPU
776 12 => 4 KB for each CPU
779 bool "Printk indexing debugfs interface"
780 depends on PRINTK && DEBUG_FS
782 Add support for indexing of all printk formats known at compile time
783 at <debugfs>/printk/index/<module>.
785 This can be used as part of maintaining daemons which monitor
786 /dev/kmsg, as it permits auditing the printk formats present in a
787 kernel, allowing detection of cases where monitored printks are
788 changed or no longer present.
790 There is no additional runtime cost to printk with this enabled.
793 # Architectures with an unreliable sched_clock() should select this:
795 config HAVE_UNSTABLE_SCHED_CLOCK
798 config GENERIC_SCHED_CLOCK
801 menu "Scheduler features"
804 bool "Enable utilization clamping for RT/FAIR tasks"
805 depends on CPU_FREQ_GOV_SCHEDUTIL
807 This feature enables the scheduler to track the clamped utilization
808 of each CPU based on RUNNABLE tasks scheduled on that CPU.
810 With this option, the user can specify the min and max CPU
811 utilization allowed for RUNNABLE tasks. The max utilization defines
812 the maximum frequency a task should use while the min utilization
813 defines the minimum frequency it should use.
815 Both min and max utilization clamp values are hints to the scheduler,
816 aiming at improving its frequency selection policy, but they do not
817 enforce or grant any specific bandwidth for tasks.
821 config UCLAMP_BUCKETS_COUNT
822 int "Number of supported utilization clamp buckets"
825 depends on UCLAMP_TASK
827 Defines the number of clamp buckets to use. The range of each bucket
828 will be SCHED_CAPACITY_SCALE/UCLAMP_BUCKETS_COUNT. The higher the
829 number of clamp buckets the finer their granularity and the higher
830 the precision of clamping aggregation and tracking at run-time.
832 For example, with the minimum configuration value we will have 5
833 clamp buckets tracking 20% utilization each. A 25% boosted tasks will
834 be refcounted in the [20..39]% bucket and will set the bucket clamp
835 effective value to 25%.
836 If a second 30% boosted task should be co-scheduled on the same CPU,
837 that task will be refcounted in the same bucket of the first task and
838 it will boost the bucket clamp effective value to 30%.
839 The clamp effective value of a bucket is reset to its nominal value
840 (20% in the example above) when there are no more tasks refcounted in
843 An additional boost/capping margin can be added to some tasks. In the
844 example above the 25% task will be boosted to 30% until it exits the
845 CPU. If that should be considered not acceptable on certain systems,
846 it's always possible to reduce the margin by increasing the number of
847 clamp buckets to trade off used memory for run-time tracking
850 If in doubt, use the default value.
855 # For architectures that want to enable the support for NUMA-affine scheduler
858 config ARCH_SUPPORTS_NUMA_BALANCING
862 # For architectures that prefer to flush all TLBs after a number of pages
863 # are unmapped instead of sending one IPI per page to flush. The architecture
864 # must provide guarantees on what happens if a clean TLB cache entry is
865 # written after the unmap. Details are in mm/rmap.c near the check for
866 # should_defer_flush. The architecture should also consider if the full flush
867 # and the refill costs are offset by the savings of sending fewer IPIs.
868 config ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH
872 def_bool !$(cc-option,$(m64-flag) -D__SIZEOF_INT128__=0) && 64BIT
874 config CC_IMPLICIT_FALLTHROUGH
876 default "-Wimplicit-fallthrough=5" if CC_IS_GCC && $(cc-option,-Wimplicit-fallthrough=5)
877 default "-Wimplicit-fallthrough" if CC_IS_CLANG && $(cc-option,-Wunreachable-code-fallthrough)
879 # Currently, disable gcc-10+ array-bounds globally.
880 # It's still broken in gcc-13, so no upper bound yet.
881 config GCC10_NO_ARRAY_BOUNDS
884 config CC_NO_ARRAY_BOUNDS
886 default y if CC_IS_GCC && GCC_VERSION >= 100000 && GCC10_NO_ARRAY_BOUNDS
888 # Currently, disable -Wstringop-overflow for GCC globally.
889 config GCC_NO_STRINGOP_OVERFLOW
892 config CC_NO_STRINGOP_OVERFLOW
894 default y if CC_IS_GCC && GCC_NO_STRINGOP_OVERFLOW
896 config CC_STRINGOP_OVERFLOW
898 default y if CC_IS_GCC && !CC_NO_STRINGOP_OVERFLOW
901 # For architectures that know their GCC __int128 support is sound
903 config ARCH_SUPPORTS_INT128
906 # For architectures that (ab)use NUMA to represent different memory regions
907 # all cpu-local but of different latencies, such as SuperH.
909 config ARCH_WANT_NUMA_VARIABLE_LOCALITY
912 config NUMA_BALANCING
913 bool "Memory placement aware NUMA scheduler"
914 depends on ARCH_SUPPORTS_NUMA_BALANCING
915 depends on !ARCH_WANT_NUMA_VARIABLE_LOCALITY
916 depends on SMP && NUMA && MIGRATION && !PREEMPT_RT
918 This option adds support for automatic NUMA aware memory/task placement.
919 The mechanism is quite primitive and is based on migrating memory when
920 it has references to the node the task is running on.
922 This system will be inactive on UMA systems.
924 config NUMA_BALANCING_DEFAULT_ENABLED
925 bool "Automatically enable NUMA aware memory/task placement"
927 depends on NUMA_BALANCING
929 If set, automatic NUMA balancing will be enabled if running on a NUMA
933 bool "Control Group support"
936 This option adds support for grouping sets of processes together, for
937 use with process control subsystems such as Cpusets, CFS, memory
938 controls or device isolation.
940 - Documentation/scheduler/sched-design-CFS.rst (CFS)
941 - Documentation/admin-guide/cgroup-v1/ (features for grouping, isolation
942 and resource control)
951 config CGROUP_FAVOR_DYNMODS
952 bool "Favor dynamic modification latency reduction by default"
954 This option enables the "favordynmods" mount option by default
955 which reduces the latencies of dynamic cgroup modifications such
956 as task migrations and controller on/offs at the cost of making
957 hot path operations such as forks and exits more expensive.
962 bool "Memory controller"
966 Provides control over the memory footprint of tasks in a cgroup.
978 Generic block IO controller cgroup interface. This is the common
979 cgroup interface which should be used by various IO controlling
982 Currently, CFQ IO scheduler uses it to recognize task groups and
983 control disk bandwidth allocation (proportional time slice allocation)
984 to such task groups. It is also used by bio throttling logic in
985 block layer to implement upper limit in IO rates on a device.
987 This option only enables generic Block IO controller infrastructure.
988 One needs to also enable actual IO controlling logic/policy. For
989 enabling proportional weight division of disk bandwidth in CFQ, set
990 CONFIG_BFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
991 CONFIG_BLK_DEV_THROTTLING=y.
993 See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information.
995 config CGROUP_WRITEBACK
997 depends on MEMCG && BLK_CGROUP
1000 menuconfig CGROUP_SCHED
1001 bool "CPU controller"
1004 This feature lets CPU scheduler recognize task groups and control CPU
1005 bandwidth allocation to such task groups. It uses cgroups to group
1009 config FAIR_GROUP_SCHED
1010 bool "Group scheduling for SCHED_OTHER"
1011 depends on CGROUP_SCHED
1012 default CGROUP_SCHED
1014 config CFS_BANDWIDTH
1015 bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED"
1016 depends on FAIR_GROUP_SCHED
1019 This option allows users to define CPU bandwidth rates (limits) for
1020 tasks running within the fair group scheduler. Groups with no limit
1021 set are considered to be unconstrained and will run with no
1023 See Documentation/scheduler/sched-bwc.rst for more information.
1025 config RT_GROUP_SCHED
1026 bool "Group scheduling for SCHED_RR/FIFO"
1027 depends on CGROUP_SCHED
1030 This feature lets you explicitly allocate real CPU bandwidth
1031 to task groups. If enabled, it will also make it impossible to
1032 schedule realtime tasks for non-root users until you allocate
1033 realtime bandwidth for them.
1034 See Documentation/scheduler/sched-rt-group.rst for more information.
1040 depends on SMP && RSEQ
1042 config UCLAMP_TASK_GROUP
1043 bool "Utilization clamping per group of tasks"
1044 depends on CGROUP_SCHED
1045 depends on UCLAMP_TASK
1048 This feature enables the scheduler to track the clamped utilization
1049 of each CPU based on RUNNABLE tasks currently scheduled on that CPU.
1051 When this option is enabled, the user can specify a min and max
1052 CPU bandwidth which is allowed for each single task in a group.
1053 The max bandwidth allows to clamp the maximum frequency a task
1054 can use, while the min bandwidth allows to define a minimum
1055 frequency a task will always use.
1057 When task group based utilization clamping is enabled, an eventually
1058 specified task-specific clamp value is constrained by the cgroup
1059 specified clamp value. Both minimum and maximum task clamping cannot
1060 be bigger than the corresponding clamping defined at task group level.
1065 bool "PIDs controller"
1067 Provides enforcement of process number limits in the scope of a
1068 cgroup. Any attempt to fork more processes than is allowed in the
1069 cgroup will fail. PIDs are fundamentally a global resource because it
1070 is fairly trivial to reach PID exhaustion before you reach even a
1071 conservative kmemcg limit. As a result, it is possible to grind a
1072 system to halt without being limited by other cgroup policies. The
1073 PIDs controller is designed to stop this from happening.
1075 It should be noted that organisational operations (such as attaching
1076 to a cgroup hierarchy) will *not* be blocked by the PIDs controller,
1077 since the PIDs limit only affects a process's ability to fork, not to
1081 bool "RDMA controller"
1083 Provides enforcement of RDMA resources defined by IB stack.
1084 It is fairly easy for consumers to exhaust RDMA resources, which
1085 can result into resource unavailability to other consumers.
1086 RDMA controller is designed to stop this from happening.
1087 Attaching processes with active RDMA resources to the cgroup
1088 hierarchy is allowed even if can cross the hierarchy's limit.
1090 config CGROUP_FREEZER
1091 bool "Freezer controller"
1093 Provides a way to freeze and unfreeze all tasks in a
1096 This option affects the ORIGINAL cgroup interface. The cgroup2 memory
1097 controller includes important in-kernel memory consumers per default.
1099 If you're using cgroup2, say N.
1101 config CGROUP_HUGETLB
1102 bool "HugeTLB controller"
1103 depends on HUGETLB_PAGE
1107 Provides a cgroup controller for HugeTLB pages.
1108 When you enable this, you can put a per cgroup limit on HugeTLB usage.
1109 The limit is enforced during page fault. Since HugeTLB doesn't
1110 support page reclaim, enforcing the limit at page fault time implies
1111 that, the application will get SIGBUS signal if it tries to access
1112 HugeTLB pages beyond its limit. This requires the application to know
1113 beforehand how much HugeTLB pages it would require for its use. The
1114 control group is tracked in the third page lru pointer. This means
1115 that we cannot use the controller with huge page less than 3 pages.
1118 bool "Cpuset controller"
1121 This option will let you create and manage CPUSETs which
1122 allow dynamically partitioning a system into sets of CPUs and
1123 Memory Nodes and assigning tasks to run only within those sets.
1124 This is primarily useful on large SMP or NUMA systems.
1128 config PROC_PID_CPUSET
1129 bool "Include legacy /proc/<pid>/cpuset file"
1133 config CGROUP_DEVICE
1134 bool "Device controller"
1136 Provides a cgroup controller implementing whitelists for
1137 devices which a process in the cgroup can mknod or open.
1139 config CGROUP_CPUACCT
1140 bool "Simple CPU accounting controller"
1142 Provides a simple controller for monitoring the
1143 total CPU consumed by the tasks in a cgroup.
1146 bool "Perf controller"
1147 depends on PERF_EVENTS
1149 This option extends the perf per-cpu mode to restrict monitoring
1150 to threads which belong to the cgroup specified and run on the
1151 designated cpu. Or this can be used to have cgroup ID in samples
1152 so that it can monitor performance events among cgroups.
1157 bool "Support for eBPF programs attached to cgroups"
1158 depends on BPF_SYSCALL
1159 select SOCK_CGROUP_DATA
1161 Allow attaching eBPF programs to a cgroup using the bpf(2)
1162 syscall command BPF_PROG_ATTACH.
1164 In which context these programs are accessed depends on the type
1165 of attachment. For instance, programs that are attached using
1166 BPF_CGROUP_INET_INGRESS will be executed on the ingress path of
1170 bool "Misc resource controller"
1173 Provides a controller for miscellaneous resources on a host.
1175 Miscellaneous scalar resources are the resources on the host system
1176 which cannot be abstracted like the other cgroups. This controller
1177 tracks and limits the miscellaneous resources used by a process
1178 attached to a cgroup hierarchy.
1180 For more information, please check misc cgroup section in
1181 /Documentation/admin-guide/cgroup-v2.rst.
1184 bool "Debug controller"
1186 depends on DEBUG_KERNEL
1188 This option enables a simple controller that exports
1189 debugging information about the cgroups framework. This
1190 controller is for control cgroup debugging only. Its
1191 interfaces are not stable.
1195 config SOCK_CGROUP_DATA
1201 menuconfig NAMESPACES
1202 bool "Namespaces support" if EXPERT
1203 depends on MULTIUSER
1206 Provides the way to make tasks work with different objects using
1207 the same id. For example same IPC id may refer to different objects
1208 or same user id or pid may refer to different tasks when used in
1209 different namespaces.
1214 bool "UTS namespace"
1217 In this namespace tasks see different info provided with the
1221 bool "TIME namespace"
1222 depends on GENERIC_VDSO_TIME_NS
1225 In this namespace boottime and monotonic clocks can be set.
1226 The time will keep going with the same pace.
1229 bool "IPC namespace"
1230 depends on (SYSVIPC || POSIX_MQUEUE)
1233 In this namespace tasks work with IPC ids which correspond to
1234 different IPC objects in different namespaces.
1237 bool "User namespace"
1240 This allows containers, i.e. vservers, to use user namespaces
1241 to provide different user info for different servers.
1243 When user namespaces are enabled in the kernel it is
1244 recommended that the MEMCG option also be enabled and that
1245 user-space use the memory control groups to limit the amount
1246 of memory a memory unprivileged users can use.
1251 bool "PID Namespaces"
1254 Support process id namespaces. This allows having multiple
1255 processes with the same pid as long as they are in different
1256 pid namespaces. This is a building block of containers.
1259 bool "Network namespace"
1263 Allow user space to create what appear to be multiple instances
1264 of the network stack.
1268 config CHECKPOINT_RESTORE
1269 bool "Checkpoint/restore support"
1271 select PROC_CHILDREN
1275 Enables additional kernel features in a sake of checkpoint/restore.
1276 In particular it adds auxiliary prctl codes to setup process text,
1277 data and heap segment sizes, and a few additional /proc filesystem
1280 If unsure, say N here.
1282 config SCHED_AUTOGROUP
1283 bool "Automatic process group scheduling"
1286 select FAIR_GROUP_SCHED
1288 This option optimizes the scheduler for common desktop workloads by
1289 automatically creating and populating task groups. This separation
1290 of workloads isolates aggressive CPU burners (like build jobs) from
1291 desktop applications. Task group autogeneration is currently based
1295 bool "Kernel->user space relay support (formerly relayfs)"
1298 This option enables support for relay interface support in
1299 certain file systems (such as debugfs).
1300 It is designed to provide an efficient mechanism for tools and
1301 facilities to relay large amounts of data from kernel space to
1306 config BLK_DEV_INITRD
1307 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
1309 The initial RAM filesystem is a ramfs which is loaded by the
1310 boot loader (loadlin or lilo) and that is mounted as root
1311 before the normal boot procedure. It is typically used to
1312 load modules needed to mount the "real" root file system,
1313 etc. See <file:Documentation/admin-guide/initrd.rst> for details.
1315 If RAM disk support (BLK_DEV_RAM) is also included, this
1316 also enables initial RAM disk (initrd) support and adds
1317 15 Kbytes (more on some other architectures) to the kernel size.
1323 source "usr/Kconfig"
1328 bool "Boot config support"
1329 select BLK_DEV_INITRD if !BOOT_CONFIG_EMBED
1331 Extra boot config allows system admin to pass a config file as
1332 complemental extension of kernel cmdline when booting.
1333 The boot config file must be attached at the end of initramfs
1334 with checksum, size and magic word.
1335 See <file:Documentation/admin-guide/bootconfig.rst> for details.
1339 config BOOT_CONFIG_FORCE
1340 bool "Force unconditional bootconfig processing"
1341 depends on BOOT_CONFIG
1342 default y if BOOT_CONFIG_EMBED
1344 With this Kconfig option set, BOOT_CONFIG processing is carried
1345 out even when the "bootconfig" kernel-boot parameter is omitted.
1346 In fact, with this Kconfig option set, there is no way to
1347 make the kernel ignore the BOOT_CONFIG-supplied kernel-boot
1352 config BOOT_CONFIG_EMBED
1353 bool "Embed bootconfig file in the kernel"
1354 depends on BOOT_CONFIG
1356 Embed a bootconfig file given by BOOT_CONFIG_EMBED_FILE in the
1357 kernel. Usually, the bootconfig file is loaded with the initrd
1358 image. But if the system doesn't support initrd, this option will
1359 help you by embedding a bootconfig file while building the kernel.
1363 config BOOT_CONFIG_EMBED_FILE
1364 string "Embedded bootconfig file path"
1365 depends on BOOT_CONFIG_EMBED
1367 Specify a bootconfig file which will be embedded to the kernel.
1368 This bootconfig will be used if there is no initrd or no other
1369 bootconfig in the initrd.
1371 config INITRAMFS_PRESERVE_MTIME
1372 bool "Preserve cpio archive mtimes in initramfs"
1375 Each entry in an initramfs cpio archive carries an mtime value. When
1376 enabled, extracted cpio items take this mtime, with directory mtime
1377 setting deferred until after creation of any child entries.
1382 prompt "Compiler optimization level"
1383 default CC_OPTIMIZE_FOR_PERFORMANCE
1385 config CC_OPTIMIZE_FOR_PERFORMANCE
1386 bool "Optimize for performance (-O2)"
1388 This is the default optimization level for the kernel, building
1389 with the "-O2" compiler flag for best performance and most
1390 helpful compile-time warnings.
1392 config CC_OPTIMIZE_FOR_SIZE
1393 bool "Optimize for size (-Os)"
1395 Choosing this option will pass "-Os" to your compiler resulting
1396 in a smaller kernel.
1400 config HAVE_LD_DEAD_CODE_DATA_ELIMINATION
1403 This requires that the arch annotates or otherwise protects
1404 its external entry points from being discarded. Linker scripts
1405 must also merge .text.*, .data.*, and .bss.* correctly into
1406 output sections. Care must be taken not to pull in unrelated
1407 sections (e.g., '.text.init'). Typically '.' in section names
1408 is used to distinguish them from label names / C identifiers.
1410 config LD_DEAD_CODE_DATA_ELIMINATION
1411 bool "Dead code and data elimination (EXPERIMENTAL)"
1412 depends on HAVE_LD_DEAD_CODE_DATA_ELIMINATION
1414 depends on $(cc-option,-ffunction-sections -fdata-sections)
1415 depends on $(ld-option,--gc-sections)
1417 Enable this if you want to do dead code and data elimination with
1418 the linker by compiling with -ffunction-sections -fdata-sections,
1419 and linking with --gc-sections.
1421 This can reduce on disk and in-memory size of the kernel
1422 code and static data, particularly for small configs and
1423 on small systems. This has the possibility of introducing
1424 silently broken kernel if the required annotations are not
1425 present. This option is not well tested yet, so use at your
1428 config LD_ORPHAN_WARN
1430 depends on ARCH_WANT_LD_ORPHAN_WARN
1431 depends on $(ld-option,--orphan-handling=warn)
1432 depends on $(ld-option,--orphan-handling=error)
1434 config LD_ORPHAN_WARN_LEVEL
1436 depends on LD_ORPHAN_WARN
1437 default "error" if WERROR
1446 config SYSCTL_EXCEPTION_TRACE
1449 Enable support for /proc/sys/debug/exception-trace.
1451 config SYSCTL_ARCH_UNALIGN_NO_WARN
1454 Enable support for /proc/sys/kernel/ignore-unaligned-usertrap
1455 Allows arch to define/use @no_unaligned_warning to possibly warn
1456 about unaligned access emulation going on under the hood.
1458 config SYSCTL_ARCH_UNALIGN_ALLOW
1461 Enable support for /proc/sys/kernel/unaligned-trap
1462 Allows arches to define/use @unaligned_enabled to runtime toggle
1463 the unaligned access emulation.
1464 see arch/parisc/kernel/unaligned.c for reference
1466 config HAVE_PCSPKR_PLATFORM
1470 bool "Configure standard kernel features (expert users)"
1471 # Unhide debug options, to make the on-by-default options visible
1474 This option allows certain base kernel options and settings
1475 to be disabled or tweaked. This is for specialized
1476 environments which can tolerate a "non-standard" kernel.
1477 Only use this if you really know what you are doing.
1480 bool "Enable 16-bit UID system calls" if EXPERT
1481 depends on HAVE_UID16 && MULTIUSER
1484 This enables the legacy 16-bit UID syscall wrappers.
1487 bool "Multiple users, groups and capabilities support" if EXPERT
1490 This option enables support for non-root users, groups and
1493 If you say N here, all processes will run with UID 0, GID 0, and all
1494 possible capabilities. Saying N here also compiles out support for
1495 system calls related to UIDs, GIDs, and capabilities, such as setuid,
1498 If unsure, say Y here.
1500 config SGETMASK_SYSCALL
1501 bool "sgetmask/ssetmask syscalls support" if EXPERT
1502 default PARISC || M68K || PPC || MIPS || X86 || SPARC || MICROBLAZE || SUPERH
1504 sys_sgetmask and sys_ssetmask are obsolete system calls
1505 no longer supported in libc but still enabled by default in some
1508 If unsure, leave the default option here.
1510 config SYSFS_SYSCALL
1511 bool "Sysfs syscall support" if EXPERT
1514 sys_sysfs is an obsolete system call no longer supported in libc.
1515 Note that disabling this option is more secure but might break
1516 compatibility with some systems.
1518 If unsure say Y here.
1521 bool "open by fhandle syscalls" if EXPERT
1525 If you say Y here, a user level program will be able to map
1526 file names to handle and then later use the handle for
1527 different file system operations. This is useful in implementing
1528 userspace file servers, which now track files using handles instead
1529 of names. The handle would remain the same even if file names
1530 get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2)
1534 bool "Posix Clocks & timers" if EXPERT
1537 This includes native support for POSIX timers to the kernel.
1538 Some embedded systems have no use for them and therefore they
1539 can be configured out to reduce the size of the kernel image.
1541 When this option is disabled, the following syscalls won't be
1542 available: timer_create, timer_gettime: timer_getoverrun,
1543 timer_settime, timer_delete, clock_adjtime, getitimer,
1544 setitimer, alarm. Furthermore, the clock_settime, clock_gettime,
1545 clock_getres and clock_nanosleep syscalls will be limited to
1546 CLOCK_REALTIME, CLOCK_MONOTONIC and CLOCK_BOOTTIME only.
1552 bool "Enable support for printk" if EXPERT
1555 This option enables normal printk support. Removing it
1556 eliminates most of the message strings from the kernel image
1557 and makes the kernel more or less silent. As this makes it
1558 very difficult to diagnose system problems, saying N here is
1559 strongly discouraged.
1562 bool "BUG() support" if EXPERT
1565 Disabling this option eliminates support for BUG and WARN, reducing
1566 the size of your kernel image and potentially quietly ignoring
1567 numerous fatal conditions. You should only consider disabling this
1568 option for embedded systems with no facilities for reporting errors.
1574 bool "Enable ELF core dumps" if EXPERT
1576 Enable support for generating core dumps. Disabling saves about 4k.
1579 config PCSPKR_PLATFORM
1580 bool "Enable PC-Speaker support" if EXPERT
1581 depends on HAVE_PCSPKR_PLATFORM
1585 This option allows to disable the internal PC-Speaker
1586 support, saving some memory.
1590 bool "Enable full-sized data structures for core" if EXPERT
1592 Disabling this option reduces the size of miscellaneous core
1593 kernel data structures. This saves memory on small machines,
1594 but may reduce performance.
1597 bool "Enable futex support" if EXPERT
1598 depends on !(SPARC32 && SMP)
1602 Disabling this option will cause the kernel to be built without
1603 support for "fast userspace mutexes". The resulting kernel may not
1604 run glibc-based applications correctly.
1608 depends on FUTEX && RT_MUTEXES
1612 bool "Enable eventpoll support" if EXPERT
1615 Disabling this option will cause the kernel to be built without
1616 support for epoll family of system calls.
1619 bool "Enable signalfd() system call" if EXPERT
1622 Enable the signalfd() system call that allows to receive signals
1623 on a file descriptor.
1628 bool "Enable timerfd() system call" if EXPERT
1631 Enable the timerfd() system call that allows to receive timer
1632 events on a file descriptor.
1637 bool "Enable eventfd() system call" if EXPERT
1640 Enable the eventfd() system call that allows to receive both
1641 kernel notification (ie. KAIO) or userspace notifications.
1646 bool "Use full shmem filesystem" if EXPERT
1650 The shmem is an internal filesystem used to manage shared memory.
1651 It is backed by swap and manages resource limits. It is also exported
1652 to userspace as tmpfs if TMPFS is enabled. Disabling this
1653 option replaces shmem and tmpfs with the much simpler ramfs code,
1654 which may be appropriate on small systems without swap.
1657 bool "Enable AIO support" if EXPERT
1660 This option enables POSIX asynchronous I/O which may by used
1661 by some high performance threaded applications. Disabling
1662 this option saves about 7k.
1665 bool "Enable IO uring support" if EXPERT
1669 This option enables support for the io_uring interface, enabling
1670 applications to submit and complete IO through submission and
1671 completion rings that are shared between the kernel and application.
1673 config ADVISE_SYSCALLS
1674 bool "Enable madvise/fadvise syscalls" if EXPERT
1677 This option enables the madvise and fadvise syscalls, used by
1678 applications to advise the kernel about their future memory or file
1679 usage, improving performance. If building an embedded system where no
1680 applications use these syscalls, you can disable this option to save
1684 bool "Enable membarrier() system call" if EXPERT
1687 Enable the membarrier() system call that allows issuing memory
1688 barriers across all running threads, which can be used to distribute
1689 the cost of user-space memory barriers asymmetrically by transforming
1690 pairs of memory barriers into pairs consisting of membarrier() and a
1696 bool "Enable kcmp() system call" if EXPERT
1698 Enable the kernel resource comparison system call. It provides
1699 user-space with the ability to compare two processes to see if they
1700 share a common resource, such as a file descriptor or even virtual
1706 bool "Enable rseq() system call" if EXPERT
1708 depends on HAVE_RSEQ
1711 Enable the restartable sequences system call. It provides a
1712 user-space cache for the current CPU number value, which
1713 speeds up getting the current CPU number from user-space,
1714 as well as an ABI to speed up user-space operations on
1721 bool "Enable debugging of rseq() system call" if EXPERT
1722 depends on RSEQ && DEBUG_KERNEL
1724 Enable extra debugging checks for the rseq system call.
1728 config CACHESTAT_SYSCALL
1729 bool "Enable cachestat() system call" if EXPERT
1732 Enable the cachestat system call, which queries the page cache
1733 statistics of a file (number of cached pages, dirty pages,
1734 pages marked for writeback, (recently) evicted pages).
1736 If unsure say Y here.
1739 bool "PC/104 support" if EXPERT
1741 Expose PC/104 form factor device drivers and options available for
1742 selection and configuration. Enable this option if your target
1743 machine has a PC/104 bus.
1746 bool "Load all symbols for debugging/ksymoops" if EXPERT
1749 Say Y here to let the kernel print out symbolic crash information and
1750 symbolic stack backtraces. This increases the size of the kernel
1751 somewhat, as all symbols have to be loaded into the kernel image.
1753 config KALLSYMS_SELFTEST
1754 bool "Test the basic functions and performance of kallsyms"
1758 Test the basic functions and performance of some interfaces, such as
1759 kallsyms_lookup_name. It also calculates the compression rate of the
1760 kallsyms compression algorithm for the current symbol set.
1762 Start self-test automatically after system startup. Suggest executing
1763 "dmesg | grep kallsyms_selftest" to collect test results. "finish" is
1764 displayed in the last line, indicating that the test is complete.
1767 bool "Include all symbols in kallsyms"
1768 depends on DEBUG_KERNEL && KALLSYMS
1770 Normally kallsyms only contains the symbols of functions for nicer
1771 OOPS messages and backtraces (i.e., symbols from the text and inittext
1772 sections). This is sufficient for most cases. And only if you want to
1773 enable kernel live patching, or other less common use cases (e.g.,
1774 when a debugger is used) all symbols are required (i.e., names of
1775 variables from the data sections, etc).
1777 This option makes sure that all symbols are loaded into the kernel
1778 image (i.e., symbols from all sections) in cost of increased kernel
1779 size (depending on the kernel configuration, it may be 300KiB or
1780 something like this).
1782 Say N unless you really need all symbols, or kernel live patching.
1784 config KALLSYMS_ABSOLUTE_PERCPU
1787 default X86_64 && SMP
1789 config KALLSYMS_BASE_RELATIVE
1794 Instead of emitting them as absolute values in the native word size,
1795 emit the symbol references in the kallsyms table as 32-bit entries,
1796 each containing a relative value in the range [base, base + U32_MAX]
1797 or, when KALLSYMS_ABSOLUTE_PERCPU is in effect, each containing either
1798 an absolute value in the range [0, S32_MAX] or a relative value in the
1799 range [base, base + S32_MAX], where base is the lowest relative symbol
1800 address encountered in the image.
1802 On 64-bit builds, this reduces the size of the address table by 50%,
1803 but more importantly, it results in entries whose values are build
1804 time constants, and no relocation pass is required at runtime to fix
1805 up the entries based on the runtime load address of the kernel.
1807 # end of the "standard kernel features (expert users)" menu
1809 config ARCH_HAS_MEMBARRIER_CALLBACKS
1812 config ARCH_HAS_MEMBARRIER_SYNC_CORE
1815 config HAVE_PERF_EVENTS
1818 See tools/perf/design.txt for details.
1820 config GUEST_PERF_EVENTS
1822 depends on HAVE_PERF_EVENTS
1824 config PERF_USE_VMALLOC
1827 See tools/perf/design.txt for details
1829 menu "Kernel Performance Events And Counters"
1832 bool "Kernel performance events and counters"
1833 default y if PROFILING
1834 depends on HAVE_PERF_EVENTS
1837 Enable kernel support for various performance events provided
1838 by software and hardware.
1840 Software events are supported either built-in or via the
1841 use of generic tracepoints.
1843 Most modern CPUs support performance events via performance
1844 counter registers. These registers count the number of certain
1845 types of hw events: such as instructions executed, cachemisses
1846 suffered, or branches mis-predicted - without slowing down the
1847 kernel or applications. These registers can also trigger interrupts
1848 when a threshold number of events have passed - and can thus be
1849 used to profile the code that runs on that CPU.
1851 The Linux Performance Event subsystem provides an abstraction of
1852 these software and hardware event capabilities, available via a
1853 system call and used by the "perf" utility in tools/perf/. It
1854 provides per task and per CPU counters, and it provides event
1855 capabilities on top of those.
1859 config DEBUG_PERF_USE_VMALLOC
1861 bool "Debug: use vmalloc to back perf mmap() buffers"
1862 depends on PERF_EVENTS && DEBUG_KERNEL && !PPC
1863 select PERF_USE_VMALLOC
1865 Use vmalloc memory to back perf mmap() buffers.
1867 Mostly useful for debugging the vmalloc code on platforms
1868 that don't require it.
1874 config SYSTEM_DATA_VERIFICATION
1876 select SYSTEM_TRUSTED_KEYRING
1880 select ASYMMETRIC_KEY_TYPE
1881 select ASYMMETRIC_PUBLIC_KEY_SUBTYPE
1884 select X509_CERTIFICATE_PARSER
1885 select PKCS7_MESSAGE_PARSER
1887 Provide PKCS#7 message verification using the contents of the system
1888 trusted keyring to provide public keys. This then can be used for
1889 module verification, kexec image verification and firmware blob
1893 bool "Profiling support"
1895 Say Y here to enable the extended profiling support mechanisms used
1900 depends on HAVE_RUST
1901 depends on RUST_IS_AVAILABLE
1902 depends on !MODVERSIONS
1903 depends on !GCC_PLUGINS
1904 depends on !RANDSTRUCT
1905 depends on !DEBUG_INFO_BTF || PAHOLE_HAS_LANG_EXCLUDE
1908 Enables Rust support in the kernel.
1910 This allows other Rust-related options, like drivers written in Rust,
1913 It is also required to be able to load external kernel modules
1916 See Documentation/rust/ for more information.
1920 config RUSTC_VERSION_TEXT
1923 default $(shell,command -v $(RUSTC) >/dev/null 2>&1 && $(RUSTC) --version || echo n)
1925 config BINDGEN_VERSION_TEXT
1928 default $(shell,command -v $(BINDGEN) >/dev/null 2>&1 && $(BINDGEN) --version || echo n)
1931 # Place an empty function call at each tracepoint site. Can be
1932 # dynamically changed for a probe function.
1937 source "kernel/Kconfig.kexec"
1939 endmenu # General setup
1941 source "arch/Kconfig"
1945 default y if PREEMPT_RT
1949 default 0 if BASE_FULL
1950 default 1 if !BASE_FULL
1952 config MODULE_SIG_FORMAT
1954 select SYSTEM_DATA_VERIFICATION
1956 source "kernel/module/Kconfig"
1958 config INIT_ALL_POSSIBLE
1961 Back when each arch used to define their own cpu_online_mask and
1962 cpu_possible_mask, some of them chose to initialize cpu_possible_mask
1963 with all 1s, and others with all 0s. When they were centralised,
1964 it was better to provide this option than to break all the archs
1965 and have several arch maintainers pursuing me down dark alleys.
1967 source "block/Kconfig"
1969 config PREEMPT_NOTIFIERS
1979 Build a simple ASN.1 grammar compiler that produces a bytecode output
1980 that can be interpreted by the ASN.1 stream decoder and used to
1981 inform it as to what tags are to be expected in a stream and what
1982 functions to call on what tags.
1984 source "kernel/Kconfig.locks"
1986 config ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE
1989 config ARCH_HAS_PREPARE_SYNC_CORE_CMD
1992 config ARCH_HAS_SYNC_CORE_BEFORE_USERMODE
1995 # It may be useful for an architecture to override the definitions of the
1996 # SYSCALL_DEFINE() and __SYSCALL_DEFINEx() macros in <linux/syscalls.h>
1997 # and the COMPAT_ variants in <linux/compat.h>, in particular to use a
1998 # different calling convention for syscalls. They can also override the
1999 # macros for not-implemented syscalls in kernel/sys_ni.c and
2000 # kernel/time/posix-stubs.c. All these overrides need to be available in
2001 # <asm/syscall_wrapper.h>.
2002 config ARCH_HAS_SYSCALL_WRAPPER
projects / thirdparty / linux.git / blob