7 option env="KERNELVERSION"
13 default "/lib/modules/$UNAME_RELEASE/.config"
14 default "/etc/kernel-config"
15 default "/boot/config-$UNAME_RELEASE"
16 default "$ARCH_DEFCONFIG"
17 default "arch/$ARCH/defconfig"
26 config BUILDTIME_EXTABLE_SORT
36 depends on BROKEN || !SMP
39 config INIT_ENV_ARG_LIMIT
44 Maximum of each of the number of arguments and environment
45 variables passed to init from the kernel command line.
49 string "Cross-compiler tool prefix"
51 Same as running 'make CROSS_COMPILE=prefix-' but stored for
52 default make runs in this kernel build directory. You don't
53 need to set this unless you want the configured kernel build
54 directory to select the cross-compiler automatically.
57 bool "Compile also drivers which will not load"
60 Some drivers can be compiled on a different platform than they are
61 intended to be run on. Despite they cannot be loaded there (or even
62 when they load they cannot be used due to missing HW support),
63 developers still, opposing to distributors, might want to build such
64 drivers to compile-test them.
66 If you are a developer and want to build everything available, say Y
67 here. If you are a user/distributor, say N here to exclude useless
68 drivers to be distributed.
71 string "Local version - append to kernel release"
73 Append an extra string to the end of your kernel version.
74 This will show up when you type uname, for example.
75 The string you set here will be appended after the contents of
76 any files with a filename matching localversion* in your
77 object and source tree, in that order. Your total string can
78 be a maximum of 64 characters.
80 config LOCALVERSION_AUTO
81 bool "Automatically append version information to the version string"
84 This will try to automatically determine if the current tree is a
85 release tree by looking for git tags that belong to the current
88 A string of the format -gxxxxxxxx will be added to the localversion
89 if a git-based tree is found. The string generated by this will be
90 appended after any matching localversion* files, and after the value
91 set in CONFIG_LOCALVERSION.
93 (The actual string used here is the first eight characters produced
94 by running the command:
96 $ git rev-parse --verify HEAD
98 which is done within the script "scripts/setlocalversion".)
100 config HAVE_KERNEL_GZIP
103 config HAVE_KERNEL_BZIP2
106 config HAVE_KERNEL_LZMA
109 config HAVE_KERNEL_XZ
112 config HAVE_KERNEL_LZO
115 config HAVE_KERNEL_LZ4
119 prompt "Kernel compression mode"
121 depends on HAVE_KERNEL_GZIP || HAVE_KERNEL_BZIP2 || HAVE_KERNEL_LZMA || HAVE_KERNEL_XZ || HAVE_KERNEL_LZO || HAVE_KERNEL_LZ4
123 The linux kernel is a kind of self-extracting executable.
124 Several compression algorithms are available, which differ
125 in efficiency, compression and decompression speed.
126 Compression speed is only relevant when building a kernel.
127 Decompression speed is relevant at each boot.
129 If you have any problems with bzip2 or lzma compressed
130 kernels, mail me (Alain Knaff) <alain@knaff.lu>. (An older
131 version of this functionality (bzip2 only), for 2.4, was
132 supplied by Christian Ludwig)
134 High compression options are mostly useful for users, who
135 are low on disk space (embedded systems), but for whom ram
138 If in doubt, select 'gzip'
142 depends on HAVE_KERNEL_GZIP
144 The old and tried gzip compression. It provides a good balance
145 between compression ratio and decompression speed.
149 depends on HAVE_KERNEL_BZIP2
151 Its compression ratio and speed is intermediate.
152 Decompression speed is slowest among the choices. The kernel
153 size is about 10% smaller with bzip2, in comparison to gzip.
154 Bzip2 uses a large amount of memory. For modern kernels you
155 will need at least 8MB RAM or more for booting.
159 depends on HAVE_KERNEL_LZMA
161 This compression algorithm's ratio is best. Decompression speed
162 is between gzip and bzip2. Compression is slowest.
163 The kernel size is about 33% smaller with LZMA in comparison to gzip.
167 depends on HAVE_KERNEL_XZ
169 XZ uses the LZMA2 algorithm and instruction set specific
170 BCJ filters which can improve compression ratio of executable
171 code. The size of the kernel is about 30% smaller with XZ in
172 comparison to gzip. On architectures for which there is a BCJ
173 filter (i386, x86_64, ARM, IA-64, PowerPC, and SPARC), XZ
174 will create a few percent smaller kernel than plain LZMA.
176 The speed is about the same as with LZMA: The decompression
177 speed of XZ is better than that of bzip2 but worse than gzip
178 and LZO. Compression is slow.
182 depends on HAVE_KERNEL_LZO
184 Its compression ratio is the poorest among the choices. The kernel
185 size is about 10% bigger than gzip; however its speed
186 (both compression and decompression) is the fastest.
190 depends on HAVE_KERNEL_LZ4
192 LZ4 is an LZ77-type compressor with a fixed, byte-oriented encoding.
193 A preliminary version of LZ4 de/compression tool is available at
194 <https://code.google.com/p/lz4/>.
196 Its compression ratio is worse than LZO. The size of the kernel
197 is about 8% bigger than LZO. But the decompression speed is
202 config DEFAULT_HOSTNAME
203 string "Default hostname"
206 This option determines the default system hostname before userspace
207 calls sethostname(2). The kernel traditionally uses "(none)" here,
208 but you may wish to use a different default here to make a minimal
209 system more usable with less configuration.
212 bool "Support for paging of anonymous memory (swap)"
213 depends on MMU && BLOCK
216 This option allows you to choose whether you want to have support
217 for so called swap devices or swap files in your kernel that are
218 used to provide more virtual memory than the actual RAM present
219 in your computer. If unsure say Y.
224 Inter Process Communication is a suite of library functions and
225 system calls which let processes (running programs) synchronize and
226 exchange information. It is generally considered to be a good thing,
227 and some programs won't run unless you say Y here. In particular, if
228 you want to run the DOS emulator dosemu under Linux (read the
229 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
230 you'll need to say Y here.
232 You can find documentation about IPC with "info ipc" and also in
233 section 6.4 of the Linux Programmer's Guide, available from
234 <http://www.tldp.org/guides.html>.
236 config SYSVIPC_SYSCTL
243 bool "POSIX Message Queues"
246 POSIX variant of message queues is a part of IPC. In POSIX message
247 queues every message has a priority which decides about succession
248 of receiving it by a process. If you want to compile and run
249 programs written e.g. for Solaris with use of its POSIX message
250 queues (functions mq_*) say Y here.
252 POSIX message queues are visible as a filesystem called 'mqueue'
253 and can be mounted somewhere if you want to do filesystem
254 operations on message queues.
258 config POSIX_MQUEUE_SYSCTL
260 depends on POSIX_MQUEUE
264 config CROSS_MEMORY_ATTACH
265 bool "Enable process_vm_readv/writev syscalls"
269 Enabling this option adds the system calls process_vm_readv and
270 process_vm_writev which allow a process with the correct privileges
271 to directly read from or write to another process' address space.
272 See the man page for more details.
275 bool "open by fhandle syscalls"
278 If you say Y here, a user level program will be able to map
279 file names to handle and then later use the handle for
280 different file system operations. This is useful in implementing
281 userspace file servers, which now track files using handles instead
282 of names. The handle would remain the same even if file names
283 get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2)
287 bool "uselib syscall"
288 def_bool ALPHA || M68K || SPARC || X86_32 || IA32_EMULATION
290 This option enables the uselib syscall, a system call used in the
291 dynamic linker from libc5 and earlier. glibc does not use this
292 system call. If you intend to run programs built on libc5 or
293 earlier, you may need to enable this syscall. Current systems
294 running glibc can safely disable this.
297 bool "Auditing support"
300 Enable auditing infrastructure that can be used with another
301 kernel subsystem, such as SELinux (which requires this for
302 logging of avc messages output). System call auditing is included
303 on architectures which support it.
305 config HAVE_ARCH_AUDITSYSCALL
310 depends on AUDIT && HAVE_ARCH_AUDITSYSCALL
314 depends on AUDITSYSCALL
319 depends on AUDITSYSCALL
322 source "kernel/irq/Kconfig"
323 source "kernel/time/Kconfig"
325 menu "CPU/Task time and stats accounting"
327 config VIRT_CPU_ACCOUNTING
331 prompt "Cputime accounting"
332 default TICK_CPU_ACCOUNTING if !PPC64
333 default VIRT_CPU_ACCOUNTING_NATIVE if PPC64
335 # Kind of a stub config for the pure tick based cputime accounting
336 config TICK_CPU_ACCOUNTING
337 bool "Simple tick based cputime accounting"
338 depends on !S390 && !NO_HZ_FULL
340 This is the basic tick based cputime accounting that maintains
341 statistics about user, system and idle time spent on per jiffies
346 config VIRT_CPU_ACCOUNTING_NATIVE
347 bool "Deterministic task and CPU time accounting"
348 depends on HAVE_VIRT_CPU_ACCOUNTING && !NO_HZ_FULL
349 select VIRT_CPU_ACCOUNTING
351 Select this option to enable more accurate task and CPU time
352 accounting. This is done by reading a CPU counter on each
353 kernel entry and exit and on transitions within the kernel
354 between system, softirq and hardirq state, so there is a
355 small performance impact. In the case of s390 or IBM POWER > 5,
356 this also enables accounting of stolen time on logically-partitioned
359 config VIRT_CPU_ACCOUNTING_GEN
360 bool "Full dynticks CPU time accounting"
361 depends on HAVE_CONTEXT_TRACKING
362 depends on HAVE_VIRT_CPU_ACCOUNTING_GEN
363 select VIRT_CPU_ACCOUNTING
364 select CONTEXT_TRACKING
366 Select this option to enable task and CPU time accounting on full
367 dynticks systems. This accounting is implemented by watching every
368 kernel-user boundaries using the context tracking subsystem.
369 The accounting is thus performed at the expense of some significant
372 For now this is only useful if you are working on the full
373 dynticks subsystem development.
377 config IRQ_TIME_ACCOUNTING
378 bool "Fine granularity task level IRQ time accounting"
379 depends on HAVE_IRQ_TIME_ACCOUNTING && !NO_HZ_FULL
381 Select this option to enable fine granularity task irq time
382 accounting. This is done by reading a timestamp on each
383 transitions between softirq and hardirq state, so there can be a
384 small performance impact.
386 If in doubt, say N here.
390 config BSD_PROCESS_ACCT
391 bool "BSD Process Accounting"
394 If you say Y here, a user level program will be able to instruct the
395 kernel (via a special system call) to write process accounting
396 information to a file: whenever a process exits, information about
397 that process will be appended to the file by the kernel. The
398 information includes things such as creation time, owning user,
399 command name, memory usage, controlling terminal etc. (the complete
400 list is in the struct acct in <file:include/linux/acct.h>). It is
401 up to the user level program to do useful things with this
402 information. This is generally a good idea, so say Y.
404 config BSD_PROCESS_ACCT_V3
405 bool "BSD Process Accounting version 3 file format"
406 depends on BSD_PROCESS_ACCT
409 If you say Y here, the process accounting information is written
410 in a new file format that also logs the process IDs of each
411 process and it's parent. Note that this file format is incompatible
412 with previous v0/v1/v2 file formats, so you will need updated tools
413 for processing it. A preliminary version of these tools is available
414 at <http://www.gnu.org/software/acct/>.
417 bool "Export task/process statistics through netlink"
422 Export selected statistics for tasks/processes through the
423 generic netlink interface. Unlike BSD process accounting, the
424 statistics are available during the lifetime of tasks/processes as
425 responses to commands. Like BSD accounting, they are sent to user
430 config TASK_DELAY_ACCT
431 bool "Enable per-task delay accounting"
435 Collect information on time spent by a task waiting for system
436 resources like cpu, synchronous block I/O completion and swapping
437 in pages. Such statistics can help in setting a task's priorities
438 relative to other tasks for cpu, io, rss limits etc.
443 bool "Enable extended accounting over taskstats"
446 Collect extended task accounting data and send the data
447 to userland for processing over the taskstats interface.
451 config TASK_IO_ACCOUNTING
452 bool "Enable per-task storage I/O accounting"
453 depends on TASK_XACCT
455 Collect information on the number of bytes of storage I/O which this
460 endmenu # "CPU/Task time and stats accounting"
466 default y if !PREEMPT && SMP
468 This option selects the RCU implementation that is
469 designed for very large SMP system with hundreds or
470 thousands of CPUs. It also scales down nicely to
477 This option selects the RCU implementation that is
478 designed for very large SMP systems with hundreds or
479 thousands of CPUs, but for which real-time response
480 is also required. It also scales down nicely to
483 Select this option if you are unsure.
487 default y if !PREEMPT && !SMP
489 This option selects the RCU implementation that is
490 designed for UP systems from which real-time response
491 is not required. This option greatly reduces the
492 memory footprint of RCU.
495 bool "Make expert-level adjustments to RCU configuration"
498 This option needs to be enabled if you wish to make
499 expert-level adjustments to RCU configuration. By default,
500 no such adjustments can be made, which has the often-beneficial
501 side-effect of preventing "make oldconfig" from asking you all
502 sorts of detailed questions about how you would like numerous
503 obscure RCU options to be set up.
505 Say Y if you need to make expert-level adjustments to RCU.
507 Say N if you are unsure.
512 This option selects the sleepable version of RCU. This version
513 permits arbitrary sleeping or blocking within RCU read-side critical
521 This option enables a task-based RCU implementation that uses
522 only voluntary context switch (not preemption!), idle, and
523 user-mode execution as quiescent states.
525 config RCU_STALL_COMMON
526 def_bool ( TREE_RCU || PREEMPT_RCU || RCU_TRACE )
528 This option enables RCU CPU stall code that is common between
529 the TINY and TREE variants of RCU. The purpose is to allow
530 the tiny variants to disable RCU CPU stall warnings, while
531 making these warnings mandatory for the tree variants.
533 config CONTEXT_TRACKING
536 config CONTEXT_TRACKING_FORCE
537 bool "Force context tracking"
538 depends on CONTEXT_TRACKING
539 default y if !NO_HZ_FULL
541 The major pre-requirement for full dynticks to work is to
542 support the context tracking subsystem. But there are also
543 other dependencies to provide in order to make the full
546 This option stands for testing when an arch implements the
547 context tracking backend but doesn't yet fullfill all the
548 requirements to make the full dynticks feature working.
549 Without the full dynticks, there is no way to test the support
550 for context tracking and the subsystems that rely on it: RCU
551 userspace extended quiescent state and tickless cputime
552 accounting. This option copes with the absence of the full
553 dynticks subsystem by forcing the context tracking on all
556 Say Y only if you're working on the development of an
557 architecture backend for the context tracking.
559 Say N otherwise, this option brings an overhead that you
560 don't want in production.
564 int "Tree-based hierarchical RCU fanout value"
567 depends on (TREE_RCU || PREEMPT_RCU) && RCU_EXPERT
571 This option controls the fanout of hierarchical implementations
572 of RCU, allowing RCU to work efficiently on machines with
573 large numbers of CPUs. This value must be at least the fourth
574 root of NR_CPUS, which allows NR_CPUS to be insanely large.
575 The default value of RCU_FANOUT should be used for production
576 systems, but if you are stress-testing the RCU implementation
577 itself, small RCU_FANOUT values allow you to test large-system
578 code paths on small(er) systems.
580 Select a specific number if testing RCU itself.
581 Take the default if unsure.
583 config RCU_FANOUT_LEAF
584 int "Tree-based hierarchical RCU leaf-level fanout value"
587 depends on (TREE_RCU || PREEMPT_RCU) && RCU_EXPERT
590 This option controls the leaf-level fanout of hierarchical
591 implementations of RCU, and allows trading off cache misses
592 against lock contention. Systems that synchronize their
593 scheduling-clock interrupts for energy-efficiency reasons will
594 want the default because the smaller leaf-level fanout keeps
595 lock contention levels acceptably low. Very large systems
596 (hundreds or thousands of CPUs) will instead want to set this
597 value to the maximum value possible in order to reduce the
598 number of cache misses incurred during RCU's grace-period
599 initialization. These systems tend to run CPU-bound, and thus
600 are not helped by synchronized interrupts, and thus tend to
601 skew them, which reduces lock contention enough that large
602 leaf-level fanouts work well.
604 Select a specific number if testing RCU itself.
606 Select the maximum permissible value for large systems.
608 Take the default if unsure.
610 config RCU_FAST_NO_HZ
611 bool "Accelerate last non-dyntick-idle CPU's grace periods"
612 depends on NO_HZ_COMMON && SMP && RCU_EXPERT
615 This option permits CPUs to enter dynticks-idle state even if
616 they have RCU callbacks queued, and prevents RCU from waking
617 these CPUs up more than roughly once every four jiffies (by
618 default, you can adjust this using the rcutree.rcu_idle_gp_delay
619 parameter), thus improving energy efficiency. On the other
620 hand, this option increases the duration of RCU grace periods,
621 for example, slowing down synchronize_rcu().
623 Say Y if energy efficiency is critically important, and you
624 don't care about increased grace-period durations.
626 Say N if you are unsure.
628 config TREE_RCU_TRACE
629 def_bool RCU_TRACE && ( TREE_RCU || PREEMPT_RCU )
632 This option provides tracing for the TREE_RCU and
633 PREEMPT_RCU implementations, permitting Makefile to
634 trivially select kernel/rcutree_trace.c.
637 bool "Enable RCU priority boosting"
638 depends on RT_MUTEXES && PREEMPT_RCU && RCU_EXPERT
641 This option boosts the priority of preempted RCU readers that
642 block the current preemptible RCU grace period for too long.
643 This option also prevents heavy loads from blocking RCU
644 callback invocation for all flavors of RCU.
646 Say Y here if you are working with real-time apps or heavy loads
647 Say N here if you are unsure.
649 config RCU_KTHREAD_PRIO
650 int "Real-time priority to use for RCU worker threads"
651 range 1 99 if RCU_BOOST
652 range 0 99 if !RCU_BOOST
653 default 1 if RCU_BOOST
654 default 0 if !RCU_BOOST
655 depends on RCU_EXPERT
657 This option specifies the SCHED_FIFO priority value that will be
658 assigned to the rcuc/n and rcub/n threads and is also the value
659 used for RCU_BOOST (if enabled). If you are working with a
660 real-time application that has one or more CPU-bound threads
661 running at a real-time priority level, you should set
662 RCU_KTHREAD_PRIO to a priority higher than the highest-priority
663 real-time CPU-bound application thread. The default RCU_KTHREAD_PRIO
664 value of 1 is appropriate in the common case, which is real-time
665 applications that do not have any CPU-bound threads.
667 Some real-time applications might not have a single real-time
668 thread that saturates a given CPU, but instead might have
669 multiple real-time threads that, taken together, fully utilize
670 that CPU. In this case, you should set RCU_KTHREAD_PRIO to
671 a priority higher than the lowest-priority thread that is
672 conspiring to prevent the CPU from running any non-real-time
673 tasks. For example, if one thread at priority 10 and another
674 thread at priority 5 are between themselves fully consuming
675 the CPU time on a given CPU, then RCU_KTHREAD_PRIO should be
676 set to priority 6 or higher.
678 Specify the real-time priority, or take the default if unsure.
680 config RCU_BOOST_DELAY
681 int "Milliseconds to delay boosting after RCU grace-period start"
686 This option specifies the time to wait after the beginning of
687 a given grace period before priority-boosting preempted RCU
688 readers blocking that grace period. Note that any RCU reader
689 blocking an expedited RCU grace period is boosted immediately.
691 Accept the default if unsure.
694 bool "Offload RCU callback processing from boot-selected CPUs"
695 depends on TREE_RCU || PREEMPT_RCU
696 depends on RCU_EXPERT || NO_HZ_FULL
699 Use this option to reduce OS jitter for aggressive HPC or
700 real-time workloads. It can also be used to offload RCU
701 callback invocation to energy-efficient CPUs in battery-powered
702 asymmetric multiprocessors.
704 This option offloads callback invocation from the set of
705 CPUs specified at boot time by the rcu_nocbs parameter.
706 For each such CPU, a kthread ("rcuox/N") will be created to
707 invoke callbacks, where the "N" is the CPU being offloaded,
708 and where the "x" is "b" for RCU-bh, "p" for RCU-preempt, and
709 "s" for RCU-sched. Nothing prevents this kthread from running
710 on the specified CPUs, but (1) the kthreads may be preempted
711 between each callback, and (2) affinity or cgroups can be used
712 to force the kthreads to run on whatever set of CPUs is desired.
714 Say Y here if you want to help to debug reduced OS jitter.
715 Say N here if you are unsure.
718 prompt "Build-forced no-CBs CPUs"
719 default RCU_NOCB_CPU_NONE
720 depends on RCU_NOCB_CPU
722 This option allows no-CBs CPUs (whose RCU callbacks are invoked
723 from kthreads rather than from softirq context) to be specified
724 at build time. Additional no-CBs CPUs may be specified by
725 the rcu_nocbs= boot parameter.
727 config RCU_NOCB_CPU_NONE
728 bool "No build_forced no-CBs CPUs"
730 This option does not force any of the CPUs to be no-CBs CPUs.
731 Only CPUs designated by the rcu_nocbs= boot parameter will be
732 no-CBs CPUs, whose RCU callbacks will be invoked by per-CPU
733 kthreads whose names begin with "rcuo". All other CPUs will
734 invoke their own RCU callbacks in softirq context.
736 Select this option if you want to choose no-CBs CPUs at
737 boot time, for example, to allow testing of different no-CBs
738 configurations without having to rebuild the kernel each time.
740 config RCU_NOCB_CPU_ZERO
741 bool "CPU 0 is a build_forced no-CBs CPU"
743 This option forces CPU 0 to be a no-CBs CPU, so that its RCU
744 callbacks are invoked by a per-CPU kthread whose name begins
745 with "rcuo". Additional CPUs may be designated as no-CBs
746 CPUs using the rcu_nocbs= boot parameter will be no-CBs CPUs.
747 All other CPUs will invoke their own RCU callbacks in softirq
750 Select this if CPU 0 needs to be a no-CBs CPU for real-time
751 or energy-efficiency reasons, but the real reason it exists
752 is to ensure that randconfig testing covers mixed systems.
754 config RCU_NOCB_CPU_ALL
755 bool "All CPUs are build_forced no-CBs CPUs"
757 This option forces all CPUs to be no-CBs CPUs. The rcu_nocbs=
758 boot parameter will be ignored. All CPUs' RCU callbacks will
759 be executed in the context of per-CPU rcuo kthreads created for
760 this purpose. Assuming that the kthreads whose names start with
761 "rcuo" are bound to "housekeeping" CPUs, this reduces OS jitter
762 on the remaining CPUs, but might decrease memory locality during
763 RCU-callback invocation, thus potentially degrading throughput.
765 Select this if all CPUs need to be no-CBs CPUs for real-time
766 or energy-efficiency reasons.
770 config RCU_EXPEDITE_BOOT
774 This option enables expedited grace periods at boot time,
775 as if rcu_expedite_gp() had been invoked early in boot.
776 The corresponding rcu_unexpedite_gp() is invoked from
777 rcu_end_inkernel_boot(), which is intended to be invoked
778 at the end of the kernel-only boot sequence, just before
781 Accept the default if unsure.
783 endmenu # "RCU Subsystem"
790 tristate "Kernel .config support"
793 This option enables the complete Linux kernel ".config" file
794 contents to be saved in the kernel. It provides documentation
795 of which kernel options are used in a running kernel or in an
796 on-disk kernel. This information can be extracted from the kernel
797 image file with the script scripts/extract-ikconfig and used as
798 input to rebuild the current kernel or to build another kernel.
799 It can also be extracted from a running kernel by reading
800 /proc/config.gz if enabled (below).
803 bool "Enable access to .config through /proc/config.gz"
804 depends on IKCONFIG && PROC_FS
806 This option enables access to the kernel configuration file
807 through /proc/config.gz.
810 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
815 Select the minimal kernel log buffer size as a power of 2.
816 The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
817 parameter, see below. Any higher size also might be forced
818 by "log_buf_len" boot parameter.
828 config LOG_CPU_MAX_BUF_SHIFT
829 int "CPU kernel log buffer size contribution (13 => 8 KB, 17 => 128KB)"
832 default 12 if !BASE_SMALL
833 default 0 if BASE_SMALL
836 This option allows to increase the default ring buffer size
837 according to the number of CPUs. The value defines the contribution
838 of each CPU as a power of 2. The used space is typically only few
839 lines however it might be much more when problems are reported,
842 The increased size means that a new buffer has to be allocated and
843 the original static one is unused. It makes sense only on systems
844 with more CPUs. Therefore this value is used only when the sum of
845 contributions is greater than the half of the default kernel ring
846 buffer as defined by LOG_BUF_SHIFT. The default values are set
847 so that more than 64 CPUs are needed to trigger the allocation.
849 Also this option is ignored when "log_buf_len" kernel parameter is
850 used as it forces an exact (power of two) size of the ring buffer.
852 The number of possible CPUs is used for this computation ignoring
853 hotplugging making the compuation optimal for the the worst case
854 scenerio while allowing a simple algorithm to be used from bootup.
856 Examples shift values and their meaning:
857 17 => 128 KB for each CPU
858 16 => 64 KB for each CPU
859 15 => 32 KB for each CPU
860 14 => 16 KB for each CPU
861 13 => 8 KB for each CPU
862 12 => 4 KB for each CPU
864 config NMI_LOG_BUF_SHIFT
865 int "Temporary per-CPU NMI log buffer size (12 => 4KB, 13 => 8KB)"
868 depends on PRINTK_NMI
870 Select the size of a per-CPU buffer where NMI messages are temporary
871 stored. They are copied to the main log buffer in a safe context
872 to avoid a deadlock. The value defines the size as a power of 2.
874 NMI messages are rare and limited. The largest one is when
875 a backtrace is printed. It usually fits into 4KB. Select
876 8KB if you want to be on the safe side.
879 17 => 128 KB for each CPU
880 16 => 64 KB for each CPU
881 15 => 32 KB for each CPU
882 14 => 16 KB for each CPU
883 13 => 8 KB for each CPU
884 12 => 4 KB for each CPU
887 # Architectures with an unreliable sched_clock() should select this:
889 config HAVE_UNSTABLE_SCHED_CLOCK
892 config GENERIC_SCHED_CLOCK
896 # For architectures that want to enable the support for NUMA-affine scheduler
899 config ARCH_SUPPORTS_NUMA_BALANCING
903 # For architectures that prefer to flush all TLBs after a number of pages
904 # are unmapped instead of sending one IPI per page to flush. The architecture
905 # must provide guarantees on what happens if a clean TLB cache entry is
906 # written after the unmap. Details are in mm/rmap.c near the check for
907 # should_defer_flush. The architecture should also consider if the full flush
908 # and the refill costs are offset by the savings of sending fewer IPIs.
909 config ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH
913 # For architectures that know their GCC __int128 support is sound
915 config ARCH_SUPPORTS_INT128
918 # For architectures that (ab)use NUMA to represent different memory regions
919 # all cpu-local but of different latencies, such as SuperH.
921 config ARCH_WANT_NUMA_VARIABLE_LOCALITY
924 config NUMA_BALANCING
925 bool "Memory placement aware NUMA scheduler"
926 depends on ARCH_SUPPORTS_NUMA_BALANCING
927 depends on !ARCH_WANT_NUMA_VARIABLE_LOCALITY
928 depends on SMP && NUMA && MIGRATION
930 This option adds support for automatic NUMA aware memory/task placement.
931 The mechanism is quite primitive and is based on migrating memory when
932 it has references to the node the task is running on.
934 This system will be inactive on UMA systems.
936 config NUMA_BALANCING_DEFAULT_ENABLED
937 bool "Automatically enable NUMA aware memory/task placement"
939 depends on NUMA_BALANCING
941 If set, automatic NUMA balancing will be enabled if running on a NUMA
945 bool "Control Group support"
948 This option adds support for grouping sets of processes together, for
949 use with process control subsystems such as Cpusets, CFS, memory
950 controls or device isolation.
952 - Documentation/scheduler/sched-design-CFS.txt (CFS)
953 - Documentation/cgroups/ (features for grouping, isolation
954 and resource control)
964 bool "Memory controller"
968 Provides control over the memory footprint of tasks in a cgroup.
971 bool "Swap controller"
972 depends on MEMCG && SWAP
974 Provides control over the swap space consumed by tasks in a cgroup.
976 config MEMCG_SWAP_ENABLED
977 bool "Swap controller enabled by default"
978 depends on MEMCG_SWAP
981 Memory Resource Controller Swap Extension comes with its price in
982 a bigger memory consumption. General purpose distribution kernels
983 which want to enable the feature but keep it disabled by default
984 and let the user enable it by swapaccount=1 boot command line
985 parameter should have this option unselected.
986 For those who want to have the feature enabled by default should
987 select this option (if, for some reason, they need to disable it
988 then swapaccount=0 does the trick).
995 Generic block IO controller cgroup interface. This is the common
996 cgroup interface which should be used by various IO controlling
999 Currently, CFQ IO scheduler uses it to recognize task groups and
1000 control disk bandwidth allocation (proportional time slice allocation)
1001 to such task groups. It is also used by bio throttling logic in
1002 block layer to implement upper limit in IO rates on a device.
1004 This option only enables generic Block IO controller infrastructure.
1005 One needs to also enable actual IO controlling logic/policy. For
1006 enabling proportional weight division of disk bandwidth in CFQ, set
1007 CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
1008 CONFIG_BLK_DEV_THROTTLING=y.
1010 See Documentation/cgroups/blkio-controller.txt for more information.
1012 config DEBUG_BLK_CGROUP
1013 bool "IO controller debugging"
1014 depends on BLK_CGROUP
1017 Enable some debugging help. Currently it exports additional stat
1018 files in a cgroup which can be useful for debugging.
1020 config CGROUP_WRITEBACK
1022 depends on MEMCG && BLK_CGROUP
1025 menuconfig CGROUP_SCHED
1026 bool "CPU controller"
1029 This feature lets CPU scheduler recognize task groups and control CPU
1030 bandwidth allocation to such task groups. It uses cgroups to group
1034 config FAIR_GROUP_SCHED
1035 bool "Group scheduling for SCHED_OTHER"
1036 depends on CGROUP_SCHED
1037 default CGROUP_SCHED
1039 config CFS_BANDWIDTH
1040 bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED"
1041 depends on FAIR_GROUP_SCHED
1044 This option allows users to define CPU bandwidth rates (limits) for
1045 tasks running within the fair group scheduler. Groups with no limit
1046 set are considered to be unconstrained and will run with no
1048 See tip/Documentation/scheduler/sched-bwc.txt for more information.
1050 config RT_GROUP_SCHED
1051 bool "Group scheduling for SCHED_RR/FIFO"
1052 depends on CGROUP_SCHED
1055 This feature lets you explicitly allocate real CPU bandwidth
1056 to task groups. If enabled, it will also make it impossible to
1057 schedule realtime tasks for non-root users until you allocate
1058 realtime bandwidth for them.
1059 See Documentation/scheduler/sched-rt-group.txt for more information.
1064 bool "PIDs controller"
1066 Provides enforcement of process number limits in the scope of a
1067 cgroup. Any attempt to fork more processes than is allowed in the
1068 cgroup will fail. PIDs are fundamentally a global resource because it
1069 is fairly trivial to reach PID exhaustion before you reach even a
1070 conservative kmemcg limit. As a result, it is possible to grind a
1071 system to halt without being limited by other cgroup policies. The
1072 PIDs cgroup subsystem is designed to stop this from happening.
1074 It should be noted that organisational operations (such as attaching
1075 to a cgroup hierarchy will *not* be blocked by the PIDs subsystem),
1076 since the PIDs limit only affects a process's ability to fork, not to
1079 config CGROUP_FREEZER
1080 bool "Freezer controller"
1082 Provides a way to freeze and unfreeze all tasks in a
1085 This option affects the ORIGINAL cgroup interface. The cgroup2 memory
1086 controller includes important in-kernel memory consumers per default.
1088 If you're using cgroup2, say N.
1090 config CGROUP_HUGETLB
1091 bool "HugeTLB controller"
1092 depends on HUGETLB_PAGE
1096 Provides a cgroup controller for HugeTLB pages.
1097 When you enable this, you can put a per cgroup limit on HugeTLB usage.
1098 The limit is enforced during page fault. Since HugeTLB doesn't
1099 support page reclaim, enforcing the limit at page fault time implies
1100 that, the application will get SIGBUS signal if it tries to access
1101 HugeTLB pages beyond its limit. This requires the application to know
1102 beforehand how much HugeTLB pages it would require for its use. The
1103 control group is tracked in the third page lru pointer. This means
1104 that we cannot use the controller with huge page less than 3 pages.
1107 bool "Cpuset controller"
1109 This option will let you create and manage CPUSETs which
1110 allow dynamically partitioning a system into sets of CPUs and
1111 Memory Nodes and assigning tasks to run only within those sets.
1112 This is primarily useful on large SMP or NUMA systems.
1116 config PROC_PID_CPUSET
1117 bool "Include legacy /proc/<pid>/cpuset file"
1121 config CGROUP_DEVICE
1122 bool "Device controller"
1124 Provides a cgroup controller implementing whitelists for
1125 devices which a process in the cgroup can mknod or open.
1127 config CGROUP_CPUACCT
1128 bool "Simple CPU accounting controller"
1130 Provides a simple controller for monitoring the
1131 total CPU consumed by the tasks in a cgroup.
1134 bool "Perf controller"
1135 depends on PERF_EVENTS
1137 This option extends the perf per-cpu mode to restrict monitoring
1138 to threads which belong to the cgroup specified and run on the
1144 bool "Example controller"
1147 This option enables a simple controller that exports
1148 debugging information about the cgroups framework.
1154 config CHECKPOINT_RESTORE
1155 bool "Checkpoint/restore support" if EXPERT
1156 select PROC_CHILDREN
1159 Enables additional kernel features in a sake of checkpoint/restore.
1160 In particular it adds auxiliary prctl codes to setup process text,
1161 data and heap segment sizes, and a few additional /proc filesystem
1164 If unsure, say N here.
1166 menuconfig NAMESPACES
1167 bool "Namespaces support" if EXPERT
1168 depends on MULTIUSER
1171 Provides the way to make tasks work with different objects using
1172 the same id. For example same IPC id may refer to different objects
1173 or same user id or pid may refer to different tasks when used in
1174 different namespaces.
1179 bool "UTS namespace"
1182 In this namespace tasks see different info provided with the
1186 bool "IPC namespace"
1187 depends on (SYSVIPC || POSIX_MQUEUE)
1190 In this namespace tasks work with IPC ids which correspond to
1191 different IPC objects in different namespaces.
1194 bool "User namespace"
1197 This allows containers, i.e. vservers, to use user namespaces
1198 to provide different user info for different servers.
1200 When user namespaces are enabled in the kernel it is
1201 recommended that the MEMCG option also be enabled and that
1202 user-space use the memory control groups to limit the amount
1203 of memory a memory unprivileged users can use.
1208 bool "PID Namespaces"
1211 Support process id namespaces. This allows having multiple
1212 processes with the same pid as long as they are in different
1213 pid namespaces. This is a building block of containers.
1216 bool "Network namespace"
1220 Allow user space to create what appear to be multiple instances
1221 of the network stack.
1225 config SCHED_AUTOGROUP
1226 bool "Automatic process group scheduling"
1229 select FAIR_GROUP_SCHED
1231 This option optimizes the scheduler for common desktop workloads by
1232 automatically creating and populating task groups. This separation
1233 of workloads isolates aggressive CPU burners (like build jobs) from
1234 desktop applications. Task group autogeneration is currently based
1237 config SYSFS_DEPRECATED
1238 bool "Enable deprecated sysfs features to support old userspace tools"
1242 This option adds code that switches the layout of the "block" class
1243 devices, to not show up in /sys/class/block/, but only in
1246 This switch is only active when the sysfs.deprecated=1 boot option is
1247 passed or the SYSFS_DEPRECATED_V2 option is set.
1249 This option allows new kernels to run on old distributions and tools,
1250 which might get confused by /sys/class/block/. Since 2007/2008 all
1251 major distributions and tools handle this just fine.
1253 Recent distributions and userspace tools after 2009/2010 depend on
1254 the existence of /sys/class/block/, and will not work with this
1257 Only if you are using a new kernel on an old distribution, you might
1260 config SYSFS_DEPRECATED_V2
1261 bool "Enable deprecated sysfs features by default"
1264 depends on SYSFS_DEPRECATED
1266 Enable deprecated sysfs by default.
1268 See the CONFIG_SYSFS_DEPRECATED option for more details about this
1271 Only if you are using a new kernel on an old distribution, you might
1272 need to say Y here. Even then, odds are you would not need it
1273 enabled, you can always pass the boot option if absolutely necessary.
1276 bool "Kernel->user space relay support (formerly relayfs)"
1278 This option enables support for relay interface support in
1279 certain file systems (such as debugfs).
1280 It is designed to provide an efficient mechanism for tools and
1281 facilities to relay large amounts of data from kernel space to
1286 config BLK_DEV_INITRD
1287 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
1288 depends on BROKEN || !FRV
1290 The initial RAM filesystem is a ramfs which is loaded by the
1291 boot loader (loadlin or lilo) and that is mounted as root
1292 before the normal boot procedure. It is typically used to
1293 load modules needed to mount the "real" root file system,
1294 etc. See <file:Documentation/initrd.txt> for details.
1296 If RAM disk support (BLK_DEV_RAM) is also included, this
1297 also enables initial RAM disk (initrd) support and adds
1298 15 Kbytes (more on some other architectures) to the kernel size.
1304 source "usr/Kconfig"
1308 config CC_OPTIMIZE_FOR_SIZE
1309 bool "Optimize for size"
1311 Enabling this option will pass "-Os" instead of "-O2" to
1312 your compiler resulting in a smaller kernel.
1325 config SYSCTL_EXCEPTION_TRACE
1328 Enable support for /proc/sys/debug/exception-trace.
1330 config SYSCTL_ARCH_UNALIGN_NO_WARN
1333 Enable support for /proc/sys/kernel/ignore-unaligned-usertrap
1334 Allows arch to define/use @no_unaligned_warning to possibly warn
1335 about unaligned access emulation going on under the hood.
1337 config SYSCTL_ARCH_UNALIGN_ALLOW
1340 Enable support for /proc/sys/kernel/unaligned-trap
1341 Allows arches to define/use @unaligned_enabled to runtime toggle
1342 the unaligned access emulation.
1343 see arch/parisc/kernel/unaligned.c for reference
1345 config HAVE_PCSPKR_PLATFORM
1348 # interpreter that classic socket filters depend on
1353 bool "Configure standard kernel features (expert users)"
1354 # Unhide debug options, to make the on-by-default options visible
1357 This option allows certain base kernel options and settings
1358 to be disabled or tweaked. This is for specialized
1359 environments which can tolerate a "non-standard" kernel.
1360 Only use this if you really know what you are doing.
1363 bool "Enable 16-bit UID system calls" if EXPERT
1364 depends on HAVE_UID16 && MULTIUSER
1367 This enables the legacy 16-bit UID syscall wrappers.
1370 bool "Multiple users, groups and capabilities support" if EXPERT
1373 This option enables support for non-root users, groups and
1376 If you say N here, all processes will run with UID 0, GID 0, and all
1377 possible capabilities. Saying N here also compiles out support for
1378 system calls related to UIDs, GIDs, and capabilities, such as setuid,
1381 If unsure, say Y here.
1383 config SGETMASK_SYSCALL
1384 bool "sgetmask/ssetmask syscalls support" if EXPERT
1385 def_bool PARISC || MN10300 || BLACKFIN || M68K || PPC || MIPS || X86 || SPARC || CRIS || MICROBLAZE || SUPERH
1387 sys_sgetmask and sys_ssetmask are obsolete system calls
1388 no longer supported in libc but still enabled by default in some
1391 If unsure, leave the default option here.
1393 config SYSFS_SYSCALL
1394 bool "Sysfs syscall support" if EXPERT
1397 sys_sysfs is an obsolete system call no longer supported in libc.
1398 Note that disabling this option is more secure but might break
1399 compatibility with some systems.
1401 If unsure say Y here.
1403 config SYSCTL_SYSCALL
1404 bool "Sysctl syscall support" if EXPERT
1405 depends on PROC_SYSCTL
1409 sys_sysctl uses binary paths that have been found challenging
1410 to properly maintain and use. The interface in /proc/sys
1411 using paths with ascii names is now the primary path to this
1414 Almost nothing using the binary sysctl interface so if you are
1415 trying to save some space it is probably safe to disable this,
1416 making your kernel marginally smaller.
1418 If unsure say N here.
1421 bool "Load all symbols for debugging/ksymoops" if EXPERT
1424 Say Y here to let the kernel print out symbolic crash information and
1425 symbolic stack backtraces. This increases the size of the kernel
1426 somewhat, as all symbols have to be loaded into the kernel image.
1429 bool "Include all symbols in kallsyms"
1430 depends on DEBUG_KERNEL && KALLSYMS
1432 Normally kallsyms only contains the symbols of functions for nicer
1433 OOPS messages and backtraces (i.e., symbols from the text and inittext
1434 sections). This is sufficient for most cases. And only in very rare
1435 cases (e.g., when a debugger is used) all symbols are required (e.g.,
1436 names of variables from the data sections, etc).
1438 This option makes sure that all symbols are loaded into the kernel
1439 image (i.e., symbols from all sections) in cost of increased kernel
1440 size (depending on the kernel configuration, it may be 300KiB or
1441 something like this).
1443 Say N unless you really need all symbols.
1445 config KALLSYMS_ABSOLUTE_PERCPU
1447 default X86_64 && SMP
1449 config KALLSYMS_BASE_RELATIVE
1452 default !IA64 && !(TILE && 64BIT)
1454 Instead of emitting them as absolute values in the native word size,
1455 emit the symbol references in the kallsyms table as 32-bit entries,
1456 each containing a relative value in the range [base, base + U32_MAX]
1457 or, when KALLSYMS_ABSOLUTE_PERCPU is in effect, each containing either
1458 an absolute value in the range [0, S32_MAX] or a relative value in the
1459 range [base, base + S32_MAX], where base is the lowest relative symbol
1460 address encountered in the image.
1462 On 64-bit builds, this reduces the size of the address table by 50%,
1463 but more importantly, it results in entries whose values are build
1464 time constants, and no relocation pass is required at runtime to fix
1465 up the entries based on the runtime load address of the kernel.
1469 bool "Enable support for printk" if EXPERT
1472 This option enables normal printk support. Removing it
1473 eliminates most of the message strings from the kernel image
1474 and makes the kernel more or less silent. As this makes it
1475 very difficult to diagnose system problems, saying N here is
1476 strongly discouraged.
1484 bool "BUG() support" if EXPERT
1487 Disabling this option eliminates support for BUG and WARN, reducing
1488 the size of your kernel image and potentially quietly ignoring
1489 numerous fatal conditions. You should only consider disabling this
1490 option for embedded systems with no facilities for reporting errors.
1496 bool "Enable ELF core dumps" if EXPERT
1498 Enable support for generating core dumps. Disabling saves about 4k.
1501 config PCSPKR_PLATFORM
1502 bool "Enable PC-Speaker support" if EXPERT
1503 depends on HAVE_PCSPKR_PLATFORM
1507 This option allows to disable the internal PC-Speaker
1508 support, saving some memory.
1512 bool "Enable full-sized data structures for core" if EXPERT
1514 Disabling this option reduces the size of miscellaneous core
1515 kernel data structures. This saves memory on small machines,
1516 but may reduce performance.
1519 bool "Enable futex support" if EXPERT
1523 Disabling this option will cause the kernel to be built without
1524 support for "fast userspace mutexes". The resulting kernel may not
1525 run glibc-based applications correctly.
1527 config HAVE_FUTEX_CMPXCHG
1531 Architectures should select this if futex_atomic_cmpxchg_inatomic()
1532 is implemented and always working. This removes a couple of runtime
1536 bool "Enable eventpoll support" if EXPERT
1540 Disabling this option will cause the kernel to be built without
1541 support for epoll family of system calls.
1544 bool "Enable signalfd() system call" if EXPERT
1548 Enable the signalfd() system call that allows to receive signals
1549 on a file descriptor.
1554 bool "Enable timerfd() system call" if EXPERT
1558 Enable the timerfd() system call that allows to receive timer
1559 events on a file descriptor.
1564 bool "Enable eventfd() system call" if EXPERT
1568 Enable the eventfd() system call that allows to receive both
1569 kernel notification (ie. KAIO) or userspace notifications.
1573 # syscall, maps, verifier
1575 bool "Enable bpf() system call"
1580 Enable the bpf() system call that allows to manipulate eBPF
1581 programs and maps via file descriptors.
1584 bool "Use full shmem filesystem" if EXPERT
1588 The shmem is an internal filesystem used to manage shared memory.
1589 It is backed by swap and manages resource limits. It is also exported
1590 to userspace as tmpfs if TMPFS is enabled. Disabling this
1591 option replaces shmem and tmpfs with the much simpler ramfs code,
1592 which may be appropriate on small systems without swap.
1595 bool "Enable AIO support" if EXPERT
1598 This option enables POSIX asynchronous I/O which may by used
1599 by some high performance threaded applications. Disabling
1600 this option saves about 7k.
1603 bool "Support kernel thread based AIO" if EXPERT
1607 This option enables using kernel thread based AIO which implements
1608 asynchronous operations using the kernel's queue_work() mechanism.
1609 The automatic use of threads for async operations is currently
1610 disabled by default until the security implications for usage
1611 are completely understood. This functionality can be enabled at
1612 runtime if this option is enabled by setting the fs.aio-auto-threads
1615 config ADVISE_SYSCALLS
1616 bool "Enable madvise/fadvise syscalls" if EXPERT
1619 This option enables the madvise and fadvise syscalls, used by
1620 applications to advise the kernel about their future memory or file
1621 usage, improving performance. If building an embedded system where no
1622 applications use these syscalls, you can disable this option to save
1626 bool "Enable userfaultfd() system call"
1630 Enable the userfaultfd() system call that allows to intercept and
1631 handle page faults in userland.
1635 bool "Enable PCI quirk workarounds" if EXPERT
1638 This enables workarounds for various PCI chipset
1639 bugs/quirks. Disable this only if your target machine is
1640 unaffected by PCI quirks.
1643 bool "Enable membarrier() system call" if EXPERT
1646 Enable the membarrier() system call that allows issuing memory
1647 barriers across all running threads, which can be used to distribute
1648 the cost of user-space memory barriers asymmetrically by transforming
1649 pairs of memory barriers into pairs consisting of membarrier() and a
1655 bool "Embedded system"
1656 option allnoconfig_y
1659 This option should be enabled if compiling the kernel for
1660 an embedded system so certain expert options are available
1663 config HAVE_PERF_EVENTS
1666 See tools/perf/design.txt for details.
1668 config PERF_USE_VMALLOC
1671 See tools/perf/design.txt for details
1673 menu "Kernel Performance Events And Counters"
1676 bool "Kernel performance events and counters"
1677 default y if PROFILING
1678 depends on HAVE_PERF_EVENTS
1683 Enable kernel support for various performance events provided
1684 by software and hardware.
1686 Software events are supported either built-in or via the
1687 use of generic tracepoints.
1689 Most modern CPUs support performance events via performance
1690 counter registers. These registers count the number of certain
1691 types of hw events: such as instructions executed, cachemisses
1692 suffered, or branches mis-predicted - without slowing down the
1693 kernel or applications. These registers can also trigger interrupts
1694 when a threshold number of events have passed - and can thus be
1695 used to profile the code that runs on that CPU.
1697 The Linux Performance Event subsystem provides an abstraction of
1698 these software and hardware event capabilities, available via a
1699 system call and used by the "perf" utility in tools/perf/. It
1700 provides per task and per CPU counters, and it provides event
1701 capabilities on top of those.
1705 config DEBUG_PERF_USE_VMALLOC
1707 bool "Debug: use vmalloc to back perf mmap() buffers"
1708 depends on PERF_EVENTS && DEBUG_KERNEL && !PPC
1709 select PERF_USE_VMALLOC
1711 Use vmalloc memory to back perf mmap() buffers.
1713 Mostly useful for debugging the vmalloc code on platforms
1714 that don't require it.
1720 config VM_EVENT_COUNTERS
1722 bool "Enable VM event counters for /proc/vmstat" if EXPERT
1724 VM event counters are needed for event counts to be shown.
1725 This option allows the disabling of the VM event counters
1726 on EXPERT systems. /proc/vmstat will only show page counts
1727 if VM event counters are disabled.
1731 bool "Enable SLUB debugging support" if EXPERT
1732 depends on SLUB && SYSFS
1734 SLUB has extensive debug support features. Disabling these can
1735 result in significant savings in code size. This also disables
1736 SLUB sysfs support. /sys/slab will not exist and there will be
1737 no support for cache validation etc.
1740 bool "Disable heap randomization"
1743 Randomizing heap placement makes heap exploits harder, but it
1744 also breaks ancient binaries (including anything libc5 based).
1745 This option changes the bootup default to heap randomization
1746 disabled, and can be overridden at runtime by setting
1747 /proc/sys/kernel/randomize_va_space to 2.
1749 On non-ancient distros (post-2000 ones) N is usually a safe choice.
1752 prompt "Choose SLAB allocator"
1755 This option allows to select a slab allocator.
1760 The regular slab allocator that is established and known to work
1761 well in all environments. It organizes cache hot objects in
1762 per cpu and per node queues.
1765 bool "SLUB (Unqueued Allocator)"
1767 SLUB is a slab allocator that minimizes cache line usage
1768 instead of managing queues of cached objects (SLAB approach).
1769 Per cpu caching is realized using slabs of objects instead
1770 of queues of objects. SLUB can use memory efficiently
1771 and has enhanced diagnostics. SLUB is the default choice for
1776 bool "SLOB (Simple Allocator)"
1778 SLOB replaces the stock allocator with a drastically simpler
1779 allocator. SLOB is generally more space efficient but
1780 does not perform as well on large systems.
1784 config SLUB_CPU_PARTIAL
1786 depends on SLUB && SMP
1787 bool "SLUB per cpu partial cache"
1789 Per cpu partial caches accellerate objects allocation and freeing
1790 that is local to a processor at the price of more indeterminism
1791 in the latency of the free. On overflow these caches will be cleared
1792 which requires the taking of locks that may cause latency spikes.
1793 Typically one would choose no for a realtime system.
1795 config MMAP_ALLOW_UNINITIALIZED
1796 bool "Allow mmapped anonymous memory to be uninitialized"
1797 depends on EXPERT && !MMU
1800 Normally, and according to the Linux spec, anonymous memory obtained
1801 from mmap() has it's contents cleared before it is passed to
1802 userspace. Enabling this config option allows you to request that
1803 mmap() skip that if it is given an MAP_UNINITIALIZED flag, thus
1804 providing a huge performance boost. If this option is not enabled,
1805 then the flag will be ignored.
1807 This is taken advantage of by uClibc's malloc(), and also by
1808 ELF-FDPIC binfmt's brk and stack allocator.
1810 Because of the obvious security issues, this option should only be
1811 enabled on embedded devices where you control what is run in
1812 userspace. Since that isn't generally a problem on no-MMU systems,
1813 it is normally safe to say Y here.
1815 See Documentation/nommu-mmap.txt for more information.
1817 config SYSTEM_DATA_VERIFICATION
1819 select SYSTEM_TRUSTED_KEYRING
1822 select ASYMMETRIC_KEY_TYPE
1823 select ASYMMETRIC_PUBLIC_KEY_SUBTYPE
1824 select PUBLIC_KEY_ALGO_RSA
1827 select X509_CERTIFICATE_PARSER
1828 select PKCS7_MESSAGE_PARSER
1830 Provide PKCS#7 message verification using the contents of the system
1831 trusted keyring to provide public keys. This then can be used for
1832 module verification, kexec image verification and firmware blob
1836 bool "Profiling support"
1838 Say Y here to enable the extended profiling support mechanisms used
1839 by profilers such as OProfile.
1842 # Place an empty function call at each tracepoint site. Can be
1843 # dynamically changed for a probe function.
1848 source "arch/Kconfig"
1850 endmenu # General setup
1852 config HAVE_GENERIC_DMA_COHERENT
1859 depends on SLAB || SLUB_DEBUG
1867 default 0 if BASE_FULL
1868 default 1 if !BASE_FULL
1871 bool "Enable loadable module support"
1874 Kernel modules are small pieces of compiled code which can
1875 be inserted in the running kernel, rather than being
1876 permanently built into the kernel. You use the "modprobe"
1877 tool to add (and sometimes remove) them. If you say Y here,
1878 many parts of the kernel can be built as modules (by
1879 answering M instead of Y where indicated): this is most
1880 useful for infrequently used options which are not required
1881 for booting. For more information, see the man pages for
1882 modprobe, lsmod, modinfo, insmod and rmmod.
1884 If you say Y here, you will need to run "make
1885 modules_install" to put the modules under /lib/modules/
1886 where modprobe can find them (you may need to be root to do
1893 config MODULE_FORCE_LOAD
1894 bool "Forced module loading"
1897 Allow loading of modules without version information (ie. modprobe
1898 --force). Forced module loading sets the 'F' (forced) taint flag and
1899 is usually a really bad idea.
1901 config MODULE_UNLOAD
1902 bool "Module unloading"
1904 Without this option you will not be able to unload any
1905 modules (note that some modules may not be unloadable
1906 anyway), which makes your kernel smaller, faster
1907 and simpler. If unsure, say Y.
1909 config MODULE_FORCE_UNLOAD
1910 bool "Forced module unloading"
1911 depends on MODULE_UNLOAD
1913 This option allows you to force a module to unload, even if the
1914 kernel believes it is unsafe: the kernel will remove the module
1915 without waiting for anyone to stop using it (using the -f option to
1916 rmmod). This is mainly for kernel developers and desperate users.
1920 bool "Module versioning support"
1922 Usually, you have to use modules compiled with your kernel.
1923 Saying Y here makes it sometimes possible to use modules
1924 compiled for different kernels, by adding enough information
1925 to the modules to (hopefully) spot any changes which would
1926 make them incompatible with the kernel you are running. If
1929 config MODULE_SRCVERSION_ALL
1930 bool "Source checksum for all modules"
1932 Modules which contain a MODULE_VERSION get an extra "srcversion"
1933 field inserted into their modinfo section, which contains a
1934 sum of the source files which made it. This helps maintainers
1935 see exactly which source was used to build a module (since
1936 others sometimes change the module source without updating
1937 the version). With this option, such a "srcversion" field
1938 will be created for all modules. If unsure, say N.
1941 bool "Module signature verification"
1943 select SYSTEM_DATA_VERIFICATION
1945 Check modules for valid signatures upon load: the signature
1946 is simply appended to the module. For more information see
1947 Documentation/module-signing.txt.
1949 Note that this option adds the OpenSSL development packages as a
1950 kernel build dependency so that the signing tool can use its crypto
1953 !!!WARNING!!! If you enable this option, you MUST make sure that the
1954 module DOES NOT get stripped after being signed. This includes the
1955 debuginfo strip done by some packagers (such as rpmbuild) and
1956 inclusion into an initramfs that wants the module size reduced.
1958 config MODULE_SIG_FORCE
1959 bool "Require modules to be validly signed"
1960 depends on MODULE_SIG
1962 Reject unsigned modules or signed modules for which we don't have a
1963 key. Without this, such modules will simply taint the kernel.
1965 config MODULE_SIG_ALL
1966 bool "Automatically sign all modules"
1968 depends on MODULE_SIG
1970 Sign all modules during make modules_install. Without this option,
1971 modules must be signed manually, using the scripts/sign-file tool.
1973 comment "Do not forget to sign required modules with scripts/sign-file"
1974 depends on MODULE_SIG_FORCE && !MODULE_SIG_ALL
1977 prompt "Which hash algorithm should modules be signed with?"
1978 depends on MODULE_SIG
1980 This determines which sort of hashing algorithm will be used during
1981 signature generation. This algorithm _must_ be built into the kernel
1982 directly so that signature verification can take place. It is not
1983 possible to load a signed module containing the algorithm to check
1984 the signature on that module.
1986 config MODULE_SIG_SHA1
1987 bool "Sign modules with SHA-1"
1990 config MODULE_SIG_SHA224
1991 bool "Sign modules with SHA-224"
1992 select CRYPTO_SHA256
1994 config MODULE_SIG_SHA256
1995 bool "Sign modules with SHA-256"
1996 select CRYPTO_SHA256
1998 config MODULE_SIG_SHA384
1999 bool "Sign modules with SHA-384"
2000 select CRYPTO_SHA512
2002 config MODULE_SIG_SHA512
2003 bool "Sign modules with SHA-512"
2004 select CRYPTO_SHA512
2008 config MODULE_SIG_HASH
2010 depends on MODULE_SIG
2011 default "sha1" if MODULE_SIG_SHA1
2012 default "sha224" if MODULE_SIG_SHA224
2013 default "sha256" if MODULE_SIG_SHA256
2014 default "sha384" if MODULE_SIG_SHA384
2015 default "sha512" if MODULE_SIG_SHA512
2017 config MODULE_COMPRESS
2018 bool "Compress modules on installation"
2022 Compresses kernel modules when 'make modules_install' is run; gzip or
2023 xz depending on "Compression algorithm" below.
2025 module-init-tools MAY support gzip, and kmod MAY support gzip and xz.
2027 Out-of-tree kernel modules installed using Kbuild will also be
2028 compressed upon installation.
2030 Note: for modules inside an initrd or initramfs, it's more efficient
2031 to compress the whole initrd or initramfs instead.
2033 Note: This is fully compatible with signed modules.
2038 prompt "Compression algorithm"
2039 depends on MODULE_COMPRESS
2040 default MODULE_COMPRESS_GZIP
2042 This determines which sort of compression will be used during
2043 'make modules_install'.
2045 GZIP (default) and XZ are supported.
2047 config MODULE_COMPRESS_GZIP
2050 config MODULE_COMPRESS_XZ
2057 config MODULES_TREE_LOOKUP
2059 depends on PERF_EVENTS || TRACING
2061 config INIT_ALL_POSSIBLE
2064 Back when each arch used to define their own cpu_online_mask and
2065 cpu_possible_mask, some of them chose to initialize cpu_possible_mask
2066 with all 1s, and others with all 0s. When they were centralised,
2067 it was better to provide this option than to break all the archs
2068 and have several arch maintainers pursuing me down dark alleys.
2070 source "block/Kconfig"
2072 config PREEMPT_NOTIFIERS
2079 # Can be selected by architectures with broken toolchains
2080 # that get confused by correct const<->read_only section
2082 config BROKEN_RODATA
2088 Build a simple ASN.1 grammar compiler that produces a bytecode output
2089 that can be interpreted by the ASN.1 stream decoder and used to
2090 inform it as to what tags are to be expected in a stream and what
2091 functions to call on what tags.
2093 source "kernel/Kconfig.locks"
projects / karo-tx-linux.git / blob