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"
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). Does not do system-call
303 auditing without CONFIG_AUDITSYSCALL.
305 config HAVE_ARCH_AUDITSYSCALL
309 bool "Enable system-call auditing support"
310 depends on AUDIT && HAVE_ARCH_AUDITSYSCALL
311 default y if SECURITY_SELINUX
313 Enable low-overhead system-call auditing infrastructure that
314 can be used independently or with another kernel subsystem,
319 depends on AUDITSYSCALL
324 depends on AUDITSYSCALL
327 source "kernel/irq/Kconfig"
328 source "kernel/time/Kconfig"
330 menu "CPU/Task time and stats accounting"
332 config VIRT_CPU_ACCOUNTING
336 prompt "Cputime accounting"
337 default TICK_CPU_ACCOUNTING if !PPC64
338 default VIRT_CPU_ACCOUNTING_NATIVE if PPC64
340 # Kind of a stub config for the pure tick based cputime accounting
341 config TICK_CPU_ACCOUNTING
342 bool "Simple tick based cputime accounting"
343 depends on !S390 && !NO_HZ_FULL
345 This is the basic tick based cputime accounting that maintains
346 statistics about user, system and idle time spent on per jiffies
351 config VIRT_CPU_ACCOUNTING_NATIVE
352 bool "Deterministic task and CPU time accounting"
353 depends on HAVE_VIRT_CPU_ACCOUNTING && !NO_HZ_FULL
354 select VIRT_CPU_ACCOUNTING
356 Select this option to enable more accurate task and CPU time
357 accounting. This is done by reading a CPU counter on each
358 kernel entry and exit and on transitions within the kernel
359 between system, softirq and hardirq state, so there is a
360 small performance impact. In the case of s390 or IBM POWER > 5,
361 this also enables accounting of stolen time on logically-partitioned
364 config VIRT_CPU_ACCOUNTING_GEN
365 bool "Full dynticks CPU time accounting"
366 depends on HAVE_CONTEXT_TRACKING
367 depends on HAVE_VIRT_CPU_ACCOUNTING_GEN
368 select VIRT_CPU_ACCOUNTING
369 select CONTEXT_TRACKING
371 Select this option to enable task and CPU time accounting on full
372 dynticks systems. This accounting is implemented by watching every
373 kernel-user boundaries using the context tracking subsystem.
374 The accounting is thus performed at the expense of some significant
377 For now this is only useful if you are working on the full
378 dynticks subsystem development.
382 config IRQ_TIME_ACCOUNTING
383 bool "Fine granularity task level IRQ time accounting"
384 depends on HAVE_IRQ_TIME_ACCOUNTING && !NO_HZ_FULL
386 Select this option to enable fine granularity task irq time
387 accounting. This is done by reading a timestamp on each
388 transitions between softirq and hardirq state, so there can be a
389 small performance impact.
391 If in doubt, say N here.
395 config BSD_PROCESS_ACCT
396 bool "BSD Process Accounting"
398 If you say Y here, a user level program will be able to instruct the
399 kernel (via a special system call) to write process accounting
400 information to a file: whenever a process exits, information about
401 that process will be appended to the file by the kernel. The
402 information includes things such as creation time, owning user,
403 command name, memory usage, controlling terminal etc. (the complete
404 list is in the struct acct in <file:include/linux/acct.h>). It is
405 up to the user level program to do useful things with this
406 information. This is generally a good idea, so say Y.
408 config BSD_PROCESS_ACCT_V3
409 bool "BSD Process Accounting version 3 file format"
410 depends on BSD_PROCESS_ACCT
413 If you say Y here, the process accounting information is written
414 in a new file format that also logs the process IDs of each
415 process and it's parent. Note that this file format is incompatible
416 with previous v0/v1/v2 file formats, so you will need updated tools
417 for processing it. A preliminary version of these tools is available
418 at <http://www.gnu.org/software/acct/>.
421 bool "Export task/process statistics through netlink"
425 Export selected statistics for tasks/processes through the
426 generic netlink interface. Unlike BSD process accounting, the
427 statistics are available during the lifetime of tasks/processes as
428 responses to commands. Like BSD accounting, they are sent to user
433 config TASK_DELAY_ACCT
434 bool "Enable per-task delay accounting"
437 Collect information on time spent by a task waiting for system
438 resources like cpu, synchronous block I/O completion and swapping
439 in pages. Such statistics can help in setting a task's priorities
440 relative to other tasks for cpu, io, rss limits etc.
445 bool "Enable extended accounting over taskstats"
448 Collect extended task accounting data and send the data
449 to userland for processing over the taskstats interface.
453 config TASK_IO_ACCOUNTING
454 bool "Enable per-task storage I/O accounting"
455 depends on TASK_XACCT
457 Collect information on the number of bytes of storage I/O which this
462 endmenu # "CPU/Task time and stats accounting"
467 prompt "RCU Implementation"
471 bool "Tree-based hierarchical RCU"
472 depends on !PREEMPT && SMP
475 This option selects the RCU implementation that is
476 designed for very large SMP system with hundreds or
477 thousands of CPUs. It also scales down nicely to
480 config TREE_PREEMPT_RCU
481 bool "Preemptible tree-based hierarchical RCU"
485 This option selects the RCU implementation that is
486 designed for very large SMP systems with hundreds or
487 thousands of CPUs, but for which real-time response
488 is also required. It also scales down nicely to
491 Select this option if you are unsure.
494 bool "UP-only small-memory-footprint RCU"
495 depends on !PREEMPT && !SMP
497 This option selects the RCU implementation that is
498 designed for UP systems from which real-time response
499 is not required. This option greatly reduces the
500 memory footprint of RCU.
505 def_bool TREE_PREEMPT_RCU
507 This option enables preemptible-RCU code that is common between
508 TREE_PREEMPT_RCU and, in the old days, TINY_PREEMPT_RCU.
511 bool "Task_based RCU implementation using voluntary context switch"
514 This option enables a task-based RCU implementation that uses
515 only voluntary context switch (not preemption!), idle, and
516 user-mode execution as quiescent states.
520 config RCU_STALL_COMMON
521 def_bool ( TREE_RCU || TREE_PREEMPT_RCU || RCU_TRACE )
523 This option enables RCU CPU stall code that is common between
524 the TINY and TREE variants of RCU. The purpose is to allow
525 the tiny variants to disable RCU CPU stall warnings, while
526 making these warnings mandatory for the tree variants.
528 config CONTEXT_TRACKING
532 bool "Consider userspace as in RCU extended quiescent state"
533 depends on HAVE_CONTEXT_TRACKING && SMP
534 select CONTEXT_TRACKING
536 This option sets hooks on kernel / userspace boundaries and
537 puts RCU in extended quiescent state when the CPU runs in
538 userspace. It means that when a CPU runs in userspace, it is
539 excluded from the global RCU state machine and thus doesn't
540 try to keep the timer tick on for RCU.
542 Unless you want to hack and help the development of the full
543 dynticks mode, you shouldn't enable this option. It also
544 adds unnecessary overhead.
548 config CONTEXT_TRACKING_FORCE
549 bool "Force context tracking"
550 depends on CONTEXT_TRACKING
551 default y if !NO_HZ_FULL
553 The major pre-requirement for full dynticks to work is to
554 support the context tracking subsystem. But there are also
555 other dependencies to provide in order to make the full
558 This option stands for testing when an arch implements the
559 context tracking backend but doesn't yet fullfill all the
560 requirements to make the full dynticks feature working.
561 Without the full dynticks, there is no way to test the support
562 for context tracking and the subsystems that rely on it: RCU
563 userspace extended quiescent state and tickless cputime
564 accounting. This option copes with the absence of the full
565 dynticks subsystem by forcing the context tracking on all
568 Say Y only if you're working on the development of an
569 architecture backend for the context tracking.
571 Say N otherwise, this option brings an overhead that you
572 don't want in production.
576 int "Tree-based hierarchical RCU fanout value"
579 depends on TREE_RCU || TREE_PREEMPT_RCU
583 This option controls the fanout of hierarchical implementations
584 of RCU, allowing RCU to work efficiently on machines with
585 large numbers of CPUs. This value must be at least the fourth
586 root of NR_CPUS, which allows NR_CPUS to be insanely large.
587 The default value of RCU_FANOUT should be used for production
588 systems, but if you are stress-testing the RCU implementation
589 itself, small RCU_FANOUT values allow you to test large-system
590 code paths on small(er) systems.
592 Select a specific number if testing RCU itself.
593 Take the default if unsure.
595 config RCU_FANOUT_LEAF
596 int "Tree-based hierarchical RCU leaf-level fanout value"
597 range 2 RCU_FANOUT if 64BIT
598 range 2 RCU_FANOUT if !64BIT
599 depends on TREE_RCU || TREE_PREEMPT_RCU
602 This option controls the leaf-level fanout of hierarchical
603 implementations of RCU, and allows trading off cache misses
604 against lock contention. Systems that synchronize their
605 scheduling-clock interrupts for energy-efficiency reasons will
606 want the default because the smaller leaf-level fanout keeps
607 lock contention levels acceptably low. Very large systems
608 (hundreds or thousands of CPUs) will instead want to set this
609 value to the maximum value possible in order to reduce the
610 number of cache misses incurred during RCU's grace-period
611 initialization. These systems tend to run CPU-bound, and thus
612 are not helped by synchronized interrupts, and thus tend to
613 skew them, which reduces lock contention enough that large
614 leaf-level fanouts work well.
616 Select a specific number if testing RCU itself.
618 Select the maximum permissible value for large systems.
620 Take the default if unsure.
622 config RCU_FANOUT_EXACT
623 bool "Disable tree-based hierarchical RCU auto-balancing"
624 depends on TREE_RCU || TREE_PREEMPT_RCU
627 This option forces use of the exact RCU_FANOUT value specified,
628 regardless of imbalances in the hierarchy. This is useful for
629 testing RCU itself, and might one day be useful on systems with
630 strong NUMA behavior.
632 Without RCU_FANOUT_EXACT, the code will balance the hierarchy.
636 config RCU_FAST_NO_HZ
637 bool "Accelerate last non-dyntick-idle CPU's grace periods"
638 depends on NO_HZ_COMMON && SMP
641 This option permits CPUs to enter dynticks-idle state even if
642 they have RCU callbacks queued, and prevents RCU from waking
643 these CPUs up more than roughly once every four jiffies (by
644 default, you can adjust this using the rcutree.rcu_idle_gp_delay
645 parameter), thus improving energy efficiency. On the other
646 hand, this option increases the duration of RCU grace periods,
647 for example, slowing down synchronize_rcu().
649 Say Y if energy efficiency is critically important, and you
650 don't care about increased grace-period durations.
652 Say N if you are unsure.
654 config TREE_RCU_TRACE
655 def_bool RCU_TRACE && ( TREE_RCU || TREE_PREEMPT_RCU )
658 This option provides tracing for the TREE_RCU and
659 TREE_PREEMPT_RCU implementations, permitting Makefile to
660 trivially select kernel/rcutree_trace.c.
663 bool "Enable RCU priority boosting"
664 depends on RT_MUTEXES && PREEMPT_RCU
667 This option boosts the priority of preempted RCU readers that
668 block the current preemptible RCU grace period for too long.
669 This option also prevents heavy loads from blocking RCU
670 callback invocation for all flavors of RCU.
672 Say Y here if you are working with real-time apps or heavy loads
673 Say N here if you are unsure.
675 config RCU_BOOST_PRIO
676 int "Real-time priority to boost RCU readers to"
681 This option specifies the real-time priority to which long-term
682 preempted RCU readers are to be boosted. If you are working
683 with a real-time application that has one or more CPU-bound
684 threads running at a real-time priority level, you should set
685 RCU_BOOST_PRIO to a priority higher then the highest-priority
686 real-time CPU-bound thread. The default RCU_BOOST_PRIO value
687 of 1 is appropriate in the common case, which is real-time
688 applications that do not have any CPU-bound threads.
690 Some real-time applications might not have a single real-time
691 thread that saturates a given CPU, but instead might have
692 multiple real-time threads that, taken together, fully utilize
693 that CPU. In this case, you should set RCU_BOOST_PRIO to
694 a priority higher than the lowest-priority thread that is
695 conspiring to prevent the CPU from running any non-real-time
696 tasks. For example, if one thread at priority 10 and another
697 thread at priority 5 are between themselves fully consuming
698 the CPU time on a given CPU, then RCU_BOOST_PRIO should be
699 set to priority 6 or higher.
701 Specify the real-time priority, or take the default if unsure.
703 config RCU_BOOST_DELAY
704 int "Milliseconds to delay boosting after RCU grace-period start"
709 This option specifies the time to wait after the beginning of
710 a given grace period before priority-boosting preempted RCU
711 readers blocking that grace period. Note that any RCU reader
712 blocking an expedited RCU grace period is boosted immediately.
714 Accept the default if unsure.
717 bool "Offload RCU callback processing from boot-selected CPUs"
718 depends on TREE_RCU || TREE_PREEMPT_RCU
721 Use this option to reduce OS jitter for aggressive HPC or
722 real-time workloads. It can also be used to offload RCU
723 callback invocation to energy-efficient CPUs in battery-powered
724 asymmetric multiprocessors.
726 This option offloads callback invocation from the set of
727 CPUs specified at boot time by the rcu_nocbs parameter.
728 For each such CPU, a kthread ("rcuox/N") will be created to
729 invoke callbacks, where the "N" is the CPU being offloaded,
730 and where the "x" is "b" for RCU-bh, "p" for RCU-preempt, and
731 "s" for RCU-sched. Nothing prevents this kthread from running
732 on the specified CPUs, but (1) the kthreads may be preempted
733 between each callback, and (2) affinity or cgroups can be used
734 to force the kthreads to run on whatever set of CPUs is desired.
736 Say Y here if you want to help to debug reduced OS jitter.
737 Say N here if you are unsure.
740 prompt "Build-forced no-CBs CPUs"
741 default RCU_NOCB_CPU_NONE
743 This option allows no-CBs CPUs (whose RCU callbacks are invoked
744 from kthreads rather than from softirq context) to be specified
745 at build time. Additional no-CBs CPUs may be specified by
746 the rcu_nocbs= boot parameter.
748 config RCU_NOCB_CPU_NONE
749 bool "No build_forced no-CBs CPUs"
750 depends on RCU_NOCB_CPU
752 This option does not force any of the CPUs to be no-CBs CPUs.
753 Only CPUs designated by the rcu_nocbs= boot parameter will be
754 no-CBs CPUs, whose RCU callbacks will be invoked by per-CPU
755 kthreads whose names begin with "rcuo". All other CPUs will
756 invoke their own RCU callbacks in softirq context.
758 Select this option if you want to choose no-CBs CPUs at
759 boot time, for example, to allow testing of different no-CBs
760 configurations without having to rebuild the kernel each time.
762 config RCU_NOCB_CPU_ZERO
763 bool "CPU 0 is a build_forced no-CBs CPU"
764 depends on RCU_NOCB_CPU
766 This option forces CPU 0 to be a no-CBs CPU, so that its RCU
767 callbacks are invoked by a per-CPU kthread whose name begins
768 with "rcuo". Additional CPUs may be designated as no-CBs
769 CPUs using the rcu_nocbs= boot parameter will be no-CBs CPUs.
770 All other CPUs will invoke their own RCU callbacks in softirq
773 Select this if CPU 0 needs to be a no-CBs CPU for real-time
774 or energy-efficiency reasons, but the real reason it exists
775 is to ensure that randconfig testing covers mixed systems.
777 config RCU_NOCB_CPU_ALL
778 bool "All CPUs are build_forced no-CBs CPUs"
779 depends on RCU_NOCB_CPU
781 This option forces all CPUs to be no-CBs CPUs. The rcu_nocbs=
782 boot parameter will be ignored. All CPUs' RCU callbacks will
783 be executed in the context of per-CPU rcuo kthreads created for
784 this purpose. Assuming that the kthreads whose names start with
785 "rcuo" are bound to "housekeeping" CPUs, this reduces OS jitter
786 on the remaining CPUs, but might decrease memory locality during
787 RCU-callback invocation, thus potentially degrading throughput.
789 Select this if all CPUs need to be no-CBs CPUs for real-time
790 or energy-efficiency reasons.
794 endmenu # "RCU Subsystem"
801 tristate "Kernel .config support"
804 This option enables the complete Linux kernel ".config" file
805 contents to be saved in the kernel. It provides documentation
806 of which kernel options are used in a running kernel or in an
807 on-disk kernel. This information can be extracted from the kernel
808 image file with the script scripts/extract-ikconfig and used as
809 input to rebuild the current kernel or to build another kernel.
810 It can also be extracted from a running kernel by reading
811 /proc/config.gz if enabled (below).
814 bool "Enable access to .config through /proc/config.gz"
815 depends on IKCONFIG && PROC_FS
817 This option enables access to the kernel configuration file
818 through /proc/config.gz.
821 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
826 Select the minimal kernel log buffer size as a power of 2.
827 The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
828 parameter, see below. Any higher size also might be forced
829 by "log_buf_len" boot parameter.
839 config LOG_CPU_MAX_BUF_SHIFT
840 int "CPU kernel log buffer size contribution (13 => 8 KB, 17 => 128KB)"
842 default 12 if !BASE_SMALL
843 default 0 if BASE_SMALL
846 This option allows to increase the default ring buffer size
847 according to the number of CPUs. The value defines the contribution
848 of each CPU as a power of 2. The used space is typically only few
849 lines however it might be much more when problems are reported,
852 The increased size means that a new buffer has to be allocated and
853 the original static one is unused. It makes sense only on systems
854 with more CPUs. Therefore this value is used only when the sum of
855 contributions is greater than the half of the default kernel ring
856 buffer as defined by LOG_BUF_SHIFT. The default values are set
857 so that more than 64 CPUs are needed to trigger the allocation.
859 Also this option is ignored when "log_buf_len" kernel parameter is
860 used as it forces an exact (power of two) size of the ring buffer.
862 The number of possible CPUs is used for this computation ignoring
863 hotplugging making the compuation optimal for the the worst case
864 scenerio while allowing a simple algorithm to be used from bootup.
866 Examples shift values and their meaning:
867 17 => 128 KB for each CPU
868 16 => 64 KB for each CPU
869 15 => 32 KB for each CPU
870 14 => 16 KB for each CPU
871 13 => 8 KB for each CPU
872 12 => 4 KB for each CPU
875 # Architectures with an unreliable sched_clock() should select this:
877 config HAVE_UNSTABLE_SCHED_CLOCK
880 config GENERIC_SCHED_CLOCK
884 # For architectures that want to enable the support for NUMA-affine scheduler
887 config ARCH_SUPPORTS_NUMA_BALANCING
891 # For architectures that know their GCC __int128 support is sound
893 config ARCH_SUPPORTS_INT128
896 # For architectures that (ab)use NUMA to represent different memory regions
897 # all cpu-local but of different latencies, such as SuperH.
899 config ARCH_WANT_NUMA_VARIABLE_LOCALITY
902 config NUMA_BALANCING_DEFAULT_ENABLED
903 bool "Automatically enable NUMA aware memory/task placement"
905 depends on NUMA_BALANCING
907 If set, automatic NUMA balancing will be enabled if running on a NUMA
910 config NUMA_BALANCING
911 bool "Memory placement aware NUMA scheduler"
912 depends on ARCH_SUPPORTS_NUMA_BALANCING
913 depends on !ARCH_WANT_NUMA_VARIABLE_LOCALITY
914 depends on SMP && NUMA && MIGRATION
916 This option adds support for automatic NUMA aware memory/task placement.
917 The mechanism is quite primitive and is based on migrating memory when
918 it has references to the node the task is running on.
920 This system will be inactive on UMA systems.
923 boolean "Control Group support"
926 This option adds support for grouping sets of processes together, for
927 use with process control subsystems such as Cpusets, CFS, memory
928 controls or device isolation.
930 - Documentation/scheduler/sched-design-CFS.txt (CFS)
931 - Documentation/cgroups/ (features for grouping, isolation
932 and resource control)
939 bool "Example debug cgroup subsystem"
942 This option enables a simple cgroup subsystem that
943 exports useful debugging information about the cgroups
948 config CGROUP_FREEZER
949 bool "Freezer cgroup subsystem"
951 Provides a way to freeze and unfreeze all tasks in a
955 bool "Device controller for cgroups"
957 Provides a cgroup implementing whitelists for devices which
958 a process in the cgroup can mknod or open.
961 bool "Cpuset support"
963 This option will let you create and manage CPUSETs which
964 allow dynamically partitioning a system into sets of CPUs and
965 Memory Nodes and assigning tasks to run only within those sets.
966 This is primarily useful on large SMP or NUMA systems.
970 config PROC_PID_CPUSET
971 bool "Include legacy /proc/<pid>/cpuset file"
975 config CGROUP_CPUACCT
976 bool "Simple CPU accounting cgroup subsystem"
978 Provides a simple Resource Controller for monitoring the
979 total CPU consumed by the tasks in a cgroup.
981 config RESOURCE_COUNTERS
982 bool "Resource counters"
984 This option enables controller independent resource accounting
985 infrastructure that works with cgroups.
988 bool "Memory Resource Controller for Control Groups"
989 depends on RESOURCE_COUNTERS
992 Provides a memory resource controller that manages both anonymous
993 memory and page cache. (See Documentation/cgroups/memory.txt)
995 Note that setting this option increases fixed memory overhead
996 associated with each page of memory in the system. By this,
997 8(16)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
998 usage tracking struct at boot. Total amount of this is printed out
1001 Only enable when you're ok with these trade offs and really
1002 sure you need the memory resource controller. Even when you enable
1003 this, you can set "cgroup_disable=memory" at your boot option to
1004 disable memory resource controller and you can avoid overheads.
1005 (and lose benefits of memory resource controller)
1008 bool "Memory Resource Controller Swap Extension"
1009 depends on MEMCG && SWAP
1011 Add swap management feature to memory resource controller. When you
1012 enable this, you can limit mem+swap usage per cgroup. In other words,
1013 when you disable this, memory resource controller has no cares to
1014 usage of swap...a process can exhaust all of the swap. This extension
1015 is useful when you want to avoid exhaustion swap but this itself
1016 adds more overheads and consumes memory for remembering information.
1017 Especially if you use 32bit system or small memory system, please
1018 be careful about enabling this. When memory resource controller
1019 is disabled by boot option, this will be automatically disabled and
1020 there will be no overhead from this. Even when you set this config=y,
1021 if boot option "swapaccount=0" is set, swap will not be accounted.
1022 Now, memory usage of swap_cgroup is 2 bytes per entry. If swap page
1023 size is 4096bytes, 512k per 1Gbytes of swap.
1024 config MEMCG_SWAP_ENABLED
1025 bool "Memory Resource Controller Swap Extension enabled by default"
1026 depends on MEMCG_SWAP
1029 Memory Resource Controller Swap Extension comes with its price in
1030 a bigger memory consumption. General purpose distribution kernels
1031 which want to enable the feature but keep it disabled by default
1032 and let the user enable it by swapaccount=1 boot command line
1033 parameter should have this option unselected.
1034 For those who want to have the feature enabled by default should
1035 select this option (if, for some reason, they need to disable it
1036 then swapaccount=0 does the trick).
1038 bool "Memory Resource Controller Kernel Memory accounting"
1040 depends on SLUB || SLAB
1042 The Kernel Memory extension for Memory Resource Controller can limit
1043 the amount of memory used by kernel objects in the system. Those are
1044 fundamentally different from the entities handled by the standard
1045 Memory Controller, which are page-based, and can be swapped. Users of
1046 the kmem extension can use it to guarantee that no group of processes
1047 will ever exhaust kernel resources alone.
1049 WARNING: Current implementation lacks reclaim support. That means
1050 allocation attempts will fail when close to the limit even if there
1051 are plenty of kmem available for reclaim. That makes this option
1052 unusable in real life so DO NOT SELECT IT unless for development
1055 config CGROUP_HUGETLB
1056 bool "HugeTLB Resource Controller for Control Groups"
1057 depends on RESOURCE_COUNTERS && HUGETLB_PAGE
1060 Provides a cgroup Resource Controller for HugeTLB pages.
1061 When you enable this, you can put a per cgroup limit on HugeTLB usage.
1062 The limit is enforced during page fault. Since HugeTLB doesn't
1063 support page reclaim, enforcing the limit at page fault time implies
1064 that, the application will get SIGBUS signal if it tries to access
1065 HugeTLB pages beyond its limit. This requires the application to know
1066 beforehand how much HugeTLB pages it would require for its use. The
1067 control group is tracked in the third page lru pointer. This means
1068 that we cannot use the controller with huge page less than 3 pages.
1071 bool "Enable perf_event per-cpu per-container group (cgroup) monitoring"
1072 depends on PERF_EVENTS && CGROUPS
1074 This option extends the per-cpu mode to restrict monitoring to
1075 threads which belong to the cgroup specified and run on the
1080 menuconfig CGROUP_SCHED
1081 bool "Group CPU scheduler"
1084 This feature lets CPU scheduler recognize task groups and control CPU
1085 bandwidth allocation to such task groups. It uses cgroups to group
1089 config FAIR_GROUP_SCHED
1090 bool "Group scheduling for SCHED_OTHER"
1091 depends on CGROUP_SCHED
1092 default CGROUP_SCHED
1094 config CFS_BANDWIDTH
1095 bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED"
1096 depends on FAIR_GROUP_SCHED
1099 This option allows users to define CPU bandwidth rates (limits) for
1100 tasks running within the fair group scheduler. Groups with no limit
1101 set are considered to be unconstrained and will run with no
1103 See tip/Documentation/scheduler/sched-bwc.txt for more information.
1105 config RT_GROUP_SCHED
1106 bool "Group scheduling for SCHED_RR/FIFO"
1107 depends on CGROUP_SCHED
1110 This feature lets you explicitly allocate real CPU bandwidth
1111 to task groups. If enabled, it will also make it impossible to
1112 schedule realtime tasks for non-root users until you allocate
1113 realtime bandwidth for them.
1114 See Documentation/scheduler/sched-rt-group.txt for more information.
1119 bool "Block IO controller"
1123 Generic block IO controller cgroup interface. This is the common
1124 cgroup interface which should be used by various IO controlling
1127 Currently, CFQ IO scheduler uses it to recognize task groups and
1128 control disk bandwidth allocation (proportional time slice allocation)
1129 to such task groups. It is also used by bio throttling logic in
1130 block layer to implement upper limit in IO rates on a device.
1132 This option only enables generic Block IO controller infrastructure.
1133 One needs to also enable actual IO controlling logic/policy. For
1134 enabling proportional weight division of disk bandwidth in CFQ, set
1135 CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
1136 CONFIG_BLK_DEV_THROTTLING=y.
1138 See Documentation/cgroups/blkio-controller.txt for more information.
1140 config DEBUG_BLK_CGROUP
1141 bool "Enable Block IO controller debugging"
1142 depends on BLK_CGROUP
1145 Enable some debugging help. Currently it exports additional stat
1146 files in a cgroup which can be useful for debugging.
1150 config CHECKPOINT_RESTORE
1151 bool "Checkpoint/restore support" if EXPERT
1154 Enables additional kernel features in a sake of checkpoint/restore.
1155 In particular it adds auxiliary prctl codes to setup process text,
1156 data and heap segment sizes, and a few additional /proc filesystem
1159 If unsure, say N here.
1161 menuconfig NAMESPACES
1162 bool "Namespaces support" if EXPERT
1165 Provides the way to make tasks work with different objects using
1166 the same id. For example same IPC id may refer to different objects
1167 or same user id or pid may refer to different tasks when used in
1168 different namespaces.
1173 bool "UTS namespace"
1176 In this namespace tasks see different info provided with the
1180 bool "IPC namespace"
1181 depends on (SYSVIPC || POSIX_MQUEUE)
1184 In this namespace tasks work with IPC ids which correspond to
1185 different IPC objects in different namespaces.
1188 bool "User namespace"
1191 This allows containers, i.e. vservers, to use user namespaces
1192 to provide different user info for different servers.
1194 When user namespaces are enabled in the kernel it is
1195 recommended that the MEMCG and MEMCG_KMEM options also be
1196 enabled and that user-space use the memory control groups to
1197 limit the amount of memory a memory unprivileged users can
1203 bool "PID Namespaces"
1206 Support process id namespaces. This allows having multiple
1207 processes with the same pid as long as they are in different
1208 pid namespaces. This is a building block of containers.
1211 bool "Network namespace"
1215 Allow user space to create what appear to be multiple instances
1216 of the network stack.
1220 config SCHED_AUTOGROUP
1221 bool "Automatic process group scheduling"
1224 select FAIR_GROUP_SCHED
1226 This option optimizes the scheduler for common desktop workloads by
1227 automatically creating and populating task groups. This separation
1228 of workloads isolates aggressive CPU burners (like build jobs) from
1229 desktop applications. Task group autogeneration is currently based
1232 config SYSFS_DEPRECATED
1233 bool "Enable deprecated sysfs features to support old userspace tools"
1237 This option adds code that switches the layout of the "block" class
1238 devices, to not show up in /sys/class/block/, but only in
1241 This switch is only active when the sysfs.deprecated=1 boot option is
1242 passed or the SYSFS_DEPRECATED_V2 option is set.
1244 This option allows new kernels to run on old distributions and tools,
1245 which might get confused by /sys/class/block/. Since 2007/2008 all
1246 major distributions and tools handle this just fine.
1248 Recent distributions and userspace tools after 2009/2010 depend on
1249 the existence of /sys/class/block/, and will not work with this
1252 Only if you are using a new kernel on an old distribution, you might
1255 config SYSFS_DEPRECATED_V2
1256 bool "Enable deprecated sysfs features by default"
1259 depends on SYSFS_DEPRECATED
1261 Enable deprecated sysfs by default.
1263 See the CONFIG_SYSFS_DEPRECATED option for more details about this
1266 Only if you are using a new kernel on an old distribution, you might
1267 need to say Y here. Even then, odds are you would not need it
1268 enabled, you can always pass the boot option if absolutely necessary.
1271 bool "Kernel->user space relay support (formerly relayfs)"
1273 This option enables support for relay interface support in
1274 certain file systems (such as debugfs).
1275 It is designed to provide an efficient mechanism for tools and
1276 facilities to relay large amounts of data from kernel space to
1281 config BLK_DEV_INITRD
1282 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
1283 depends on BROKEN || !FRV
1285 The initial RAM filesystem is a ramfs which is loaded by the
1286 boot loader (loadlin or lilo) and that is mounted as root
1287 before the normal boot procedure. It is typically used to
1288 load modules needed to mount the "real" root file system,
1289 etc. See <file:Documentation/initrd.txt> for details.
1291 If RAM disk support (BLK_DEV_RAM) is also included, this
1292 also enables initial RAM disk (initrd) support and adds
1293 15 Kbytes (more on some other architectures) to the kernel size.
1299 source "usr/Kconfig"
1303 config CC_OPTIMIZE_FOR_SIZE
1304 bool "Optimize for size"
1306 Enabling this option will pass "-Os" instead of "-O2" to gcc
1307 resulting in a smaller kernel.
1320 config SYSCTL_EXCEPTION_TRACE
1323 Enable support for /proc/sys/debug/exception-trace.
1325 config SYSCTL_ARCH_UNALIGN_NO_WARN
1328 Enable support for /proc/sys/kernel/ignore-unaligned-usertrap
1329 Allows arch to define/use @no_unaligned_warning to possibly warn
1330 about unaligned access emulation going on under the hood.
1332 config SYSCTL_ARCH_UNALIGN_ALLOW
1335 Enable support for /proc/sys/kernel/unaligned-trap
1336 Allows arches to define/use @unaligned_enabled to runtime toggle
1337 the unaligned access emulation.
1338 see arch/parisc/kernel/unaligned.c for reference
1340 config HAVE_PCSPKR_PLATFORM
1344 bool "Configure standard kernel features (expert users)"
1345 # Unhide debug options, to make the on-by-default options visible
1348 This option allows certain base kernel options and settings
1349 to be disabled or tweaked. This is for specialized
1350 environments which can tolerate a "non-standard" kernel.
1351 Only use this if you really know what you are doing.
1354 bool "Enable 16-bit UID system calls" if EXPERT
1355 depends on HAVE_UID16
1358 This enables the legacy 16-bit UID syscall wrappers.
1360 config SGETMASK_SYSCALL
1361 bool "sgetmask/ssetmask syscalls support" if EXPERT
1362 def_bool PARISC || MN10300 || BLACKFIN || M68K || PPC || MIPS || X86 || SPARC || CRIS || MICROBLAZE || SUPERH
1364 sys_sgetmask and sys_ssetmask are obsolete system calls
1365 no longer supported in libc but still enabled by default in some
1368 If unsure, leave the default option here.
1370 config SYSFS_SYSCALL
1371 bool "Sysfs syscall support" if EXPERT
1374 sys_sysfs is an obsolete system call no longer supported in libc.
1375 Note that disabling this option is more secure but might break
1376 compatibility with some systems.
1378 If unsure say Y here.
1380 config SYSCTL_SYSCALL
1381 bool "Sysctl syscall support" if EXPERT
1382 depends on PROC_SYSCTL
1386 sys_sysctl uses binary paths that have been found challenging
1387 to properly maintain and use. The interface in /proc/sys
1388 using paths with ascii names is now the primary path to this
1391 Almost nothing using the binary sysctl interface so if you are
1392 trying to save some space it is probably safe to disable this,
1393 making your kernel marginally smaller.
1395 If unsure say N here.
1398 bool "Load all symbols for debugging/ksymoops" if EXPERT
1401 Say Y here to let the kernel print out symbolic crash information and
1402 symbolic stack backtraces. This increases the size of the kernel
1403 somewhat, as all symbols have to be loaded into the kernel image.
1406 bool "Include all symbols in kallsyms"
1407 depends on DEBUG_KERNEL && KALLSYMS
1409 Normally kallsyms only contains the symbols of functions for nicer
1410 OOPS messages and backtraces (i.e., symbols from the text and inittext
1411 sections). This is sufficient for most cases. And only in very rare
1412 cases (e.g., when a debugger is used) all symbols are required (e.g.,
1413 names of variables from the data sections, etc).
1415 This option makes sure that all symbols are loaded into the kernel
1416 image (i.e., symbols from all sections) in cost of increased kernel
1417 size (depending on the kernel configuration, it may be 300KiB or
1418 something like this).
1420 Say N unless you really need all symbols.
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.
1434 bool "BUG() support" if EXPERT
1437 Disabling this option eliminates support for BUG and WARN, reducing
1438 the size of your kernel image and potentially quietly ignoring
1439 numerous fatal conditions. You should only consider disabling this
1440 option for embedded systems with no facilities for reporting errors.
1446 bool "Enable ELF core dumps" if EXPERT
1448 Enable support for generating core dumps. Disabling saves about 4k.
1451 config PCSPKR_PLATFORM
1452 bool "Enable PC-Speaker support" if EXPERT
1453 depends on HAVE_PCSPKR_PLATFORM
1457 This option allows to disable the internal PC-Speaker
1458 support, saving some memory.
1462 bool "Enable full-sized data structures for core" if EXPERT
1464 Disabling this option reduces the size of miscellaneous core
1465 kernel data structures. This saves memory on small machines,
1466 but may reduce performance.
1469 bool "Enable futex support" if EXPERT
1473 Disabling this option will cause the kernel to be built without
1474 support for "fast userspace mutexes". The resulting kernel may not
1475 run glibc-based applications correctly.
1477 config HAVE_FUTEX_CMPXCHG
1481 Architectures should select this if futex_atomic_cmpxchg_inatomic()
1482 is implemented and always working. This removes a couple of runtime
1486 bool "Enable eventpoll support" if EXPERT
1490 Disabling this option will cause the kernel to be built without
1491 support for epoll family of system calls.
1494 bool "Enable signalfd() system call" if EXPERT
1498 Enable the signalfd() system call that allows to receive signals
1499 on a file descriptor.
1504 bool "Enable timerfd() system call" if EXPERT
1508 Enable the timerfd() system call that allows to receive timer
1509 events on a file descriptor.
1514 bool "Enable eventfd() system call" if EXPERT
1518 Enable the eventfd() system call that allows to receive both
1519 kernel notification (ie. KAIO) or userspace notifications.
1524 bool "Use full shmem filesystem" if EXPERT
1528 The shmem is an internal filesystem used to manage shared memory.
1529 It is backed by swap and manages resource limits. It is also exported
1530 to userspace as tmpfs if TMPFS is enabled. Disabling this
1531 option replaces shmem and tmpfs with the much simpler ramfs code,
1532 which may be appropriate on small systems without swap.
1535 bool "Enable AIO support" if EXPERT
1538 This option enables POSIX asynchronous I/O which may by used
1539 by some high performance threaded applications. Disabling
1540 this option saves about 7k.
1542 config ADVISE_SYSCALLS
1543 bool "Enable madvise/fadvise syscalls" if EXPERT
1546 This option enables the madvise and fadvise syscalls, used by
1547 applications to advise the kernel about their future memory or file
1548 usage, improving performance. If building an embedded system where no
1549 applications use these syscalls, you can disable this option to save
1554 bool "Enable PCI quirk workarounds" if EXPERT
1557 This enables workarounds for various PCI chipset
1558 bugs/quirks. Disable this only if your target machine is
1559 unaffected by PCI quirks.
1562 bool "Embedded system"
1563 option allnoconfig_y
1566 This option should be enabled if compiling the kernel for
1567 an embedded system so certain expert options are available
1570 config HAVE_PERF_EVENTS
1573 See tools/perf/design.txt for details.
1575 config PERF_USE_VMALLOC
1578 See tools/perf/design.txt for details
1580 menu "Kernel Performance Events And Counters"
1583 bool "Kernel performance events and counters"
1584 default y if PROFILING
1585 depends on HAVE_PERF_EVENTS
1589 Enable kernel support for various performance events provided
1590 by software and hardware.
1592 Software events are supported either built-in or via the
1593 use of generic tracepoints.
1595 Most modern CPUs support performance events via performance
1596 counter registers. These registers count the number of certain
1597 types of hw events: such as instructions executed, cachemisses
1598 suffered, or branches mis-predicted - without slowing down the
1599 kernel or applications. These registers can also trigger interrupts
1600 when a threshold number of events have passed - and can thus be
1601 used to profile the code that runs on that CPU.
1603 The Linux Performance Event subsystem provides an abstraction of
1604 these software and hardware event capabilities, available via a
1605 system call and used by the "perf" utility in tools/perf/. It
1606 provides per task and per CPU counters, and it provides event
1607 capabilities on top of those.
1611 config DEBUG_PERF_USE_VMALLOC
1613 bool "Debug: use vmalloc to back perf mmap() buffers"
1614 depends on PERF_EVENTS && DEBUG_KERNEL
1615 select PERF_USE_VMALLOC
1617 Use vmalloc memory to back perf mmap() buffers.
1619 Mostly useful for debugging the vmalloc code on platforms
1620 that don't require it.
1626 config VM_EVENT_COUNTERS
1628 bool "Enable VM event counters for /proc/vmstat" if EXPERT
1630 VM event counters are needed for event counts to be shown.
1631 This option allows the disabling of the VM event counters
1632 on EXPERT systems. /proc/vmstat will only show page counts
1633 if VM event counters are disabled.
1637 bool "Enable SLUB debugging support" if EXPERT
1638 depends on SLUB && SYSFS
1640 SLUB has extensive debug support features. Disabling these can
1641 result in significant savings in code size. This also disables
1642 SLUB sysfs support. /sys/slab will not exist and there will be
1643 no support for cache validation etc.
1646 bool "Disable heap randomization"
1649 Randomizing heap placement makes heap exploits harder, but it
1650 also breaks ancient binaries (including anything libc5 based).
1651 This option changes the bootup default to heap randomization
1652 disabled, and can be overridden at runtime by setting
1653 /proc/sys/kernel/randomize_va_space to 2.
1655 On non-ancient distros (post-2000 ones) N is usually a safe choice.
1658 prompt "Choose SLAB allocator"
1661 This option allows to select a slab allocator.
1666 The regular slab allocator that is established and known to work
1667 well in all environments. It organizes cache hot objects in
1668 per cpu and per node queues.
1671 bool "SLUB (Unqueued Allocator)"
1673 SLUB is a slab allocator that minimizes cache line usage
1674 instead of managing queues of cached objects (SLAB approach).
1675 Per cpu caching is realized using slabs of objects instead
1676 of queues of objects. SLUB can use memory efficiently
1677 and has enhanced diagnostics. SLUB is the default choice for
1682 bool "SLOB (Simple Allocator)"
1684 SLOB replaces the stock allocator with a drastically simpler
1685 allocator. SLOB is generally more space efficient but
1686 does not perform as well on large systems.
1690 config SLUB_CPU_PARTIAL
1692 depends on SLUB && SMP
1693 bool "SLUB per cpu partial cache"
1695 Per cpu partial caches accellerate objects allocation and freeing
1696 that is local to a processor at the price of more indeterminism
1697 in the latency of the free. On overflow these caches will be cleared
1698 which requires the taking of locks that may cause latency spikes.
1699 Typically one would choose no for a realtime system.
1701 config MMAP_ALLOW_UNINITIALIZED
1702 bool "Allow mmapped anonymous memory to be uninitialized"
1703 depends on EXPERT && !MMU
1706 Normally, and according to the Linux spec, anonymous memory obtained
1707 from mmap() has it's contents cleared before it is passed to
1708 userspace. Enabling this config option allows you to request that
1709 mmap() skip that if it is given an MAP_UNINITIALIZED flag, thus
1710 providing a huge performance boost. If this option is not enabled,
1711 then the flag will be ignored.
1713 This is taken advantage of by uClibc's malloc(), and also by
1714 ELF-FDPIC binfmt's brk and stack allocator.
1716 Because of the obvious security issues, this option should only be
1717 enabled on embedded devices where you control what is run in
1718 userspace. Since that isn't generally a problem on no-MMU systems,
1719 it is normally safe to say Y here.
1721 See Documentation/nommu-mmap.txt for more information.
1723 config SYSTEM_TRUSTED_KEYRING
1724 bool "Provide system-wide ring of trusted keys"
1727 Provide a system keyring to which trusted keys can be added. Keys in
1728 the keyring are considered to be trusted. Keys may be added at will
1729 by the kernel from compiled-in data and from hardware key stores, but
1730 userspace may only add extra keys if those keys can be verified by
1731 keys already in the keyring.
1733 Keys in this keyring are used by module signature checking.
1736 bool "Profiling support"
1738 Say Y here to enable the extended profiling support mechanisms used
1739 by profilers such as OProfile.
1742 # Place an empty function call at each tracepoint site. Can be
1743 # dynamically changed for a probe function.
1748 source "arch/Kconfig"
1750 endmenu # General setup
1752 config HAVE_GENERIC_DMA_COHERENT
1759 depends on SLAB || SLUB_DEBUG
1767 default 0 if BASE_FULL
1768 default 1 if !BASE_FULL
1771 bool "Enable loadable module support"
1774 Kernel modules are small pieces of compiled code which can
1775 be inserted in the running kernel, rather than being
1776 permanently built into the kernel. You use the "modprobe"
1777 tool to add (and sometimes remove) them. If you say Y here,
1778 many parts of the kernel can be built as modules (by
1779 answering M instead of Y where indicated): this is most
1780 useful for infrequently used options which are not required
1781 for booting. For more information, see the man pages for
1782 modprobe, lsmod, modinfo, insmod and rmmod.
1784 If you say Y here, you will need to run "make
1785 modules_install" to put the modules under /lib/modules/
1786 where modprobe can find them (you may need to be root to do
1793 config MODULE_FORCE_LOAD
1794 bool "Forced module loading"
1797 Allow loading of modules without version information (ie. modprobe
1798 --force). Forced module loading sets the 'F' (forced) taint flag and
1799 is usually a really bad idea.
1801 config MODULE_UNLOAD
1802 bool "Module unloading"
1804 Without this option you will not be able to unload any
1805 modules (note that some modules may not be unloadable
1806 anyway), which makes your kernel smaller, faster
1807 and simpler. If unsure, say Y.
1809 config MODULE_FORCE_UNLOAD
1810 bool "Forced module unloading"
1811 depends on MODULE_UNLOAD
1813 This option allows you to force a module to unload, even if the
1814 kernel believes it is unsafe: the kernel will remove the module
1815 without waiting for anyone to stop using it (using the -f option to
1816 rmmod). This is mainly for kernel developers and desperate users.
1820 bool "Module versioning support"
1822 Usually, you have to use modules compiled with your kernel.
1823 Saying Y here makes it sometimes possible to use modules
1824 compiled for different kernels, by adding enough information
1825 to the modules to (hopefully) spot any changes which would
1826 make them incompatible with the kernel you are running. If
1829 config MODULE_SRCVERSION_ALL
1830 bool "Source checksum for all modules"
1832 Modules which contain a MODULE_VERSION get an extra "srcversion"
1833 field inserted into their modinfo section, which contains a
1834 sum of the source files which made it. This helps maintainers
1835 see exactly which source was used to build a module (since
1836 others sometimes change the module source without updating
1837 the version). With this option, such a "srcversion" field
1838 will be created for all modules. If unsure, say N.
1841 bool "Module signature verification"
1843 select SYSTEM_TRUSTED_KEYRING
1846 select ASYMMETRIC_KEY_TYPE
1847 select ASYMMETRIC_PUBLIC_KEY_SUBTYPE
1848 select PUBLIC_KEY_ALGO_RSA
1851 select X509_CERTIFICATE_PARSER
1853 Check modules for valid signatures upon load: the signature
1854 is simply appended to the module. For more information see
1855 Documentation/module-signing.txt.
1857 !!!WARNING!!! If you enable this option, you MUST make sure that the
1858 module DOES NOT get stripped after being signed. This includes the
1859 debuginfo strip done by some packagers (such as rpmbuild) and
1860 inclusion into an initramfs that wants the module size reduced.
1862 config MODULE_SIG_FORCE
1863 bool "Require modules to be validly signed"
1864 depends on MODULE_SIG
1866 Reject unsigned modules or signed modules for which we don't have a
1867 key. Without this, such modules will simply taint the kernel.
1869 config MODULE_SIG_ALL
1870 bool "Automatically sign all modules"
1872 depends on MODULE_SIG
1874 Sign all modules during make modules_install. Without this option,
1875 modules must be signed manually, using the scripts/sign-file tool.
1877 comment "Do not forget to sign required modules with scripts/sign-file"
1878 depends on MODULE_SIG_FORCE && !MODULE_SIG_ALL
1881 prompt "Which hash algorithm should modules be signed with?"
1882 depends on MODULE_SIG
1884 This determines which sort of hashing algorithm will be used during
1885 signature generation. This algorithm _must_ be built into the kernel
1886 directly so that signature verification can take place. It is not
1887 possible to load a signed module containing the algorithm to check
1888 the signature on that module.
1890 config MODULE_SIG_SHA1
1891 bool "Sign modules with SHA-1"
1894 config MODULE_SIG_SHA224
1895 bool "Sign modules with SHA-224"
1896 select CRYPTO_SHA256
1898 config MODULE_SIG_SHA256
1899 bool "Sign modules with SHA-256"
1900 select CRYPTO_SHA256
1902 config MODULE_SIG_SHA384
1903 bool "Sign modules with SHA-384"
1904 select CRYPTO_SHA512
1906 config MODULE_SIG_SHA512
1907 bool "Sign modules with SHA-512"
1908 select CRYPTO_SHA512
1912 config MODULE_SIG_HASH
1914 depends on MODULE_SIG
1915 default "sha1" if MODULE_SIG_SHA1
1916 default "sha224" if MODULE_SIG_SHA224
1917 default "sha256" if MODULE_SIG_SHA256
1918 default "sha384" if MODULE_SIG_SHA384
1919 default "sha512" if MODULE_SIG_SHA512
1921 config MODULE_COMPRESS
1922 bool "Compress modules on installation"
1925 This option compresses the kernel modules when 'make
1926 modules_install' is run.
1928 The modules will be compressed either using gzip or xz depend on the
1929 choice made in "Compression algorithm".
1931 module-init-tools has support for gzip format while kmod handle gzip
1932 and xz compressed modules.
1934 When a kernel module is installed from outside of the main kernel
1935 source and uses the Kbuild system for installing modules then that
1936 kernel module will also be compressed when it is installed.
1938 This option provides little benefit when the modules are to be used inside
1939 an initrd or initramfs, it generally is more efficient to compress the whole
1940 initrd or initramfs instead.
1942 This is fully compatible with signed modules while the signed module is
1943 compressed. module-init-tools or kmod handles decompression and provide to
1944 other layer the uncompressed but signed payload.
1947 prompt "Compression algorithm"
1948 depends on MODULE_COMPRESS
1949 default MODULE_COMPRESS_GZIP
1951 This determines which sort of compression will be used during
1952 'make modules_install'.
1954 GZIP (default) and XZ are supported.
1956 config MODULE_COMPRESS_GZIP
1959 config MODULE_COMPRESS_XZ
1966 config INIT_ALL_POSSIBLE
1969 Back when each arch used to define their own cpu_online_mask and
1970 cpu_possible_mask, some of them chose to initialize cpu_possible_mask
1971 with all 1s, and others with all 0s. When they were centralised,
1972 it was better to provide this option than to break all the archs
1973 and have several arch maintainers pursuing me down dark alleys.
1978 depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
1980 Need stop_machine() primitive.
1982 source "block/Kconfig"
1984 config PREEMPT_NOTIFIERS
1991 # Can be selected by architectures with broken toolchains
1992 # that get confused by correct const<->read_only section
1994 config BROKEN_RODATA
2000 Build a simple ASN.1 grammar compiler that produces a bytecode output
2001 that can be interpreted by the ASN.1 stream decoder and used to
2002 inform it as to what tags are to be expected in a stream and what
2003 functions to call on what tags.
2005 source "kernel/Kconfig.locks"
git.samba.org / sfrench / cifs-2.6.git / blob