1 # SPDX-License-Identifier: GPL-2.0-only
6 default "/lib/modules/$(shell,uname -r)/.config"
7 default "/etc/kernel-config"
8 default "/boot/config-$(shell,uname -r)"
10 default "arch/$(ARCH)/defconfig"
13 def_bool $(success,$(CC) --version | head -n 1 | grep -q gcc)
17 default $(shell,$(srctree)/scripts/gcc-version.sh $(CC)) if CC_IS_GCC
21 def_bool $(success,$(CC) --version | head -n 1 | grep -q clang)
25 default $(shell,$(srctree)/scripts/clang-version.sh $(CC))
28 def_bool $(success,$(srctree)/scripts/cc-can-link.sh $(CC))
30 config CC_HAS_ASM_GOTO
31 def_bool $(success,$(srctree)/scripts/gcc-goto.sh $(CC))
33 config TOOLS_SUPPORT_RELR
34 def_bool $(success,env "CC=$(CC)" "LD=$(LD)" "NM=$(NM)" "OBJCOPY=$(OBJCOPY)" $(srctree)/scripts/tools-support-relr.sh)
36 config CC_HAS_ASM_INLINE
37 def_bool $(success,echo 'void foo(void) { asm inline (""); }' | $(CC) -x c - -c -o /dev/null)
39 config CC_HAS_WARN_MAYBE_UNINITIALIZED
40 def_bool $(cc-option,-Wmaybe-uninitialized)
42 GCC >= 4.7 supports this option.
44 config CC_DISABLE_WARN_MAYBE_UNINITIALIZED
46 depends on CC_HAS_WARN_MAYBE_UNINITIALIZED
47 default CC_IS_GCC && GCC_VERSION < 40900 # unreliable for GCC < 4.9
49 GCC's -Wmaybe-uninitialized is not reliable by definition.
50 Lots of false positive warnings are produced in some cases.
52 If this option is enabled, -Wno-maybe-uninitialzed is passed
53 to the compiler to suppress maybe-uninitialized warnings.
61 config BUILDTIME_EXTABLE_SORT
64 config THREAD_INFO_IN_TASK
67 Select this to move thread_info off the stack into task_struct. To
68 make this work, an arch will need to remove all thread_info fields
69 except flags and fix any runtime bugs.
71 One subtle change that will be needed is to use try_get_task_stack()
72 and put_task_stack() in save_thread_stack_tsk() and get_wchan().
81 depends on BROKEN || !SMP
84 config INIT_ENV_ARG_LIMIT
89 Maximum of each of the number of arguments and environment
90 variables passed to init from the kernel command line.
93 bool "Compile also drivers which will not load"
97 Some drivers can be compiled on a different platform than they are
98 intended to be run on. Despite they cannot be loaded there (or even
99 when they load they cannot be used due to missing HW support),
100 developers still, opposing to distributors, might want to build such
101 drivers to compile-test them.
103 If you are a developer and want to build everything available, say Y
104 here. If you are a user/distributor, say N here to exclude useless
105 drivers to be distributed.
108 bool "Compile test headers that should be standalone compilable"
110 Compile test headers listed in header-test-y target to ensure they are
111 self-contained, i.e. compilable as standalone units.
113 If you are a developer or tester and want to ensure the requested
114 headers are self-contained, say Y here. Otherwise, choose N.
116 config KERNEL_HEADER_TEST
117 bool "Compile test kernel headers"
118 depends on HEADER_TEST
120 Headers in include/ are used to build external moduls.
121 Compile test them to ensure they are self-contained, i.e.
122 compilable as standalone units.
124 If you are a developer or tester and want to ensure the headers
125 in include/ are self-contained, say Y here. Otherwise, choose N.
127 config UAPI_HEADER_TEST
128 bool "Compile test UAPI headers"
129 depends on HEADER_TEST && HEADERS_INSTALL && CC_CAN_LINK
131 Compile test headers exported to user-space to ensure they are
132 self-contained, i.e. compilable as standalone units.
134 If you are a developer or tester and want to ensure the exported
135 headers are self-contained, say Y here. Otherwise, choose N.
138 string "Local version - append to kernel release"
140 Append an extra string to the end of your kernel version.
141 This will show up when you type uname, for example.
142 The string you set here will be appended after the contents of
143 any files with a filename matching localversion* in your
144 object and source tree, in that order. Your total string can
145 be a maximum of 64 characters.
147 config LOCALVERSION_AUTO
148 bool "Automatically append version information to the version string"
150 depends on !COMPILE_TEST
152 This will try to automatically determine if the current tree is a
153 release tree by looking for git tags that belong to the current
154 top of tree revision.
156 A string of the format -gxxxxxxxx will be added to the localversion
157 if a git-based tree is found. The string generated by this will be
158 appended after any matching localversion* files, and after the value
159 set in CONFIG_LOCALVERSION.
161 (The actual string used here is the first eight characters produced
162 by running the command:
164 $ git rev-parse --verify HEAD
166 which is done within the script "scripts/setlocalversion".)
169 string "Build ID Salt"
172 The build ID is used to link binaries and their debug info. Setting
173 this option will use the value in the calculation of the build id.
174 This is mostly useful for distributions which want to ensure the
175 build is unique between builds. It's safe to leave the default.
177 config HAVE_KERNEL_GZIP
180 config HAVE_KERNEL_BZIP2
183 config HAVE_KERNEL_LZMA
186 config HAVE_KERNEL_XZ
189 config HAVE_KERNEL_LZO
192 config HAVE_KERNEL_LZ4
195 config HAVE_KERNEL_UNCOMPRESSED
199 prompt "Kernel compression mode"
201 depends on HAVE_KERNEL_GZIP || HAVE_KERNEL_BZIP2 || HAVE_KERNEL_LZMA || HAVE_KERNEL_XZ || HAVE_KERNEL_LZO || HAVE_KERNEL_LZ4 || HAVE_KERNEL_UNCOMPRESSED
203 The linux kernel is a kind of self-extracting executable.
204 Several compression algorithms are available, which differ
205 in efficiency, compression and decompression speed.
206 Compression speed is only relevant when building a kernel.
207 Decompression speed is relevant at each boot.
209 If you have any problems with bzip2 or lzma compressed
210 kernels, mail me (Alain Knaff) <alain@knaff.lu>. (An older
211 version of this functionality (bzip2 only), for 2.4, was
212 supplied by Christian Ludwig)
214 High compression options are mostly useful for users, who
215 are low on disk space (embedded systems), but for whom ram
218 If in doubt, select 'gzip'
222 depends on HAVE_KERNEL_GZIP
224 The old and tried gzip compression. It provides a good balance
225 between compression ratio and decompression speed.
229 depends on HAVE_KERNEL_BZIP2
231 Its compression ratio and speed is intermediate.
232 Decompression speed is slowest among the choices. The kernel
233 size is about 10% smaller with bzip2, in comparison to gzip.
234 Bzip2 uses a large amount of memory. For modern kernels you
235 will need at least 8MB RAM or more for booting.
239 depends on HAVE_KERNEL_LZMA
241 This compression algorithm's ratio is best. Decompression speed
242 is between gzip and bzip2. Compression is slowest.
243 The kernel size is about 33% smaller with LZMA in comparison to gzip.
247 depends on HAVE_KERNEL_XZ
249 XZ uses the LZMA2 algorithm and instruction set specific
250 BCJ filters which can improve compression ratio of executable
251 code. The size of the kernel is about 30% smaller with XZ in
252 comparison to gzip. On architectures for which there is a BCJ
253 filter (i386, x86_64, ARM, IA-64, PowerPC, and SPARC), XZ
254 will create a few percent smaller kernel than plain LZMA.
256 The speed is about the same as with LZMA: The decompression
257 speed of XZ is better than that of bzip2 but worse than gzip
258 and LZO. Compression is slow.
262 depends on HAVE_KERNEL_LZO
264 Its compression ratio is the poorest among the choices. The kernel
265 size is about 10% bigger than gzip; however its speed
266 (both compression and decompression) is the fastest.
270 depends on HAVE_KERNEL_LZ4
272 LZ4 is an LZ77-type compressor with a fixed, byte-oriented encoding.
273 A preliminary version of LZ4 de/compression tool is available at
274 <https://code.google.com/p/lz4/>.
276 Its compression ratio is worse than LZO. The size of the kernel
277 is about 8% bigger than LZO. But the decompression speed is
280 config KERNEL_UNCOMPRESSED
282 depends on HAVE_KERNEL_UNCOMPRESSED
284 Produce uncompressed kernel image. This option is usually not what
285 you want. It is useful for debugging the kernel in slow simulation
286 environments, where decompressing and moving the kernel is awfully
287 slow. This option allows early boot code to skip the decompressor
288 and jump right at uncompressed kernel image.
292 config DEFAULT_HOSTNAME
293 string "Default hostname"
296 This option determines the default system hostname before userspace
297 calls sethostname(2). The kernel traditionally uses "(none)" here,
298 but you may wish to use a different default here to make a minimal
299 system more usable with less configuration.
302 # For some reason microblaze and nios2 hard code SWAP=n. Hopefully we can
303 # add proper SWAP support to them, in which case this can be remove.
309 bool "Support for paging of anonymous memory (swap)"
310 depends on MMU && BLOCK && !ARCH_NO_SWAP
313 This option allows you to choose whether you want to have support
314 for so called swap devices or swap files in your kernel that are
315 used to provide more virtual memory than the actual RAM present
316 in your computer. If unsure say Y.
321 Inter Process Communication is a suite of library functions and
322 system calls which let processes (running programs) synchronize and
323 exchange information. It is generally considered to be a good thing,
324 and some programs won't run unless you say Y here. In particular, if
325 you want to run the DOS emulator dosemu under Linux (read the
326 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
327 you'll need to say Y here.
329 You can find documentation about IPC with "info ipc" and also in
330 section 6.4 of the Linux Programmer's Guide, available from
331 <http://www.tldp.org/guides.html>.
333 config SYSVIPC_SYSCTL
340 bool "POSIX Message Queues"
343 POSIX variant of message queues is a part of IPC. In POSIX message
344 queues every message has a priority which decides about succession
345 of receiving it by a process. If you want to compile and run
346 programs written e.g. for Solaris with use of its POSIX message
347 queues (functions mq_*) say Y here.
349 POSIX message queues are visible as a filesystem called 'mqueue'
350 and can be mounted somewhere if you want to do filesystem
351 operations on message queues.
355 config POSIX_MQUEUE_SYSCTL
357 depends on POSIX_MQUEUE
361 config CROSS_MEMORY_ATTACH
362 bool "Enable process_vm_readv/writev syscalls"
366 Enabling this option adds the system calls process_vm_readv and
367 process_vm_writev which allow a process with the correct privileges
368 to directly read from or write to another process' address space.
369 See the man page for more details.
372 bool "uselib syscall"
373 def_bool ALPHA || M68K || SPARC || X86_32 || IA32_EMULATION
375 This option enables the uselib syscall, a system call used in the
376 dynamic linker from libc5 and earlier. glibc does not use this
377 system call. If you intend to run programs built on libc5 or
378 earlier, you may need to enable this syscall. Current systems
379 running glibc can safely disable this.
382 bool "Auditing support"
385 Enable auditing infrastructure that can be used with another
386 kernel subsystem, such as SELinux (which requires this for
387 logging of avc messages output). System call auditing is included
388 on architectures which support it.
390 config HAVE_ARCH_AUDITSYSCALL
395 depends on AUDIT && HAVE_ARCH_AUDITSYSCALL
398 source "kernel/irq/Kconfig"
399 source "kernel/time/Kconfig"
400 source "kernel/Kconfig.preempt"
402 menu "CPU/Task time and stats accounting"
404 config VIRT_CPU_ACCOUNTING
408 prompt "Cputime accounting"
409 default TICK_CPU_ACCOUNTING if !PPC64
410 default VIRT_CPU_ACCOUNTING_NATIVE if PPC64
412 # Kind of a stub config for the pure tick based cputime accounting
413 config TICK_CPU_ACCOUNTING
414 bool "Simple tick based cputime accounting"
415 depends on !S390 && !NO_HZ_FULL
417 This is the basic tick based cputime accounting that maintains
418 statistics about user, system and idle time spent on per jiffies
423 config VIRT_CPU_ACCOUNTING_NATIVE
424 bool "Deterministic task and CPU time accounting"
425 depends on HAVE_VIRT_CPU_ACCOUNTING && !NO_HZ_FULL
426 select VIRT_CPU_ACCOUNTING
428 Select this option to enable more accurate task and CPU time
429 accounting. This is done by reading a CPU counter on each
430 kernel entry and exit and on transitions within the kernel
431 between system, softirq and hardirq state, so there is a
432 small performance impact. In the case of s390 or IBM POWER > 5,
433 this also enables accounting of stolen time on logically-partitioned
436 config VIRT_CPU_ACCOUNTING_GEN
437 bool "Full dynticks CPU time accounting"
438 depends on HAVE_CONTEXT_TRACKING
439 depends on HAVE_VIRT_CPU_ACCOUNTING_GEN
440 depends on GENERIC_CLOCKEVENTS
441 select VIRT_CPU_ACCOUNTING
442 select CONTEXT_TRACKING
444 Select this option to enable task and CPU time accounting on full
445 dynticks systems. This accounting is implemented by watching every
446 kernel-user boundaries using the context tracking subsystem.
447 The accounting is thus performed at the expense of some significant
450 For now this is only useful if you are working on the full
451 dynticks subsystem development.
457 config IRQ_TIME_ACCOUNTING
458 bool "Fine granularity task level IRQ time accounting"
459 depends on HAVE_IRQ_TIME_ACCOUNTING && !VIRT_CPU_ACCOUNTING_NATIVE
461 Select this option to enable fine granularity task irq time
462 accounting. This is done by reading a timestamp on each
463 transitions between softirq and hardirq state, so there can be a
464 small performance impact.
466 If in doubt, say N here.
468 config HAVE_SCHED_AVG_IRQ
470 depends on IRQ_TIME_ACCOUNTING || PARAVIRT_TIME_ACCOUNTING
473 config BSD_PROCESS_ACCT
474 bool "BSD Process Accounting"
477 If you say Y here, a user level program will be able to instruct the
478 kernel (via a special system call) to write process accounting
479 information to a file: whenever a process exits, information about
480 that process will be appended to the file by the kernel. The
481 information includes things such as creation time, owning user,
482 command name, memory usage, controlling terminal etc. (the complete
483 list is in the struct acct in <file:include/linux/acct.h>). It is
484 up to the user level program to do useful things with this
485 information. This is generally a good idea, so say Y.
487 config BSD_PROCESS_ACCT_V3
488 bool "BSD Process Accounting version 3 file format"
489 depends on BSD_PROCESS_ACCT
492 If you say Y here, the process accounting information is written
493 in a new file format that also logs the process IDs of each
494 process and its parent. Note that this file format is incompatible
495 with previous v0/v1/v2 file formats, so you will need updated tools
496 for processing it. A preliminary version of these tools is available
497 at <http://www.gnu.org/software/acct/>.
500 bool "Export task/process statistics through netlink"
505 Export selected statistics for tasks/processes through the
506 generic netlink interface. Unlike BSD process accounting, the
507 statistics are available during the lifetime of tasks/processes as
508 responses to commands. Like BSD accounting, they are sent to user
513 config TASK_DELAY_ACCT
514 bool "Enable per-task delay accounting"
518 Collect information on time spent by a task waiting for system
519 resources like cpu, synchronous block I/O completion and swapping
520 in pages. Such statistics can help in setting a task's priorities
521 relative to other tasks for cpu, io, rss limits etc.
526 bool "Enable extended accounting over taskstats"
529 Collect extended task accounting data and send the data
530 to userland for processing over the taskstats interface.
534 config TASK_IO_ACCOUNTING
535 bool "Enable per-task storage I/O accounting"
536 depends on TASK_XACCT
538 Collect information on the number of bytes of storage I/O which this
544 bool "Pressure stall information tracking"
546 Collect metrics that indicate how overcommitted the CPU, memory,
547 and IO capacity are in the system.
549 If you say Y here, the kernel will create /proc/pressure/ with the
550 pressure statistics files cpu, memory, and io. These will indicate
551 the share of walltime in which some or all tasks in the system are
552 delayed due to contention of the respective resource.
554 In kernels with cgroup support, cgroups (cgroup2 only) will
555 have cpu.pressure, memory.pressure, and io.pressure files,
556 which aggregate pressure stalls for the grouped tasks only.
558 For more details see Documentation/accounting/psi.rst.
562 config PSI_DEFAULT_DISABLED
563 bool "Require boot parameter to enable pressure stall information tracking"
567 If set, pressure stall information tracking will be disabled
568 per default but can be enabled through passing psi=1 on the
569 kernel commandline during boot.
571 This feature adds some code to the task wakeup and sleep
572 paths of the scheduler. The overhead is too low to affect
573 common scheduling-intense workloads in practice (such as
574 webservers, memcache), but it does show up in artificial
575 scheduler stress tests, such as hackbench.
577 If you are paranoid and not sure what the kernel will be
582 endmenu # "CPU/Task time and stats accounting"
586 depends on SMP || COMPILE_TEST
589 Make sure that CPUs running critical tasks are not disturbed by
590 any source of "noise" such as unbound workqueues, timers, kthreads...
591 Unbound jobs get offloaded to housekeeping CPUs. This is driven by
592 the "isolcpus=" boot parameter.
596 source "kernel/rcu/Kconfig"
603 tristate "Kernel .config support"
605 This option enables the complete Linux kernel ".config" file
606 contents to be saved in the kernel. It provides documentation
607 of which kernel options are used in a running kernel or in an
608 on-disk kernel. This information can be extracted from the kernel
609 image file with the script scripts/extract-ikconfig and used as
610 input to rebuild the current kernel or to build another kernel.
611 It can also be extracted from a running kernel by reading
612 /proc/config.gz if enabled (below).
615 bool "Enable access to .config through /proc/config.gz"
616 depends on IKCONFIG && PROC_FS
618 This option enables access to the kernel configuration file
619 through /proc/config.gz.
622 tristate "Enable kernel headers through /sys/kernel/kheaders.tar.xz"
625 This option enables access to the in-kernel headers that are generated during
626 the build process. These can be used to build eBPF tracing programs,
627 or similar programs. If you build the headers as a module, a module called
628 kheaders.ko is built which can be loaded on-demand to get access to headers.
631 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
636 Select the minimal kernel log buffer size as a power of 2.
637 The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
638 parameter, see below. Any higher size also might be forced
639 by "log_buf_len" boot parameter.
649 config LOG_CPU_MAX_BUF_SHIFT
650 int "CPU kernel log buffer size contribution (13 => 8 KB, 17 => 128KB)"
653 default 12 if !BASE_SMALL
654 default 0 if BASE_SMALL
657 This option allows to increase the default ring buffer size
658 according to the number of CPUs. The value defines the contribution
659 of each CPU as a power of 2. The used space is typically only few
660 lines however it might be much more when problems are reported,
663 The increased size means that a new buffer has to be allocated and
664 the original static one is unused. It makes sense only on systems
665 with more CPUs. Therefore this value is used only when the sum of
666 contributions is greater than the half of the default kernel ring
667 buffer as defined by LOG_BUF_SHIFT. The default values are set
668 so that more than 64 CPUs are needed to trigger the allocation.
670 Also this option is ignored when "log_buf_len" kernel parameter is
671 used as it forces an exact (power of two) size of the ring buffer.
673 The number of possible CPUs is used for this computation ignoring
674 hotplugging making the computation optimal for the worst case
675 scenario while allowing a simple algorithm to be used from bootup.
677 Examples shift values and their meaning:
678 17 => 128 KB for each CPU
679 16 => 64 KB for each CPU
680 15 => 32 KB for each CPU
681 14 => 16 KB for each CPU
682 13 => 8 KB for each CPU
683 12 => 4 KB for each CPU
685 config PRINTK_SAFE_LOG_BUF_SHIFT
686 int "Temporary per-CPU printk log buffer size (12 => 4KB, 13 => 8KB)"
691 Select the size of an alternate printk per-CPU buffer where messages
692 printed from usafe contexts are temporary stored. One example would
693 be NMI messages, another one - printk recursion. The messages are
694 copied to the main log buffer in a safe context to avoid a deadlock.
695 The value defines the size as a power of 2.
697 Those messages are rare and limited. The largest one is when
698 a backtrace is printed. It usually fits into 4KB. Select
699 8KB if you want to be on the safe side.
702 17 => 128 KB for each CPU
703 16 => 64 KB for each CPU
704 15 => 32 KB for each CPU
705 14 => 16 KB for each CPU
706 13 => 8 KB for each CPU
707 12 => 4 KB for each CPU
710 # Architectures with an unreliable sched_clock() should select this:
712 config HAVE_UNSTABLE_SCHED_CLOCK
715 config GENERIC_SCHED_CLOCK
718 menu "Scheduler features"
721 bool "Enable utilization clamping for RT/FAIR tasks"
722 depends on CPU_FREQ_GOV_SCHEDUTIL
724 This feature enables the scheduler to track the clamped utilization
725 of each CPU based on RUNNABLE tasks scheduled on that CPU.
727 With this option, the user can specify the min and max CPU
728 utilization allowed for RUNNABLE tasks. The max utilization defines
729 the maximum frequency a task should use while the min utilization
730 defines the minimum frequency it should use.
732 Both min and max utilization clamp values are hints to the scheduler,
733 aiming at improving its frequency selection policy, but they do not
734 enforce or grant any specific bandwidth for tasks.
738 config UCLAMP_BUCKETS_COUNT
739 int "Number of supported utilization clamp buckets"
742 depends on UCLAMP_TASK
744 Defines the number of clamp buckets to use. The range of each bucket
745 will be SCHED_CAPACITY_SCALE/UCLAMP_BUCKETS_COUNT. The higher the
746 number of clamp buckets the finer their granularity and the higher
747 the precision of clamping aggregation and tracking at run-time.
749 For example, with the minimum configuration value we will have 5
750 clamp buckets tracking 20% utilization each. A 25% boosted tasks will
751 be refcounted in the [20..39]% bucket and will set the bucket clamp
752 effective value to 25%.
753 If a second 30% boosted task should be co-scheduled on the same CPU,
754 that task will be refcounted in the same bucket of the first task and
755 it will boost the bucket clamp effective value to 30%.
756 The clamp effective value of a bucket is reset to its nominal value
757 (20% in the example above) when there are no more tasks refcounted in
760 An additional boost/capping margin can be added to some tasks. In the
761 example above the 25% task will be boosted to 30% until it exits the
762 CPU. If that should be considered not acceptable on certain systems,
763 it's always possible to reduce the margin by increasing the number of
764 clamp buckets to trade off used memory for run-time tracking
767 If in doubt, use the default value.
772 # For architectures that want to enable the support for NUMA-affine scheduler
775 config ARCH_SUPPORTS_NUMA_BALANCING
779 # For architectures that prefer to flush all TLBs after a number of pages
780 # are unmapped instead of sending one IPI per page to flush. The architecture
781 # must provide guarantees on what happens if a clean TLB cache entry is
782 # written after the unmap. Details are in mm/rmap.c near the check for
783 # should_defer_flush. The architecture should also consider if the full flush
784 # and the refill costs are offset by the savings of sending fewer IPIs.
785 config ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH
789 # For architectures that know their GCC __int128 support is sound
791 config ARCH_SUPPORTS_INT128
794 # For architectures that (ab)use NUMA to represent different memory regions
795 # all cpu-local but of different latencies, such as SuperH.
797 config ARCH_WANT_NUMA_VARIABLE_LOCALITY
800 config NUMA_BALANCING
801 bool "Memory placement aware NUMA scheduler"
802 depends on ARCH_SUPPORTS_NUMA_BALANCING
803 depends on !ARCH_WANT_NUMA_VARIABLE_LOCALITY
804 depends on SMP && NUMA && MIGRATION
806 This option adds support for automatic NUMA aware memory/task placement.
807 The mechanism is quite primitive and is based on migrating memory when
808 it has references to the node the task is running on.
810 This system will be inactive on UMA systems.
812 config NUMA_BALANCING_DEFAULT_ENABLED
813 bool "Automatically enable NUMA aware memory/task placement"
815 depends on NUMA_BALANCING
817 If set, automatic NUMA balancing will be enabled if running on a NUMA
821 bool "Control Group support"
824 This option adds support for grouping sets of processes together, for
825 use with process control subsystems such as Cpusets, CFS, memory
826 controls or device isolation.
828 - Documentation/scheduler/sched-design-CFS.rst (CFS)
829 - Documentation/admin-guide/cgroup-v1/ (features for grouping, isolation
830 and resource control)
840 bool "Memory controller"
844 Provides control over the memory footprint of tasks in a cgroup.
847 bool "Swap controller"
848 depends on MEMCG && SWAP
850 Provides control over the swap space consumed by tasks in a cgroup.
852 config MEMCG_SWAP_ENABLED
853 bool "Swap controller enabled by default"
854 depends on MEMCG_SWAP
857 Memory Resource Controller Swap Extension comes with its price in
858 a bigger memory consumption. General purpose distribution kernels
859 which want to enable the feature but keep it disabled by default
860 and let the user enable it by swapaccount=1 boot command line
861 parameter should have this option unselected.
862 For those who want to have the feature enabled by default should
863 select this option (if, for some reason, they need to disable it
864 then swapaccount=0 does the trick).
868 depends on MEMCG && !SLOB
876 Generic block IO controller cgroup interface. This is the common
877 cgroup interface which should be used by various IO controlling
880 Currently, CFQ IO scheduler uses it to recognize task groups and
881 control disk bandwidth allocation (proportional time slice allocation)
882 to such task groups. It is also used by bio throttling logic in
883 block layer to implement upper limit in IO rates on a device.
885 This option only enables generic Block IO controller infrastructure.
886 One needs to also enable actual IO controlling logic/policy. For
887 enabling proportional weight division of disk bandwidth in CFQ, set
888 CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
889 CONFIG_BLK_DEV_THROTTLING=y.
891 See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information.
893 config CGROUP_WRITEBACK
895 depends on MEMCG && BLK_CGROUP
898 menuconfig CGROUP_SCHED
899 bool "CPU controller"
902 This feature lets CPU scheduler recognize task groups and control CPU
903 bandwidth allocation to such task groups. It uses cgroups to group
907 config FAIR_GROUP_SCHED
908 bool "Group scheduling for SCHED_OTHER"
909 depends on CGROUP_SCHED
913 bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED"
914 depends on FAIR_GROUP_SCHED
917 This option allows users to define CPU bandwidth rates (limits) for
918 tasks running within the fair group scheduler. Groups with no limit
919 set are considered to be unconstrained and will run with no
921 See Documentation/scheduler/sched-bwc.rst for more information.
923 config RT_GROUP_SCHED
924 bool "Group scheduling for SCHED_RR/FIFO"
925 depends on CGROUP_SCHED
928 This feature lets you explicitly allocate real CPU bandwidth
929 to task groups. If enabled, it will also make it impossible to
930 schedule realtime tasks for non-root users until you allocate
931 realtime bandwidth for them.
932 See Documentation/scheduler/sched-rt-group.rst for more information.
936 config UCLAMP_TASK_GROUP
937 bool "Utilization clamping per group of tasks"
938 depends on CGROUP_SCHED
939 depends on UCLAMP_TASK
942 This feature enables the scheduler to track the clamped utilization
943 of each CPU based on RUNNABLE tasks currently scheduled on that CPU.
945 When this option is enabled, the user can specify a min and max
946 CPU bandwidth which is allowed for each single task in a group.
947 The max bandwidth allows to clamp the maximum frequency a task
948 can use, while the min bandwidth allows to define a minimum
949 frequency a task will always use.
951 When task group based utilization clamping is enabled, an eventually
952 specified task-specific clamp value is constrained by the cgroup
953 specified clamp value. Both minimum and maximum task clamping cannot
954 be bigger than the corresponding clamping defined at task group level.
959 bool "PIDs controller"
961 Provides enforcement of process number limits in the scope of a
962 cgroup. Any attempt to fork more processes than is allowed in the
963 cgroup will fail. PIDs are fundamentally a global resource because it
964 is fairly trivial to reach PID exhaustion before you reach even a
965 conservative kmemcg limit. As a result, it is possible to grind a
966 system to halt without being limited by other cgroup policies. The
967 PIDs controller is designed to stop this from happening.
969 It should be noted that organisational operations (such as attaching
970 to a cgroup hierarchy) will *not* be blocked by the PIDs controller,
971 since the PIDs limit only affects a process's ability to fork, not to
975 bool "RDMA controller"
977 Provides enforcement of RDMA resources defined by IB stack.
978 It is fairly easy for consumers to exhaust RDMA resources, which
979 can result into resource unavailability to other consumers.
980 RDMA controller is designed to stop this from happening.
981 Attaching processes with active RDMA resources to the cgroup
982 hierarchy is allowed even if can cross the hierarchy's limit.
984 config CGROUP_FREEZER
985 bool "Freezer controller"
987 Provides a way to freeze and unfreeze all tasks in a
990 This option affects the ORIGINAL cgroup interface. The cgroup2 memory
991 controller includes important in-kernel memory consumers per default.
993 If you're using cgroup2, say N.
995 config CGROUP_HUGETLB
996 bool "HugeTLB controller"
997 depends on HUGETLB_PAGE
1001 Provides a cgroup controller for HugeTLB pages.
1002 When you enable this, you can put a per cgroup limit on HugeTLB usage.
1003 The limit is enforced during page fault. Since HugeTLB doesn't
1004 support page reclaim, enforcing the limit at page fault time implies
1005 that, the application will get SIGBUS signal if it tries to access
1006 HugeTLB pages beyond its limit. This requires the application to know
1007 beforehand how much HugeTLB pages it would require for its use. The
1008 control group is tracked in the third page lru pointer. This means
1009 that we cannot use the controller with huge page less than 3 pages.
1012 bool "Cpuset controller"
1015 This option will let you create and manage CPUSETs which
1016 allow dynamically partitioning a system into sets of CPUs and
1017 Memory Nodes and assigning tasks to run only within those sets.
1018 This is primarily useful on large SMP or NUMA systems.
1022 config PROC_PID_CPUSET
1023 bool "Include legacy /proc/<pid>/cpuset file"
1027 config CGROUP_DEVICE
1028 bool "Device controller"
1030 Provides a cgroup controller implementing whitelists for
1031 devices which a process in the cgroup can mknod or open.
1033 config CGROUP_CPUACCT
1034 bool "Simple CPU accounting controller"
1036 Provides a simple controller for monitoring the
1037 total CPU consumed by the tasks in a cgroup.
1040 bool "Perf controller"
1041 depends on PERF_EVENTS
1043 This option extends the perf per-cpu mode to restrict monitoring
1044 to threads which belong to the cgroup specified and run on the
1050 bool "Support for eBPF programs attached to cgroups"
1051 depends on BPF_SYSCALL
1052 select SOCK_CGROUP_DATA
1054 Allow attaching eBPF programs to a cgroup using the bpf(2)
1055 syscall command BPF_PROG_ATTACH.
1057 In which context these programs are accessed depends on the type
1058 of attachment. For instance, programs that are attached using
1059 BPF_CGROUP_INET_INGRESS will be executed on the ingress path of
1063 bool "Debug controller"
1065 depends on DEBUG_KERNEL
1067 This option enables a simple controller that exports
1068 debugging information about the cgroups framework. This
1069 controller is for control cgroup debugging only. Its
1070 interfaces are not stable.
1074 config SOCK_CGROUP_DATA
1080 menuconfig NAMESPACES
1081 bool "Namespaces support" if EXPERT
1082 depends on MULTIUSER
1085 Provides the way to make tasks work with different objects using
1086 the same id. For example same IPC id may refer to different objects
1087 or same user id or pid may refer to different tasks when used in
1088 different namespaces.
1093 bool "UTS namespace"
1096 In this namespace tasks see different info provided with the
1100 bool "IPC namespace"
1101 depends on (SYSVIPC || POSIX_MQUEUE)
1104 In this namespace tasks work with IPC ids which correspond to
1105 different IPC objects in different namespaces.
1108 bool "User namespace"
1111 This allows containers, i.e. vservers, to use user namespaces
1112 to provide different user info for different servers.
1114 When user namespaces are enabled in the kernel it is
1115 recommended that the MEMCG option also be enabled and that
1116 user-space use the memory control groups to limit the amount
1117 of memory a memory unprivileged users can use.
1122 bool "PID Namespaces"
1125 Support process id namespaces. This allows having multiple
1126 processes with the same pid as long as they are in different
1127 pid namespaces. This is a building block of containers.
1130 bool "Network namespace"
1134 Allow user space to create what appear to be multiple instances
1135 of the network stack.
1139 config CHECKPOINT_RESTORE
1140 bool "Checkpoint/restore support"
1141 select PROC_CHILDREN
1144 Enables additional kernel features in a sake of checkpoint/restore.
1145 In particular it adds auxiliary prctl codes to setup process text,
1146 data and heap segment sizes, and a few additional /proc filesystem
1149 If unsure, say N here.
1151 config SCHED_AUTOGROUP
1152 bool "Automatic process group scheduling"
1155 select FAIR_GROUP_SCHED
1157 This option optimizes the scheduler for common desktop workloads by
1158 automatically creating and populating task groups. This separation
1159 of workloads isolates aggressive CPU burners (like build jobs) from
1160 desktop applications. Task group autogeneration is currently based
1163 config SYSFS_DEPRECATED
1164 bool "Enable deprecated sysfs features to support old userspace tools"
1168 This option adds code that switches the layout of the "block" class
1169 devices, to not show up in /sys/class/block/, but only in
1172 This switch is only active when the sysfs.deprecated=1 boot option is
1173 passed or the SYSFS_DEPRECATED_V2 option is set.
1175 This option allows new kernels to run on old distributions and tools,
1176 which might get confused by /sys/class/block/. Since 2007/2008 all
1177 major distributions and tools handle this just fine.
1179 Recent distributions and userspace tools after 2009/2010 depend on
1180 the existence of /sys/class/block/, and will not work with this
1183 Only if you are using a new kernel on an old distribution, you might
1186 config SYSFS_DEPRECATED_V2
1187 bool "Enable deprecated sysfs features by default"
1190 depends on SYSFS_DEPRECATED
1192 Enable deprecated sysfs by default.
1194 See the CONFIG_SYSFS_DEPRECATED option for more details about this
1197 Only if you are using a new kernel on an old distribution, you might
1198 need to say Y here. Even then, odds are you would not need it
1199 enabled, you can always pass the boot option if absolutely necessary.
1202 bool "Kernel->user space relay support (formerly relayfs)"
1205 This option enables support for relay interface support in
1206 certain file systems (such as debugfs).
1207 It is designed to provide an efficient mechanism for tools and
1208 facilities to relay large amounts of data from kernel space to
1213 config BLK_DEV_INITRD
1214 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
1216 The initial RAM filesystem is a ramfs which is loaded by the
1217 boot loader (loadlin or lilo) and that is mounted as root
1218 before the normal boot procedure. It is typically used to
1219 load modules needed to mount the "real" root file system,
1220 etc. See <file:Documentation/admin-guide/initrd.rst> for details.
1222 If RAM disk support (BLK_DEV_RAM) is also included, this
1223 also enables initial RAM disk (initrd) support and adds
1224 15 Kbytes (more on some other architectures) to the kernel size.
1230 source "usr/Kconfig"
1235 prompt "Compiler optimization level"
1236 default CC_OPTIMIZE_FOR_PERFORMANCE
1238 config CC_OPTIMIZE_FOR_PERFORMANCE
1239 bool "Optimize for performance (-O2)"
1241 This is the default optimization level for the kernel, building
1242 with the "-O2" compiler flag for best performance and most
1243 helpful compile-time warnings.
1245 config CC_OPTIMIZE_FOR_PERFORMANCE_O3
1246 bool "Optimize more for performance (-O3)"
1248 imply CC_DISABLE_WARN_MAYBE_UNINITIALIZED # avoid false positives
1250 Choosing this option will pass "-O3" to your compiler to optimize
1251 the kernel yet more for performance.
1253 config CC_OPTIMIZE_FOR_SIZE
1254 bool "Optimize for size (-Os)"
1255 imply CC_DISABLE_WARN_MAYBE_UNINITIALIZED # avoid false positives
1257 Choosing this option will pass "-Os" to your compiler resulting
1258 in a smaller kernel.
1262 config HAVE_LD_DEAD_CODE_DATA_ELIMINATION
1265 This requires that the arch annotates or otherwise protects
1266 its external entry points from being discarded. Linker scripts
1267 must also merge .text.*, .data.*, and .bss.* correctly into
1268 output sections. Care must be taken not to pull in unrelated
1269 sections (e.g., '.text.init'). Typically '.' in section names
1270 is used to distinguish them from label names / C identifiers.
1272 config LD_DEAD_CODE_DATA_ELIMINATION
1273 bool "Dead code and data elimination (EXPERIMENTAL)"
1274 depends on HAVE_LD_DEAD_CODE_DATA_ELIMINATION
1276 depends on !(FUNCTION_TRACER && CC_IS_GCC && GCC_VERSION < 40800)
1277 depends on $(cc-option,-ffunction-sections -fdata-sections)
1278 depends on $(ld-option,--gc-sections)
1280 Enable this if you want to do dead code and data elimination with
1281 the linker by compiling with -ffunction-sections -fdata-sections,
1282 and linking with --gc-sections.
1284 This can reduce on disk and in-memory size of the kernel
1285 code and static data, particularly for small configs and
1286 on small systems. This has the possibility of introducing
1287 silently broken kernel if the required annotations are not
1288 present. This option is not well tested yet, so use at your
1297 config SYSCTL_EXCEPTION_TRACE
1300 Enable support for /proc/sys/debug/exception-trace.
1302 config SYSCTL_ARCH_UNALIGN_NO_WARN
1305 Enable support for /proc/sys/kernel/ignore-unaligned-usertrap
1306 Allows arch to define/use @no_unaligned_warning to possibly warn
1307 about unaligned access emulation going on under the hood.
1309 config SYSCTL_ARCH_UNALIGN_ALLOW
1312 Enable support for /proc/sys/kernel/unaligned-trap
1313 Allows arches to define/use @unaligned_enabled to runtime toggle
1314 the unaligned access emulation.
1315 see arch/parisc/kernel/unaligned.c for reference
1317 config HAVE_PCSPKR_PLATFORM
1320 # interpreter that classic socket filters depend on
1325 bool "Configure standard kernel features (expert users)"
1326 # Unhide debug options, to make the on-by-default options visible
1329 This option allows certain base kernel options and settings
1330 to be disabled or tweaked. This is for specialized
1331 environments which can tolerate a "non-standard" kernel.
1332 Only use this if you really know what you are doing.
1335 bool "Enable 16-bit UID system calls" if EXPERT
1336 depends on HAVE_UID16 && MULTIUSER
1339 This enables the legacy 16-bit UID syscall wrappers.
1342 bool "Multiple users, groups and capabilities support" if EXPERT
1345 This option enables support for non-root users, groups and
1348 If you say N here, all processes will run with UID 0, GID 0, and all
1349 possible capabilities. Saying N here also compiles out support for
1350 system calls related to UIDs, GIDs, and capabilities, such as setuid,
1353 If unsure, say Y here.
1355 config SGETMASK_SYSCALL
1356 bool "sgetmask/ssetmask syscalls support" if EXPERT
1357 def_bool PARISC || M68K || PPC || MIPS || X86 || SPARC || MICROBLAZE || SUPERH
1359 sys_sgetmask and sys_ssetmask are obsolete system calls
1360 no longer supported in libc but still enabled by default in some
1363 If unsure, leave the default option here.
1365 config SYSFS_SYSCALL
1366 bool "Sysfs syscall support" if EXPERT
1369 sys_sysfs is an obsolete system call no longer supported in libc.
1370 Note that disabling this option is more secure but might break
1371 compatibility with some systems.
1373 If unsure say Y here.
1375 config SYSCTL_SYSCALL
1376 bool "Sysctl syscall support" if EXPERT
1377 depends on PROC_SYSCTL
1381 sys_sysctl uses binary paths that have been found challenging
1382 to properly maintain and use. The interface in /proc/sys
1383 using paths with ascii names is now the primary path to this
1386 Almost nothing using the binary sysctl interface so if you are
1387 trying to save some space it is probably safe to disable this,
1388 making your kernel marginally smaller.
1390 If unsure say N here.
1393 bool "open by fhandle syscalls" if EXPERT
1397 If you say Y here, a user level program will be able to map
1398 file names to handle and then later use the handle for
1399 different file system operations. This is useful in implementing
1400 userspace file servers, which now track files using handles instead
1401 of names. The handle would remain the same even if file names
1402 get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2)
1406 bool "Posix Clocks & timers" if EXPERT
1409 This includes native support for POSIX timers to the kernel.
1410 Some embedded systems have no use for them and therefore they
1411 can be configured out to reduce the size of the kernel image.
1413 When this option is disabled, the following syscalls won't be
1414 available: timer_create, timer_gettime: timer_getoverrun,
1415 timer_settime, timer_delete, clock_adjtime, getitimer,
1416 setitimer, alarm. Furthermore, the clock_settime, clock_gettime,
1417 clock_getres and clock_nanosleep syscalls will be limited to
1418 CLOCK_REALTIME, CLOCK_MONOTONIC and CLOCK_BOOTTIME only.
1424 bool "Enable support for printk" if EXPERT
1427 This option enables normal printk support. Removing it
1428 eliminates most of the message strings from the kernel image
1429 and makes the kernel more or less silent. As this makes it
1430 very difficult to diagnose system problems, saying N here is
1431 strongly discouraged.
1439 bool "BUG() support" if EXPERT
1442 Disabling this option eliminates support for BUG and WARN, reducing
1443 the size of your kernel image and potentially quietly ignoring
1444 numerous fatal conditions. You should only consider disabling this
1445 option for embedded systems with no facilities for reporting errors.
1451 bool "Enable ELF core dumps" if EXPERT
1453 Enable support for generating core dumps. Disabling saves about 4k.
1456 config PCSPKR_PLATFORM
1457 bool "Enable PC-Speaker support" if EXPERT
1458 depends on HAVE_PCSPKR_PLATFORM
1462 This option allows to disable the internal PC-Speaker
1463 support, saving some memory.
1467 bool "Enable full-sized data structures for core" if EXPERT
1469 Disabling this option reduces the size of miscellaneous core
1470 kernel data structures. This saves memory on small machines,
1471 but may reduce performance.
1474 bool "Enable futex support" if EXPERT
1478 Disabling this option will cause the kernel to be built without
1479 support for "fast userspace mutexes". The resulting kernel may not
1480 run glibc-based applications correctly.
1484 depends on FUTEX && RT_MUTEXES
1487 config HAVE_FUTEX_CMPXCHG
1491 Architectures should select this if futex_atomic_cmpxchg_inatomic()
1492 is implemented and always working. This removes a couple of runtime
1496 bool "Enable eventpoll support" if EXPERT
1499 Disabling this option will cause the kernel to be built without
1500 support for epoll family of system calls.
1503 bool "Enable signalfd() system call" if EXPERT
1506 Enable the signalfd() system call that allows to receive signals
1507 on a file descriptor.
1512 bool "Enable timerfd() system call" if EXPERT
1515 Enable the timerfd() system call that allows to receive timer
1516 events on a file descriptor.
1521 bool "Enable eventfd() system call" if EXPERT
1524 Enable the eventfd() system call that allows to receive both
1525 kernel notification (ie. KAIO) or userspace notifications.
1530 bool "Use full shmem filesystem" if EXPERT
1534 The shmem is an internal filesystem used to manage shared memory.
1535 It is backed by swap and manages resource limits. It is also exported
1536 to userspace as tmpfs if TMPFS is enabled. Disabling this
1537 option replaces shmem and tmpfs with the much simpler ramfs code,
1538 which may be appropriate on small systems without swap.
1541 bool "Enable AIO support" if EXPERT
1544 This option enables POSIX asynchronous I/O which may by used
1545 by some high performance threaded applications. Disabling
1546 this option saves about 7k.
1549 bool "Enable IO uring support" if EXPERT
1553 This option enables support for the io_uring interface, enabling
1554 applications to submit and complete IO through submission and
1555 completion rings that are shared between the kernel and application.
1557 config ADVISE_SYSCALLS
1558 bool "Enable madvise/fadvise syscalls" if EXPERT
1561 This option enables the madvise and fadvise syscalls, used by
1562 applications to advise the kernel about their future memory or file
1563 usage, improving performance. If building an embedded system where no
1564 applications use these syscalls, you can disable this option to save
1568 bool "Enable membarrier() system call" if EXPERT
1571 Enable the membarrier() system call that allows issuing memory
1572 barriers across all running threads, which can be used to distribute
1573 the cost of user-space memory barriers asymmetrically by transforming
1574 pairs of memory barriers into pairs consisting of membarrier() and a
1580 bool "Load all symbols for debugging/ksymoops" if EXPERT
1583 Say Y here to let the kernel print out symbolic crash information and
1584 symbolic stack backtraces. This increases the size of the kernel
1585 somewhat, as all symbols have to be loaded into the kernel image.
1588 bool "Include all symbols in kallsyms"
1589 depends on DEBUG_KERNEL && KALLSYMS
1591 Normally kallsyms only contains the symbols of functions for nicer
1592 OOPS messages and backtraces (i.e., symbols from the text and inittext
1593 sections). This is sufficient for most cases. And only in very rare
1594 cases (e.g., when a debugger is used) all symbols are required (e.g.,
1595 names of variables from the data sections, etc).
1597 This option makes sure that all symbols are loaded into the kernel
1598 image (i.e., symbols from all sections) in cost of increased kernel
1599 size (depending on the kernel configuration, it may be 300KiB or
1600 something like this).
1602 Say N unless you really need all symbols.
1604 config KALLSYMS_ABSOLUTE_PERCPU
1607 default X86_64 && SMP
1609 config KALLSYMS_BASE_RELATIVE
1614 Instead of emitting them as absolute values in the native word size,
1615 emit the symbol references in the kallsyms table as 32-bit entries,
1616 each containing a relative value in the range [base, base + U32_MAX]
1617 or, when KALLSYMS_ABSOLUTE_PERCPU is in effect, each containing either
1618 an absolute value in the range [0, S32_MAX] or a relative value in the
1619 range [base, base + S32_MAX], where base is the lowest relative symbol
1620 address encountered in the image.
1622 On 64-bit builds, this reduces the size of the address table by 50%,
1623 but more importantly, it results in entries whose values are build
1624 time constants, and no relocation pass is required at runtime to fix
1625 up the entries based on the runtime load address of the kernel.
1627 # end of the "standard kernel features (expert users)" menu
1629 # syscall, maps, verifier
1631 bool "Enable bpf() system call"
1636 Enable the bpf() system call that allows to manipulate eBPF
1637 programs and maps via file descriptors.
1639 config BPF_JIT_ALWAYS_ON
1640 bool "Permanently enable BPF JIT and remove BPF interpreter"
1641 depends on BPF_SYSCALL && HAVE_EBPF_JIT && BPF_JIT
1643 Enables BPF JIT and removes BPF interpreter to avoid
1644 speculative execution of BPF instructions by the interpreter
1647 bool "Enable userfaultfd() system call"
1650 Enable the userfaultfd() system call that allows to intercept and
1651 handle page faults in userland.
1653 config ARCH_HAS_MEMBARRIER_CALLBACKS
1656 config ARCH_HAS_MEMBARRIER_SYNC_CORE
1660 bool "Enable rseq() system call" if EXPERT
1662 depends on HAVE_RSEQ
1665 Enable the restartable sequences system call. It provides a
1666 user-space cache for the current CPU number value, which
1667 speeds up getting the current CPU number from user-space,
1668 as well as an ABI to speed up user-space operations on
1675 bool "Enabled debugging of rseq() system call" if EXPERT
1676 depends on RSEQ && DEBUG_KERNEL
1678 Enable extra debugging checks for the rseq system call.
1683 bool "Embedded system"
1684 option allnoconfig_y
1687 This option should be enabled if compiling the kernel for
1688 an embedded system so certain expert options are available
1691 config HAVE_PERF_EVENTS
1694 See tools/perf/design.txt for details.
1696 config PERF_USE_VMALLOC
1699 See tools/perf/design.txt for details
1702 bool "PC/104 support" if EXPERT
1704 Expose PC/104 form factor device drivers and options available for
1705 selection and configuration. Enable this option if your target
1706 machine has a PC/104 bus.
1708 menu "Kernel Performance Events And Counters"
1711 bool "Kernel performance events and counters"
1712 default y if PROFILING
1713 depends on HAVE_PERF_EVENTS
1717 Enable kernel support for various performance events provided
1718 by software and hardware.
1720 Software events are supported either built-in or via the
1721 use of generic tracepoints.
1723 Most modern CPUs support performance events via performance
1724 counter registers. These registers count the number of certain
1725 types of hw events: such as instructions executed, cachemisses
1726 suffered, or branches mis-predicted - without slowing down the
1727 kernel or applications. These registers can also trigger interrupts
1728 when a threshold number of events have passed - and can thus be
1729 used to profile the code that runs on that CPU.
1731 The Linux Performance Event subsystem provides an abstraction of
1732 these software and hardware event capabilities, available via a
1733 system call and used by the "perf" utility in tools/perf/. It
1734 provides per task and per CPU counters, and it provides event
1735 capabilities on top of those.
1739 config DEBUG_PERF_USE_VMALLOC
1741 bool "Debug: use vmalloc to back perf mmap() buffers"
1742 depends on PERF_EVENTS && DEBUG_KERNEL && !PPC
1743 select PERF_USE_VMALLOC
1745 Use vmalloc memory to back perf mmap() buffers.
1747 Mostly useful for debugging the vmalloc code on platforms
1748 that don't require it.
1754 config VM_EVENT_COUNTERS
1756 bool "Enable VM event counters for /proc/vmstat" if EXPERT
1758 VM event counters are needed for event counts to be shown.
1759 This option allows the disabling of the VM event counters
1760 on EXPERT systems. /proc/vmstat will only show page counts
1761 if VM event counters are disabled.
1765 bool "Enable SLUB debugging support" if EXPERT
1766 depends on SLUB && SYSFS
1768 SLUB has extensive debug support features. Disabling these can
1769 result in significant savings in code size. This also disables
1770 SLUB sysfs support. /sys/slab will not exist and there will be
1771 no support for cache validation etc.
1773 config SLUB_MEMCG_SYSFS_ON
1775 bool "Enable memcg SLUB sysfs support by default" if EXPERT
1776 depends on SLUB && SYSFS && MEMCG
1778 SLUB creates a directory under /sys/kernel/slab for each
1779 allocation cache to host info and debug files. If memory
1780 cgroup is enabled, each cache can have per memory cgroup
1781 caches. SLUB can create the same sysfs directories for these
1782 caches under /sys/kernel/slab/CACHE/cgroup but it can lead
1783 to a very high number of debug files being created. This is
1784 controlled by slub_memcg_sysfs boot parameter and this
1785 config option determines the parameter's default value.
1788 bool "Disable heap randomization"
1791 Randomizing heap placement makes heap exploits harder, but it
1792 also breaks ancient binaries (including anything libc5 based).
1793 This option changes the bootup default to heap randomization
1794 disabled, and can be overridden at runtime by setting
1795 /proc/sys/kernel/randomize_va_space to 2.
1797 On non-ancient distros (post-2000 ones) N is usually a safe choice.
1800 prompt "Choose SLAB allocator"
1803 This option allows to select a slab allocator.
1807 select HAVE_HARDENED_USERCOPY_ALLOCATOR
1809 The regular slab allocator that is established and known to work
1810 well in all environments. It organizes cache hot objects in
1811 per cpu and per node queues.
1814 bool "SLUB (Unqueued Allocator)"
1815 select HAVE_HARDENED_USERCOPY_ALLOCATOR
1817 SLUB is a slab allocator that minimizes cache line usage
1818 instead of managing queues of cached objects (SLAB approach).
1819 Per cpu caching is realized using slabs of objects instead
1820 of queues of objects. SLUB can use memory efficiently
1821 and has enhanced diagnostics. SLUB is the default choice for
1826 bool "SLOB (Simple Allocator)"
1828 SLOB replaces the stock allocator with a drastically simpler
1829 allocator. SLOB is generally more space efficient but
1830 does not perform as well on large systems.
1834 config SLAB_MERGE_DEFAULT
1835 bool "Allow slab caches to be merged"
1838 For reduced kernel memory fragmentation, slab caches can be
1839 merged when they share the same size and other characteristics.
1840 This carries a risk of kernel heap overflows being able to
1841 overwrite objects from merged caches (and more easily control
1842 cache layout), which makes such heap attacks easier to exploit
1843 by attackers. By keeping caches unmerged, these kinds of exploits
1844 can usually only damage objects in the same cache. To disable
1845 merging at runtime, "slab_nomerge" can be passed on the kernel
1848 config SLAB_FREELIST_RANDOM
1850 depends on SLAB || SLUB
1851 bool "SLAB freelist randomization"
1853 Randomizes the freelist order used on creating new pages. This
1854 security feature reduces the predictability of the kernel slab
1855 allocator against heap overflows.
1857 config SLAB_FREELIST_HARDENED
1858 bool "Harden slab freelist metadata"
1861 Many kernel heap attacks try to target slab cache metadata and
1862 other infrastructure. This options makes minor performance
1863 sacrifices to harden the kernel slab allocator against common
1864 freelist exploit methods.
1866 config SHUFFLE_PAGE_ALLOCATOR
1867 bool "Page allocator randomization"
1868 default SLAB_FREELIST_RANDOM && ACPI_NUMA
1870 Randomization of the page allocator improves the average
1871 utilization of a direct-mapped memory-side-cache. See section
1872 5.2.27 Heterogeneous Memory Attribute Table (HMAT) in the ACPI
1873 6.2a specification for an example of how a platform advertises
1874 the presence of a memory-side-cache. There are also incidental
1875 security benefits as it reduces the predictability of page
1876 allocations to compliment SLAB_FREELIST_RANDOM, but the
1877 default granularity of shuffling on the "MAX_ORDER - 1" i.e,
1878 10th order of pages is selected based on cache utilization
1881 While the randomization improves cache utilization it may
1882 negatively impact workloads on platforms without a cache. For
1883 this reason, by default, the randomization is enabled only
1884 after runtime detection of a direct-mapped memory-side-cache.
1885 Otherwise, the randomization may be force enabled with the
1886 'page_alloc.shuffle' kernel command line parameter.
1890 config SLUB_CPU_PARTIAL
1892 depends on SLUB && SMP
1893 bool "SLUB per cpu partial cache"
1895 Per cpu partial caches accelerate objects allocation and freeing
1896 that is local to a processor at the price of more indeterminism
1897 in the latency of the free. On overflow these caches will be cleared
1898 which requires the taking of locks that may cause latency spikes.
1899 Typically one would choose no for a realtime system.
1901 config MMAP_ALLOW_UNINITIALIZED
1902 bool "Allow mmapped anonymous memory to be uninitialized"
1903 depends on EXPERT && !MMU
1906 Normally, and according to the Linux spec, anonymous memory obtained
1907 from mmap() has its contents cleared before it is passed to
1908 userspace. Enabling this config option allows you to request that
1909 mmap() skip that if it is given an MAP_UNINITIALIZED flag, thus
1910 providing a huge performance boost. If this option is not enabled,
1911 then the flag will be ignored.
1913 This is taken advantage of by uClibc's malloc(), and also by
1914 ELF-FDPIC binfmt's brk and stack allocator.
1916 Because of the obvious security issues, this option should only be
1917 enabled on embedded devices where you control what is run in
1918 userspace. Since that isn't generally a problem on no-MMU systems,
1919 it is normally safe to say Y here.
1921 See Documentation/nommu-mmap.txt for more information.
1923 config SYSTEM_DATA_VERIFICATION
1925 select SYSTEM_TRUSTED_KEYRING
1929 select ASYMMETRIC_KEY_TYPE
1930 select ASYMMETRIC_PUBLIC_KEY_SUBTYPE
1933 select X509_CERTIFICATE_PARSER
1934 select PKCS7_MESSAGE_PARSER
1936 Provide PKCS#7 message verification using the contents of the system
1937 trusted keyring to provide public keys. This then can be used for
1938 module verification, kexec image verification and firmware blob
1942 bool "Profiling support"
1944 Say Y here to enable the extended profiling support mechanisms used
1945 by profilers such as OProfile.
1948 # Place an empty function call at each tracepoint site. Can be
1949 # dynamically changed for a probe function.
1954 endmenu # General setup
1956 source "arch/Kconfig"
1963 default 0 if BASE_FULL
1964 default 1 if !BASE_FULL
1966 config MODULE_SIG_FORMAT
1968 select SYSTEM_DATA_VERIFICATION
1971 bool "Enable loadable module support"
1974 Kernel modules are small pieces of compiled code which can
1975 be inserted in the running kernel, rather than being
1976 permanently built into the kernel. You use the "modprobe"
1977 tool to add (and sometimes remove) them. If you say Y here,
1978 many parts of the kernel can be built as modules (by
1979 answering M instead of Y where indicated): this is most
1980 useful for infrequently used options which are not required
1981 for booting. For more information, see the man pages for
1982 modprobe, lsmod, modinfo, insmod and rmmod.
1984 If you say Y here, you will need to run "make
1985 modules_install" to put the modules under /lib/modules/
1986 where modprobe can find them (you may need to be root to do
1993 config MODULE_FORCE_LOAD
1994 bool "Forced module loading"
1997 Allow loading of modules without version information (ie. modprobe
1998 --force). Forced module loading sets the 'F' (forced) taint flag and
1999 is usually a really bad idea.
2001 config MODULE_UNLOAD
2002 bool "Module unloading"
2004 Without this option you will not be able to unload any
2005 modules (note that some modules may not be unloadable
2006 anyway), which makes your kernel smaller, faster
2007 and simpler. If unsure, say Y.
2009 config MODULE_FORCE_UNLOAD
2010 bool "Forced module unloading"
2011 depends on MODULE_UNLOAD
2013 This option allows you to force a module to unload, even if the
2014 kernel believes it is unsafe: the kernel will remove the module
2015 without waiting for anyone to stop using it (using the -f option to
2016 rmmod). This is mainly for kernel developers and desperate users.
2020 bool "Module versioning support"
2022 Usually, you have to use modules compiled with your kernel.
2023 Saying Y here makes it sometimes possible to use modules
2024 compiled for different kernels, by adding enough information
2025 to the modules to (hopefully) spot any changes which would
2026 make them incompatible with the kernel you are running. If
2029 config ASM_MODVERSIONS
2031 default HAVE_ASM_MODVERSIONS && MODVERSIONS
2033 This enables module versioning for exported symbols also from
2034 assembly. This can be enabled only when the target architecture
2037 config MODULE_REL_CRCS
2039 depends on MODVERSIONS
2041 config MODULE_SRCVERSION_ALL
2042 bool "Source checksum for all modules"
2044 Modules which contain a MODULE_VERSION get an extra "srcversion"
2045 field inserted into their modinfo section, which contains a
2046 sum of the source files which made it. This helps maintainers
2047 see exactly which source was used to build a module (since
2048 others sometimes change the module source without updating
2049 the version). With this option, such a "srcversion" field
2050 will be created for all modules. If unsure, say N.
2053 bool "Module signature verification"
2054 select MODULE_SIG_FORMAT
2056 Check modules for valid signatures upon load: the signature
2057 is simply appended to the module. For more information see
2058 <file:Documentation/admin-guide/module-signing.rst>.
2060 Note that this option adds the OpenSSL development packages as a
2061 kernel build dependency so that the signing tool can use its crypto
2064 !!!WARNING!!! If you enable this option, you MUST make sure that the
2065 module DOES NOT get stripped after being signed. This includes the
2066 debuginfo strip done by some packagers (such as rpmbuild) and
2067 inclusion into an initramfs that wants the module size reduced.
2069 config MODULE_SIG_FORCE
2070 bool "Require modules to be validly signed"
2071 depends on MODULE_SIG
2073 Reject unsigned modules or signed modules for which we don't have a
2074 key. Without this, such modules will simply taint the kernel.
2076 config MODULE_SIG_ALL
2077 bool "Automatically sign all modules"
2079 depends on MODULE_SIG
2081 Sign all modules during make modules_install. Without this option,
2082 modules must be signed manually, using the scripts/sign-file tool.
2084 comment "Do not forget to sign required modules with scripts/sign-file"
2085 depends on MODULE_SIG_FORCE && !MODULE_SIG_ALL
2088 prompt "Which hash algorithm should modules be signed with?"
2089 depends on MODULE_SIG
2091 This determines which sort of hashing algorithm will be used during
2092 signature generation. This algorithm _must_ be built into the kernel
2093 directly so that signature verification can take place. It is not
2094 possible to load a signed module containing the algorithm to check
2095 the signature on that module.
2097 config MODULE_SIG_SHA1
2098 bool "Sign modules with SHA-1"
2101 config MODULE_SIG_SHA224
2102 bool "Sign modules with SHA-224"
2103 select CRYPTO_SHA256
2105 config MODULE_SIG_SHA256
2106 bool "Sign modules with SHA-256"
2107 select CRYPTO_SHA256
2109 config MODULE_SIG_SHA384
2110 bool "Sign modules with SHA-384"
2111 select CRYPTO_SHA512
2113 config MODULE_SIG_SHA512
2114 bool "Sign modules with SHA-512"
2115 select CRYPTO_SHA512
2119 config MODULE_SIG_HASH
2121 depends on MODULE_SIG
2122 default "sha1" if MODULE_SIG_SHA1
2123 default "sha224" if MODULE_SIG_SHA224
2124 default "sha256" if MODULE_SIG_SHA256
2125 default "sha384" if MODULE_SIG_SHA384
2126 default "sha512" if MODULE_SIG_SHA512
2128 config MODULE_COMPRESS
2129 bool "Compress modules on installation"
2132 Compresses kernel modules when 'make modules_install' is run; gzip or
2133 xz depending on "Compression algorithm" below.
2135 module-init-tools MAY support gzip, and kmod MAY support gzip and xz.
2137 Out-of-tree kernel modules installed using Kbuild will also be
2138 compressed upon installation.
2140 Note: for modules inside an initrd or initramfs, it's more efficient
2141 to compress the whole initrd or initramfs instead.
2143 Note: This is fully compatible with signed modules.
2148 prompt "Compression algorithm"
2149 depends on MODULE_COMPRESS
2150 default MODULE_COMPRESS_GZIP
2152 This determines which sort of compression will be used during
2153 'make modules_install'.
2155 GZIP (default) and XZ are supported.
2157 config MODULE_COMPRESS_GZIP
2160 config MODULE_COMPRESS_XZ
2165 config MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS
2166 bool "Allow loading of modules with missing namespace imports"
2168 Symbols exported with EXPORT_SYMBOL_NS*() are considered exported in
2169 a namespace. A module that makes use of a symbol exported with such a
2170 namespace is required to import the namespace via MODULE_IMPORT_NS().
2171 There is no technical reason to enforce correct namespace imports,
2172 but it creates consistency between symbols defining namespaces and
2173 users importing namespaces they make use of. This option relaxes this
2174 requirement and lifts the enforcement when loading a module.
2178 config UNUSED_SYMBOLS
2179 bool "Enable unused/obsolete exported symbols"
2182 Unused but exported symbols make the kernel needlessly bigger. For
2183 that reason most of these unused exports will soon be removed. This
2184 option is provided temporarily to provide a transition period in case
2185 some external kernel module needs one of these symbols anyway. If you
2186 encounter such a case in your module, consider if you are actually
2187 using the right API. (rationale: since nobody in the kernel is using
2188 this in a module, there is a pretty good chance it's actually the
2189 wrong interface to use). If you really need the symbol, please send a
2190 mail to the linux kernel mailing list mentioning the symbol and why
2191 you really need it, and what the merge plan to the mainline kernel for
2194 config TRIM_UNUSED_KSYMS
2195 bool "Trim unused exported kernel symbols"
2196 depends on !UNUSED_SYMBOLS
2198 The kernel and some modules make many symbols available for
2199 other modules to use via EXPORT_SYMBOL() and variants. Depending
2200 on the set of modules being selected in your kernel configuration,
2201 many of those exported symbols might never be used.
2203 This option allows for unused exported symbols to be dropped from
2204 the build. In turn, this provides the compiler more opportunities
2205 (especially when using LTO) for optimizing the code and reducing
2206 binary size. This might have some security advantages as well.
2208 If unsure, or if you need to build out-of-tree modules, say N.
2212 config MODULES_TREE_LOOKUP
2214 depends on PERF_EVENTS || TRACING
2216 config INIT_ALL_POSSIBLE
2219 Back when each arch used to define their own cpu_online_mask and
2220 cpu_possible_mask, some of them chose to initialize cpu_possible_mask
2221 with all 1s, and others with all 0s. When they were centralised,
2222 it was better to provide this option than to break all the archs
2223 and have several arch maintainers pursuing me down dark alleys.
2225 source "block/Kconfig"
2227 config PREEMPT_NOTIFIERS
2237 Build a simple ASN.1 grammar compiler that produces a bytecode output
2238 that can be interpreted by the ASN.1 stream decoder and used to
2239 inform it as to what tags are to be expected in a stream and what
2240 functions to call on what tags.
2242 source "kernel/Kconfig.locks"
2244 config ARCH_HAS_SYNC_CORE_BEFORE_USERMODE
2247 # It may be useful for an architecture to override the definitions of the
2248 # SYSCALL_DEFINE() and __SYSCALL_DEFINEx() macros in <linux/syscalls.h>
2249 # and the COMPAT_ variants in <linux/compat.h>, in particular to use a
2250 # different calling convention for syscalls. They can also override the
2251 # macros for not-implemented syscalls in kernel/sys_ni.c and
2252 # kernel/time/posix-stubs.c. All these overrides need to be available in
2253 # <asm/syscall_wrapper.h>.
2254 config ARCH_HAS_SYSCALL_WRAPPER
git.samba.org / sfrench / cifs-2.6.git / blob