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"
28 depends on HAVE_IRQ_WORK
30 config BUILDTIME_EXTABLE_SORT
36 bool "Prompt for development and/or incomplete code/drivers"
38 Some of the various things that Linux supports (such as network
39 drivers, file systems, network protocols, etc.) can be in a state
40 of development where the functionality, stability, or the level of
41 testing is not yet high enough for general use. This is usually
42 known as the "alpha-test" phase among developers. If a feature is
43 currently in alpha-test, then the developers usually discourage
44 uninformed widespread use of this feature by the general public to
45 avoid "Why doesn't this work?" type mail messages. However, active
46 testing and use of these systems is welcomed. Just be aware that it
47 may not meet the normal level of reliability or it may fail to work
48 in some special cases. Detailed bug reports from people familiar
49 with the kernel internals are usually welcomed by the developers
50 (before submitting bug reports, please read the documents
51 <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
52 <file:Documentation/BUG-HUNTING>, and
53 <file:Documentation/oops-tracing.txt> in the kernel source).
55 This option will also make obsoleted drivers available. These are
56 drivers that have been replaced by something else, and/or are
57 scheduled to be removed in a future kernel release.
59 Unless you intend to help test and develop a feature or driver that
60 falls into this category, or you have a situation that requires
61 using these features, you should probably say N here, which will
62 cause the configurator to present you with fewer choices. If
63 you say Y here, you will be offered the choice of using features or
64 drivers that are currently considered to be in the alpha-test phase.
71 depends on BROKEN || !SMP
74 config INIT_ENV_ARG_LIMIT
79 Maximum of each of the number of arguments and environment
80 variables passed to init from the kernel command line.
84 string "Cross-compiler tool prefix"
86 Same as running 'make CROSS_COMPILE=prefix-' but stored for
87 default make runs in this kernel build directory. You don't
88 need to set this unless you want the configured kernel build
89 directory to select the cross-compiler automatically.
92 string "Local version - append to kernel release"
94 Append an extra string to the end of your kernel version.
95 This will show up when you type uname, for example.
96 The string you set here will be appended after the contents of
97 any files with a filename matching localversion* in your
98 object and source tree, in that order. Your total string can
99 be a maximum of 64 characters.
101 config LOCALVERSION_AUTO
102 bool "Automatically append version information to the version string"
105 This will try to automatically determine if the current tree is a
106 release tree by looking for git tags that belong to the current
107 top of tree revision.
109 A string of the format -gxxxxxxxx will be added to the localversion
110 if a git-based tree is found. The string generated by this will be
111 appended after any matching localversion* files, and after the value
112 set in CONFIG_LOCALVERSION.
114 (The actual string used here is the first eight characters produced
115 by running the command:
117 $ git rev-parse --verify HEAD
119 which is done within the script "scripts/setlocalversion".)
121 config HAVE_KERNEL_GZIP
124 config HAVE_KERNEL_BZIP2
127 config HAVE_KERNEL_LZMA
130 config HAVE_KERNEL_XZ
133 config HAVE_KERNEL_LZO
137 prompt "Kernel compression mode"
139 depends on HAVE_KERNEL_GZIP || HAVE_KERNEL_BZIP2 || HAVE_KERNEL_LZMA || HAVE_KERNEL_XZ || HAVE_KERNEL_LZO
141 The linux kernel is a kind of self-extracting executable.
142 Several compression algorithms are available, which differ
143 in efficiency, compression and decompression speed.
144 Compression speed is only relevant when building a kernel.
145 Decompression speed is relevant at each boot.
147 If you have any problems with bzip2 or lzma compressed
148 kernels, mail me (Alain Knaff) <alain@knaff.lu>. (An older
149 version of this functionality (bzip2 only), for 2.4, was
150 supplied by Christian Ludwig)
152 High compression options are mostly useful for users, who
153 are low on disk space (embedded systems), but for whom ram
156 If in doubt, select 'gzip'
160 depends on HAVE_KERNEL_GZIP
162 The old and tried gzip compression. It provides a good balance
163 between compression ratio and decompression speed.
167 depends on HAVE_KERNEL_BZIP2
169 Its compression ratio and speed is intermediate.
170 Decompression speed is slowest among the three. The kernel
171 size is about 10% smaller with bzip2, in comparison to gzip.
172 Bzip2 uses a large amount of memory. For modern kernels you
173 will need at least 8MB RAM or more for booting.
177 depends on HAVE_KERNEL_LZMA
179 The most recent compression algorithm.
180 Its ratio is best, decompression speed is between the other
181 two. Compression is slowest. The kernel size is about 33%
182 smaller with LZMA in comparison to gzip.
186 depends on HAVE_KERNEL_XZ
188 XZ uses the LZMA2 algorithm and instruction set specific
189 BCJ filters which can improve compression ratio of executable
190 code. The size of the kernel is about 30% smaller with XZ in
191 comparison to gzip. On architectures for which there is a BCJ
192 filter (i386, x86_64, ARM, IA-64, PowerPC, and SPARC), XZ
193 will create a few percent smaller kernel than plain LZMA.
195 The speed is about the same as with LZMA: The decompression
196 speed of XZ is better than that of bzip2 but worse than gzip
197 and LZO. Compression is slow.
201 depends on HAVE_KERNEL_LZO
203 Its compression ratio is the poorest among the 4. The kernel
204 size is about 10% bigger than gzip; however its speed
205 (both compression and decompression) is the fastest.
209 config DEFAULT_HOSTNAME
210 string "Default hostname"
213 This option determines the default system hostname before userspace
214 calls sethostname(2). The kernel traditionally uses "(none)" here,
215 but you may wish to use a different default here to make a minimal
216 system more usable with less configuration.
219 bool "Support for paging of anonymous memory (swap)"
220 depends on MMU && BLOCK
223 This option allows you to choose whether you want to have support
224 for so called swap devices or swap files in your kernel that are
225 used to provide more virtual memory than the actual RAM present
226 in your computer. If unsure say Y.
231 Inter Process Communication is a suite of library functions and
232 system calls which let processes (running programs) synchronize and
233 exchange information. It is generally considered to be a good thing,
234 and some programs won't run unless you say Y here. In particular, if
235 you want to run the DOS emulator dosemu under Linux (read the
236 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
237 you'll need to say Y here.
239 You can find documentation about IPC with "info ipc" and also in
240 section 6.4 of the Linux Programmer's Guide, available from
241 <http://www.tldp.org/guides.html>.
243 config SYSVIPC_SYSCTL
250 bool "POSIX Message Queues"
251 depends on NET && EXPERIMENTAL
253 POSIX variant of message queues is a part of IPC. In POSIX message
254 queues every message has a priority which decides about succession
255 of receiving it by a process. If you want to compile and run
256 programs written e.g. for Solaris with use of its POSIX message
257 queues (functions mq_*) say Y here.
259 POSIX message queues are visible as a filesystem called 'mqueue'
260 and can be mounted somewhere if you want to do filesystem
261 operations on message queues.
265 config POSIX_MQUEUE_SYSCTL
267 depends on POSIX_MQUEUE
271 config BSD_PROCESS_ACCT
272 bool "BSD Process Accounting"
274 If you say Y here, a user level program will be able to instruct the
275 kernel (via a special system call) to write process accounting
276 information to a file: whenever a process exits, information about
277 that process will be appended to the file by the kernel. The
278 information includes things such as creation time, owning user,
279 command name, memory usage, controlling terminal etc. (the complete
280 list is in the struct acct in <file:include/linux/acct.h>). It is
281 up to the user level program to do useful things with this
282 information. This is generally a good idea, so say Y.
284 config BSD_PROCESS_ACCT_V3
285 bool "BSD Process Accounting version 3 file format"
286 depends on BSD_PROCESS_ACCT
289 If you say Y here, the process accounting information is written
290 in a new file format that also logs the process IDs of each
291 process and it's parent. Note that this file format is incompatible
292 with previous v0/v1/v2 file formats, so you will need updated tools
293 for processing it. A preliminary version of these tools is available
294 at <http://www.gnu.org/software/acct/>.
297 bool "open by fhandle syscalls"
300 If you say Y here, a user level program will be able to map
301 file names to handle and then later use the handle for
302 different file system operations. This is useful in implementing
303 userspace file servers, which now track files using handles instead
304 of names. The handle would remain the same even if file names
305 get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2)
309 bool "Export task/process statistics through netlink (EXPERIMENTAL)"
313 Export selected statistics for tasks/processes through the
314 generic netlink interface. Unlike BSD process accounting, the
315 statistics are available during the lifetime of tasks/processes as
316 responses to commands. Like BSD accounting, they are sent to user
321 config TASK_DELAY_ACCT
322 bool "Enable per-task delay accounting (EXPERIMENTAL)"
325 Collect information on time spent by a task waiting for system
326 resources like cpu, synchronous block I/O completion and swapping
327 in pages. Such statistics can help in setting a task's priorities
328 relative to other tasks for cpu, io, rss limits etc.
333 bool "Enable extended accounting over taskstats (EXPERIMENTAL)"
336 Collect extended task accounting data and send the data
337 to userland for processing over the taskstats interface.
341 config TASK_IO_ACCOUNTING
342 bool "Enable per-task storage I/O accounting (EXPERIMENTAL)"
343 depends on TASK_XACCT
345 Collect information on the number of bytes of storage I/O which this
351 bool "Auditing support"
354 Enable auditing infrastructure that can be used with another
355 kernel subsystem, such as SELinux (which requires this for
356 logging of avc messages output). Does not do system-call
357 auditing without CONFIG_AUDITSYSCALL.
360 bool "Enable system-call auditing support"
361 depends on AUDIT && (X86 || PPC || S390 || IA64 || UML || SPARC64 || SUPERH || ARM)
362 default y if SECURITY_SELINUX
364 Enable low-overhead system-call auditing infrastructure that
365 can be used independently or with another kernel subsystem,
370 depends on AUDITSYSCALL
375 depends on AUDITSYSCALL
378 config AUDIT_LOGINUID_IMMUTABLE
379 bool "Make audit loginuid immutable"
382 The config option toggles if a task setting its loginuid requires
383 CAP_SYS_AUDITCONTROL or if that task should require no special permissions
384 but should instead only allow setting its loginuid if it was never
385 previously set. On systems which use systemd or a similar central
386 process to restart login services this should be set to true. On older
387 systems in which an admin would typically have to directly stop and
388 start processes this should be set to false. Setting this to true allows
389 one to drop potentially dangerous capabilites from the login tasks,
390 but may not be backwards compatible with older init systems.
392 source "kernel/irq/Kconfig"
393 source "kernel/time/Kconfig"
398 prompt "RCU Implementation"
402 bool "Tree-based hierarchical RCU"
403 depends on !PREEMPT && SMP
405 This option selects the RCU implementation that is
406 designed for very large SMP system with hundreds or
407 thousands of CPUs. It also scales down nicely to
410 config TREE_PREEMPT_RCU
411 bool "Preemptible tree-based hierarchical RCU"
412 depends on PREEMPT && SMP
414 This option selects the RCU implementation that is
415 designed for very large SMP systems with hundreds or
416 thousands of CPUs, but for which real-time response
417 is also required. It also scales down nicely to
421 bool "UP-only small-memory-footprint RCU"
422 depends on !PREEMPT && !SMP
424 This option selects the RCU implementation that is
425 designed for UP systems from which real-time response
426 is not required. This option greatly reduces the
427 memory footprint of RCU.
429 config TINY_PREEMPT_RCU
430 bool "Preemptible UP-only small-memory-footprint RCU"
431 depends on PREEMPT && !SMP
433 This option selects the RCU implementation that is designed
434 for real-time UP systems. This option greatly reduces the
435 memory footprint of RCU.
440 def_bool ( TREE_PREEMPT_RCU || TINY_PREEMPT_RCU )
442 This option enables preemptible-RCU code that is common between
443 the TREE_PREEMPT_RCU and TINY_PREEMPT_RCU implementations.
446 int "Tree-based hierarchical RCU fanout value"
449 depends on TREE_RCU || TREE_PREEMPT_RCU
453 This option controls the fanout of hierarchical implementations
454 of RCU, allowing RCU to work efficiently on machines with
455 large numbers of CPUs. This value must be at least the fourth
456 root of NR_CPUS, which allows NR_CPUS to be insanely large.
457 The default value of RCU_FANOUT should be used for production
458 systems, but if you are stress-testing the RCU implementation
459 itself, small RCU_FANOUT values allow you to test large-system
460 code paths on small(er) systems.
462 Select a specific number if testing RCU itself.
463 Take the default if unsure.
465 config RCU_FANOUT_LEAF
466 int "Tree-based hierarchical RCU leaf-level fanout value"
467 range 2 RCU_FANOUT if 64BIT
468 range 2 RCU_FANOUT if !64BIT
469 depends on TREE_RCU || TREE_PREEMPT_RCU
472 This option controls the leaf-level fanout of hierarchical
473 implementations of RCU, and allows trading off cache misses
474 against lock contention. Systems that synchronize their
475 scheduling-clock interrupts for energy-efficiency reasons will
476 want the default because the smaller leaf-level fanout keeps
477 lock contention levels acceptably low. Very large systems
478 (hundreds or thousands of CPUs) will instead want to set this
479 value to the maximum value possible in order to reduce the
480 number of cache misses incurred during RCU's grace-period
481 initialization. These systems tend to run CPU-bound, and thus
482 are not helped by synchronized interrupts, and thus tend to
483 skew them, which reduces lock contention enough that large
484 leaf-level fanouts work well.
486 Select a specific number if testing RCU itself.
488 Select the maximum permissible value for large systems.
490 Take the default if unsure.
492 config RCU_FANOUT_EXACT
493 bool "Disable tree-based hierarchical RCU auto-balancing"
494 depends on TREE_RCU || TREE_PREEMPT_RCU
497 This option forces use of the exact RCU_FANOUT value specified,
498 regardless of imbalances in the hierarchy. This is useful for
499 testing RCU itself, and might one day be useful on systems with
500 strong NUMA behavior.
502 Without RCU_FANOUT_EXACT, the code will balance the hierarchy.
506 config RCU_FAST_NO_HZ
507 bool "Accelerate last non-dyntick-idle CPU's grace periods"
508 depends on NO_HZ && SMP
511 This option causes RCU to attempt to accelerate grace periods
512 in order to allow CPUs to enter dynticks-idle state more
513 quickly. On the other hand, this option increases the overhead
514 of the dynticks-idle checking, particularly on systems with
515 large numbers of CPUs.
517 Say Y if energy efficiency is critically important, particularly
518 if you have relatively few CPUs.
520 Say N if you are unsure.
522 config TREE_RCU_TRACE
523 def_bool RCU_TRACE && ( TREE_RCU || TREE_PREEMPT_RCU )
526 This option provides tracing for the TREE_RCU and
527 TREE_PREEMPT_RCU implementations, permitting Makefile to
528 trivially select kernel/rcutree_trace.c.
531 bool "Enable RCU priority boosting"
532 depends on RT_MUTEXES && PREEMPT_RCU
535 This option boosts the priority of preempted RCU readers that
536 block the current preemptible RCU grace period for too long.
537 This option also prevents heavy loads from blocking RCU
538 callback invocation for all flavors of RCU.
540 Say Y here if you are working with real-time apps or heavy loads
541 Say N here if you are unsure.
543 config RCU_BOOST_PRIO
544 int "Real-time priority to boost RCU readers to"
549 This option specifies the real-time priority to which long-term
550 preempted RCU readers are to be boosted. If you are working
551 with a real-time application that has one or more CPU-bound
552 threads running at a real-time priority level, you should set
553 RCU_BOOST_PRIO to a priority higher then the highest-priority
554 real-time CPU-bound thread. The default RCU_BOOST_PRIO value
555 of 1 is appropriate in the common case, which is real-time
556 applications that do not have any CPU-bound threads.
558 Some real-time applications might not have a single real-time
559 thread that saturates a given CPU, but instead might have
560 multiple real-time threads that, taken together, fully utilize
561 that CPU. In this case, you should set RCU_BOOST_PRIO to
562 a priority higher than the lowest-priority thread that is
563 conspiring to prevent the CPU from running any non-real-time
564 tasks. For example, if one thread at priority 10 and another
565 thread at priority 5 are between themselves fully consuming
566 the CPU time on a given CPU, then RCU_BOOST_PRIO should be
567 set to priority 6 or higher.
569 Specify the real-time priority, or take the default if unsure.
571 config RCU_BOOST_DELAY
572 int "Milliseconds to delay boosting after RCU grace-period start"
577 This option specifies the time to wait after the beginning of
578 a given grace period before priority-boosting preempted RCU
579 readers blocking that grace period. Note that any RCU reader
580 blocking an expedited RCU grace period is boosted immediately.
582 Accept the default if unsure.
584 endmenu # "RCU Subsystem"
587 tristate "Kernel .config support"
589 This option enables the complete Linux kernel ".config" file
590 contents to be saved in the kernel. It provides documentation
591 of which kernel options are used in a running kernel or in an
592 on-disk kernel. This information can be extracted from the kernel
593 image file with the script scripts/extract-ikconfig and used as
594 input to rebuild the current kernel or to build another kernel.
595 It can also be extracted from a running kernel by reading
596 /proc/config.gz if enabled (below).
599 bool "Enable access to .config through /proc/config.gz"
600 depends on IKCONFIG && PROC_FS
602 This option enables access to the kernel configuration file
603 through /proc/config.gz.
606 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
610 Select kernel log buffer size as a power of 2.
620 # Architectures with an unreliable sched_clock() should select this:
622 config HAVE_UNSTABLE_SCHED_CLOCK
626 boolean "Control Group support"
629 This option adds support for grouping sets of processes together, for
630 use with process control subsystems such as Cpusets, CFS, memory
631 controls or device isolation.
633 - Documentation/scheduler/sched-design-CFS.txt (CFS)
634 - Documentation/cgroups/ (features for grouping, isolation
635 and resource control)
642 bool "Example debug cgroup subsystem"
645 This option enables a simple cgroup subsystem that
646 exports useful debugging information about the cgroups
651 config CGROUP_FREEZER
652 bool "Freezer cgroup subsystem"
654 Provides a way to freeze and unfreeze all tasks in a
658 bool "Device controller for cgroups"
660 Provides a cgroup implementing whitelists for devices which
661 a process in the cgroup can mknod or open.
664 bool "Cpuset support"
666 This option will let you create and manage CPUSETs which
667 allow dynamically partitioning a system into sets of CPUs and
668 Memory Nodes and assigning tasks to run only within those sets.
669 This is primarily useful on large SMP or NUMA systems.
673 config PROC_PID_CPUSET
674 bool "Include legacy /proc/<pid>/cpuset file"
678 config CGROUP_CPUACCT
679 bool "Simple CPU accounting cgroup subsystem"
681 Provides a simple Resource Controller for monitoring the
682 total CPU consumed by the tasks in a cgroup.
684 config RESOURCE_COUNTERS
685 bool "Resource counters"
687 This option enables controller independent resource accounting
688 infrastructure that works with cgroups.
690 config CGROUP_MEM_RES_CTLR
691 bool "Memory Resource Controller for Control Groups"
692 depends on RESOURCE_COUNTERS
695 Provides a memory resource controller that manages both anonymous
696 memory and page cache. (See Documentation/cgroups/memory.txt)
698 Note that setting this option increases fixed memory overhead
699 associated with each page of memory in the system. By this,
700 20(40)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
701 usage tracking struct at boot. Total amount of this is printed out
704 Only enable when you're ok with these trade offs and really
705 sure you need the memory resource controller. Even when you enable
706 this, you can set "cgroup_disable=memory" at your boot option to
707 disable memory resource controller and you can avoid overheads.
708 (and lose benefits of memory resource controller)
710 This config option also selects MM_OWNER config option, which
711 could in turn add some fork/exit overhead.
713 config CGROUP_MEM_RES_CTLR_SWAP
714 bool "Memory Resource Controller Swap Extension"
715 depends on CGROUP_MEM_RES_CTLR && SWAP
717 Add swap management feature to memory resource controller. When you
718 enable this, you can limit mem+swap usage per cgroup. In other words,
719 when you disable this, memory resource controller has no cares to
720 usage of swap...a process can exhaust all of the swap. This extension
721 is useful when you want to avoid exhaustion swap but this itself
722 adds more overheads and consumes memory for remembering information.
723 Especially if you use 32bit system or small memory system, please
724 be careful about enabling this. When memory resource controller
725 is disabled by boot option, this will be automatically disabled and
726 there will be no overhead from this. Even when you set this config=y,
727 if boot option "swapaccount=0" is set, swap will not be accounted.
728 Now, memory usage of swap_cgroup is 2 bytes per entry. If swap page
729 size is 4096bytes, 512k per 1Gbytes of swap.
730 config CGROUP_MEM_RES_CTLR_SWAP_ENABLED
731 bool "Memory Resource Controller Swap Extension enabled by default"
732 depends on CGROUP_MEM_RES_CTLR_SWAP
735 Memory Resource Controller Swap Extension comes with its price in
736 a bigger memory consumption. General purpose distribution kernels
737 which want to enable the feature but keep it disabled by default
738 and let the user enable it by swapaccount boot command line
739 parameter should have this option unselected.
740 For those who want to have the feature enabled by default should
741 select this option (if, for some reason, they need to disable it
742 then swapaccount=0 does the trick).
743 config CGROUP_MEM_RES_CTLR_KMEM
744 bool "Memory Resource Controller Kernel Memory accounting (EXPERIMENTAL)"
745 depends on CGROUP_MEM_RES_CTLR && EXPERIMENTAL
748 The Kernel Memory extension for Memory Resource Controller can limit
749 the amount of memory used by kernel objects in the system. Those are
750 fundamentally different from the entities handled by the standard
751 Memory Controller, which are page-based, and can be swapped. Users of
752 the kmem extension can use it to guarantee that no group of processes
753 will ever exhaust kernel resources alone.
756 bool "Enable perf_event per-cpu per-container group (cgroup) monitoring"
757 depends on PERF_EVENTS && CGROUPS
759 This option extends the per-cpu mode to restrict monitoring to
760 threads which belong to the cgroup specified and run on the
765 menuconfig CGROUP_SCHED
766 bool "Group CPU scheduler"
769 This feature lets CPU scheduler recognize task groups and control CPU
770 bandwidth allocation to such task groups. It uses cgroups to group
774 config FAIR_GROUP_SCHED
775 bool "Group scheduling for SCHED_OTHER"
776 depends on CGROUP_SCHED
780 bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED"
781 depends on EXPERIMENTAL
782 depends on FAIR_GROUP_SCHED
785 This option allows users to define CPU bandwidth rates (limits) for
786 tasks running within the fair group scheduler. Groups with no limit
787 set are considered to be unconstrained and will run with no
789 See tip/Documentation/scheduler/sched-bwc.txt for more information.
791 config RT_GROUP_SCHED
792 bool "Group scheduling for SCHED_RR/FIFO"
793 depends on EXPERIMENTAL
794 depends on CGROUP_SCHED
797 This feature lets you explicitly allocate real CPU bandwidth
798 to task groups. If enabled, it will also make it impossible to
799 schedule realtime tasks for non-root users until you allocate
800 realtime bandwidth for them.
801 See Documentation/scheduler/sched-rt-group.txt for more information.
806 tristate "Block IO controller"
810 Generic block IO controller cgroup interface. This is the common
811 cgroup interface which should be used by various IO controlling
814 Currently, CFQ IO scheduler uses it to recognize task groups and
815 control disk bandwidth allocation (proportional time slice allocation)
816 to such task groups. It is also used by bio throttling logic in
817 block layer to implement upper limit in IO rates on a device.
819 This option only enables generic Block IO controller infrastructure.
820 One needs to also enable actual IO controlling logic/policy. For
821 enabling proportional weight division of disk bandwidth in CFQ, set
822 CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
823 CONFIG_BLK_DEV_THROTTLING=y.
825 See Documentation/cgroups/blkio-controller.txt for more information.
827 config DEBUG_BLK_CGROUP
828 bool "Enable Block IO controller debugging"
829 depends on BLK_CGROUP
832 Enable some debugging help. Currently it exports additional stat
833 files in a cgroup which can be useful for debugging.
837 config CHECKPOINT_RESTORE
838 bool "Checkpoint/restore support" if EXPERT
841 Enables additional kernel features in a sake of checkpoint/restore.
842 In particular it adds auxiliary prctl codes to setup process text,
843 data and heap segment sizes, and a few additional /proc filesystem
846 If unsure, say N here.
848 menuconfig NAMESPACES
849 bool "Namespaces support" if EXPERT
852 Provides the way to make tasks work with different objects using
853 the same id. For example same IPC id may refer to different objects
854 or same user id or pid may refer to different tasks when used in
855 different namespaces.
863 In this namespace tasks see different info provided with the
868 depends on (SYSVIPC || POSIX_MQUEUE)
871 In this namespace tasks work with IPC ids which correspond to
872 different IPC objects in different namespaces.
875 bool "User namespace (EXPERIMENTAL)"
876 depends on EXPERIMENTAL
877 depends on UIDGID_CONVERTED
878 select UIDGID_STRICT_TYPE_CHECKS
882 This allows containers, i.e. vservers, to use user namespaces
883 to provide different user info for different servers.
887 bool "PID Namespaces"
890 Support process id namespaces. This allows having multiple
891 processes with the same pid as long as they are in different
892 pid namespaces. This is a building block of containers.
895 bool "Network namespace"
899 Allow user space to create what appear to be multiple instances
900 of the network stack.
904 config UIDGID_CONVERTED
905 # True if all of the selected software conmponents are known
906 # to have uid_t and gid_t converted to kuid_t and kgid_t
907 # where appropriate and are otherwise safe to use with
908 # the user namespace.
912 # List of kernel pieces that need user namespace work
914 depends on SYSVIPC = n
919 depends on AUDITSYSCALL = n
920 depends on TASKSTATS = n
921 depends on TRACING = n
922 depends on FS_POSIX_ACL = n
924 depends on QUOTACTL = n
925 depends on DEBUG_CREDENTIALS = n
926 depends on BSD_PROCESS_ACCT = n
928 depends on PROC_EVENTS = n
932 depends on NET_9P = n
934 depends on PHONET = n
935 depends on NET_CLS_FLOW = n
936 depends on NETFILTER_XT_MATCH_OWNER = n
937 depends on NETFILTER_XT_MATCH_RECENT = n
938 depends on NETFILTER_XT_TARGET_LOG = n
939 depends on NETFILTER_NETLINK_LOG = n
942 depends on IP_SCTP = n
943 depends on AF_RXRPC = n
945 depends on NET_KEY = n
946 depends on INET_DIAG = n
947 depends on DNS_RESOLVER = n
952 depends on USB_DEVICEFS = n
953 depends on USB_GADGETFS = n
954 depends on USB_FUNCTIONFS = n
955 depends on DEVTMPFS = n
959 depends on ADFS_FS = n
960 depends on AFFS_FS = n
961 depends on AFS_FS = n
962 depends on AUTOFS4_FS = n
963 depends on BEFS_FS = n
964 depends on BFS_FS = n
965 depends on BTRFS_FS = n
966 depends on CEPH_FS = n
968 depends on CODA_FS = n
969 depends on CONFIGFS_FS = n
970 depends on CRAMFS = n
971 depends on DEBUG_FS = n
972 depends on ECRYPT_FS = n
973 depends on EFS_FS = n
974 depends on EXOFS_FS = n
975 depends on FAT_FS = n
976 depends on FUSE_FS = n
977 depends on GFS2_FS = n
978 depends on HFS_FS = n
979 depends on HFSPLUS_FS = n
980 depends on HPFS_FS = n
981 depends on HUGETLBFS = n
982 depends on ISO9660_FS = n
983 depends on JFFS2_FS = n
984 depends on JFS_FS = n
986 depends on MINIX_FS = n
987 depends on NCP_FS = n
989 depends on NFS_FS = n
990 depends on NILFS2_FS = n
991 depends on NTFS_FS = n
992 depends on OCFS2_FS = n
993 depends on OMFS_FS = n
994 depends on QNX4FS_FS = n
995 depends on QNX6FS_FS = n
996 depends on REISERFS_FS = n
997 depends on SQUASHFS = n
998 depends on SYSV_FS = n
999 depends on UBIFS_FS = n
1000 depends on UDF_FS = n
1001 depends on UFS_FS = n
1002 depends on VXFS_FS = n
1003 depends on XFS_FS = n
1005 depends on !UML || HOSTFS = n
1007 # The rare drivers that won't build
1009 depends on AIRO_CS = n
1011 depends on INFINIBAND_QIB = n
1012 depends on BLK_DEV_LOOP = n
1013 depends on ANDROID_BINDER_IPC = n
1016 depends on SECURITY_TOMOYO = n
1017 depends on SECURITY_APPARMOR = n
1019 config UIDGID_STRICT_TYPE_CHECKS
1020 bool "Require conversions between uid/gids and their internal representation"
1021 depends on UIDGID_CONVERTED
1024 While the nececessary conversions are being added to all subsystems this option allows
1025 the code to continue to build for unconverted subsystems.
1027 Say Y here if you want the strict type checking enabled
1029 config SCHED_AUTOGROUP
1030 bool "Automatic process group scheduling"
1034 select FAIR_GROUP_SCHED
1036 This option optimizes the scheduler for common desktop workloads by
1037 automatically creating and populating task groups. This separation
1038 of workloads isolates aggressive CPU burners (like build jobs) from
1039 desktop applications. Task group autogeneration is currently based
1045 config SYSFS_DEPRECATED
1046 bool "Enable deprecated sysfs features to support old userspace tools"
1050 This option adds code that switches the layout of the "block" class
1051 devices, to not show up in /sys/class/block/, but only in
1054 This switch is only active when the sysfs.deprecated=1 boot option is
1055 passed or the SYSFS_DEPRECATED_V2 option is set.
1057 This option allows new kernels to run on old distributions and tools,
1058 which might get confused by /sys/class/block/. Since 2007/2008 all
1059 major distributions and tools handle this just fine.
1061 Recent distributions and userspace tools after 2009/2010 depend on
1062 the existence of /sys/class/block/, and will not work with this
1065 Only if you are using a new kernel on an old distribution, you might
1068 config SYSFS_DEPRECATED_V2
1069 bool "Enable deprecated sysfs features by default"
1072 depends on SYSFS_DEPRECATED
1074 Enable deprecated sysfs by default.
1076 See the CONFIG_SYSFS_DEPRECATED option for more details about this
1079 Only if you are using a new kernel on an old distribution, you might
1080 need to say Y here. Even then, odds are you would not need it
1081 enabled, you can always pass the boot option if absolutely necessary.
1084 bool "Kernel->user space relay support (formerly relayfs)"
1086 This option enables support for relay interface support in
1087 certain file systems (such as debugfs).
1088 It is designed to provide an efficient mechanism for tools and
1089 facilities to relay large amounts of data from kernel space to
1094 config BLK_DEV_INITRD
1095 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
1096 depends on BROKEN || !FRV
1098 The initial RAM filesystem is a ramfs which is loaded by the
1099 boot loader (loadlin or lilo) and that is mounted as root
1100 before the normal boot procedure. It is typically used to
1101 load modules needed to mount the "real" root file system,
1102 etc. See <file:Documentation/initrd.txt> for details.
1104 If RAM disk support (BLK_DEV_RAM) is also included, this
1105 also enables initial RAM disk (initrd) support and adds
1106 15 Kbytes (more on some other architectures) to the kernel size.
1112 source "usr/Kconfig"
1116 config CC_OPTIMIZE_FOR_SIZE
1117 bool "Optimize for size"
1119 Enabling this option will pass "-Os" instead of "-O2" to gcc
1120 resulting in a smaller kernel.
1131 bool "Configure standard kernel features (expert users)"
1132 # Unhide debug options, to make the on-by-default options visible
1135 This option allows certain base kernel options and settings
1136 to be disabled or tweaked. This is for specialized
1137 environments which can tolerate a "non-standard" kernel.
1138 Only use this if you really know what you are doing.
1141 bool "Enable 16-bit UID system calls" if EXPERT
1142 depends on ARM || BLACKFIN || CRIS || FRV || H8300 || X86_32 || M68K || (S390 && !64BIT) || SUPERH || SPARC32 || (SPARC64 && COMPAT) || UML || (X86_64 && IA32_EMULATION)
1145 This enables the legacy 16-bit UID syscall wrappers.
1147 config SYSCTL_SYSCALL
1148 bool "Sysctl syscall support" if EXPERT
1149 depends on PROC_SYSCTL
1153 sys_sysctl uses binary paths that have been found challenging
1154 to properly maintain and use. The interface in /proc/sys
1155 using paths with ascii names is now the primary path to this
1158 Almost nothing using the binary sysctl interface so if you are
1159 trying to save some space it is probably safe to disable this,
1160 making your kernel marginally smaller.
1162 If unsure say N here.
1165 bool "Load all symbols for debugging/ksymoops" if EXPERT
1168 Say Y here to let the kernel print out symbolic crash information and
1169 symbolic stack backtraces. This increases the size of the kernel
1170 somewhat, as all symbols have to be loaded into the kernel image.
1173 bool "Include all symbols in kallsyms"
1174 depends on DEBUG_KERNEL && KALLSYMS
1176 Normally kallsyms only contains the symbols of functions for nicer
1177 OOPS messages and backtraces (i.e., symbols from the text and inittext
1178 sections). This is sufficient for most cases. And only in very rare
1179 cases (e.g., when a debugger is used) all symbols are required (e.g.,
1180 names of variables from the data sections, etc).
1182 This option makes sure that all symbols are loaded into the kernel
1183 image (i.e., symbols from all sections) in cost of increased kernel
1184 size (depending on the kernel configuration, it may be 300KiB or
1185 something like this).
1187 Say N unless you really need all symbols.
1190 bool "Support for hot-pluggable devices" if EXPERT
1193 This option is provided for the case where no hotplug or uevent
1194 capabilities is wanted by the kernel. You should only consider
1195 disabling this option for embedded systems that do not use modules, a
1196 dynamic /dev tree, or dynamic device discovery. Just say Y.
1200 bool "Enable support for printk" if EXPERT
1202 This option enables normal printk support. Removing it
1203 eliminates most of the message strings from the kernel image
1204 and makes the kernel more or less silent. As this makes it
1205 very difficult to diagnose system problems, saying N here is
1206 strongly discouraged.
1209 bool "BUG() support" if EXPERT
1212 Disabling this option eliminates support for BUG and WARN, reducing
1213 the size of your kernel image and potentially quietly ignoring
1214 numerous fatal conditions. You should only consider disabling this
1215 option for embedded systems with no facilities for reporting errors.
1220 bool "Enable ELF core dumps" if EXPERT
1222 Enable support for generating core dumps. Disabling saves about 4k.
1225 config PCSPKR_PLATFORM
1226 bool "Enable PC-Speaker support" if EXPERT
1227 depends on HAVE_PCSPKR_PLATFORM
1231 This option allows to disable the internal PC-Speaker
1232 support, saving some memory.
1234 config HAVE_PCSPKR_PLATFORM
1239 bool "Enable full-sized data structures for core" if EXPERT
1241 Disabling this option reduces the size of miscellaneous core
1242 kernel data structures. This saves memory on small machines,
1243 but may reduce performance.
1246 bool "Enable futex support" if EXPERT
1250 Disabling this option will cause the kernel to be built without
1251 support for "fast userspace mutexes". The resulting kernel may not
1252 run glibc-based applications correctly.
1255 bool "Enable eventpoll support" if EXPERT
1259 Disabling this option will cause the kernel to be built without
1260 support for epoll family of system calls.
1263 bool "Enable signalfd() system call" if EXPERT
1267 Enable the signalfd() system call that allows to receive signals
1268 on a file descriptor.
1273 bool "Enable timerfd() system call" if EXPERT
1277 Enable the timerfd() system call that allows to receive timer
1278 events on a file descriptor.
1283 bool "Enable eventfd() system call" if EXPERT
1287 Enable the eventfd() system call that allows to receive both
1288 kernel notification (ie. KAIO) or userspace notifications.
1293 bool "Use full shmem filesystem" if EXPERT
1297 The shmem is an internal filesystem used to manage shared memory.
1298 It is backed by swap and manages resource limits. It is also exported
1299 to userspace as tmpfs if TMPFS is enabled. Disabling this
1300 option replaces shmem and tmpfs with the much simpler ramfs code,
1301 which may be appropriate on small systems without swap.
1304 bool "Enable AIO support" if EXPERT
1307 This option enables POSIX asynchronous I/O which may by used
1308 by some high performance threaded applications. Disabling
1309 this option saves about 7k.
1312 bool "Embedded system"
1315 This option should be enabled if compiling the kernel for
1316 an embedded system so certain expert options are available
1319 config HAVE_PERF_EVENTS
1322 See tools/perf/design.txt for details.
1324 config PERF_USE_VMALLOC
1327 See tools/perf/design.txt for details
1329 menu "Kernel Performance Events And Counters"
1332 bool "Kernel performance events and counters"
1333 default y if PROFILING
1334 depends on HAVE_PERF_EVENTS
1338 Enable kernel support for various performance events provided
1339 by software and hardware.
1341 Software events are supported either built-in or via the
1342 use of generic tracepoints.
1344 Most modern CPUs support performance events via performance
1345 counter registers. These registers count the number of certain
1346 types of hw events: such as instructions executed, cachemisses
1347 suffered, or branches mis-predicted - without slowing down the
1348 kernel or applications. These registers can also trigger interrupts
1349 when a threshold number of events have passed - and can thus be
1350 used to profile the code that runs on that CPU.
1352 The Linux Performance Event subsystem provides an abstraction of
1353 these software and hardware event capabilities, available via a
1354 system call and used by the "perf" utility in tools/perf/. It
1355 provides per task and per CPU counters, and it provides event
1356 capabilities on top of those.
1360 config DEBUG_PERF_USE_VMALLOC
1362 bool "Debug: use vmalloc to back perf mmap() buffers"
1363 depends on PERF_EVENTS && DEBUG_KERNEL
1364 select PERF_USE_VMALLOC
1366 Use vmalloc memory to back perf mmap() buffers.
1368 Mostly useful for debugging the vmalloc code on platforms
1369 that don't require it.
1375 config VM_EVENT_COUNTERS
1377 bool "Enable VM event counters for /proc/vmstat" if EXPERT
1379 VM event counters are needed for event counts to be shown.
1380 This option allows the disabling of the VM event counters
1381 on EXPERT systems. /proc/vmstat will only show page counts
1382 if VM event counters are disabled.
1386 bool "Enable PCI quirk workarounds" if EXPERT
1389 This enables workarounds for various PCI chipset
1390 bugs/quirks. Disable this only if your target machine is
1391 unaffected by PCI quirks.
1395 bool "Enable SLUB debugging support" if EXPERT
1396 depends on SLUB && SYSFS
1398 SLUB has extensive debug support features. Disabling these can
1399 result in significant savings in code size. This also disables
1400 SLUB sysfs support. /sys/slab will not exist and there will be
1401 no support for cache validation etc.
1404 bool "Disable heap randomization"
1407 Randomizing heap placement makes heap exploits harder, but it
1408 also breaks ancient binaries (including anything libc5 based).
1409 This option changes the bootup default to heap randomization
1410 disabled, and can be overridden at runtime by setting
1411 /proc/sys/kernel/randomize_va_space to 2.
1413 On non-ancient distros (post-2000 ones) N is usually a safe choice.
1416 prompt "Choose SLAB allocator"
1419 This option allows to select a slab allocator.
1424 The regular slab allocator that is established and known to work
1425 well in all environments. It organizes cache hot objects in
1426 per cpu and per node queues.
1429 bool "SLUB (Unqueued Allocator)"
1431 SLUB is a slab allocator that minimizes cache line usage
1432 instead of managing queues of cached objects (SLAB approach).
1433 Per cpu caching is realized using slabs of objects instead
1434 of queues of objects. SLUB can use memory efficiently
1435 and has enhanced diagnostics. SLUB is the default choice for
1440 bool "SLOB (Simple Allocator)"
1442 SLOB replaces the stock allocator with a drastically simpler
1443 allocator. SLOB is generally more space efficient but
1444 does not perform as well on large systems.
1448 config MMAP_ALLOW_UNINITIALIZED
1449 bool "Allow mmapped anonymous memory to be uninitialized"
1450 depends on EXPERT && !MMU
1453 Normally, and according to the Linux spec, anonymous memory obtained
1454 from mmap() has it's contents cleared before it is passed to
1455 userspace. Enabling this config option allows you to request that
1456 mmap() skip that if it is given an MAP_UNINITIALIZED flag, thus
1457 providing a huge performance boost. If this option is not enabled,
1458 then the flag will be ignored.
1460 This is taken advantage of by uClibc's malloc(), and also by
1461 ELF-FDPIC binfmt's brk and stack allocator.
1463 Because of the obvious security issues, this option should only be
1464 enabled on embedded devices where you control what is run in
1465 userspace. Since that isn't generally a problem on no-MMU systems,
1466 it is normally safe to say Y here.
1468 See Documentation/nommu-mmap.txt for more information.
1471 bool "Profiling support"
1473 Say Y here to enable the extended profiling support mechanisms used
1474 by profilers such as OProfile.
1477 # Place an empty function call at each tracepoint site. Can be
1478 # dynamically changed for a probe function.
1483 source "arch/Kconfig"
1485 endmenu # General setup
1487 config HAVE_GENERIC_DMA_COHERENT
1494 depends on SLAB || SLUB_DEBUG
1502 default 0 if BASE_FULL
1503 default 1 if !BASE_FULL
1506 bool "Enable loadable module support"
1508 Kernel modules are small pieces of compiled code which can
1509 be inserted in the running kernel, rather than being
1510 permanently built into the kernel. You use the "modprobe"
1511 tool to add (and sometimes remove) them. If you say Y here,
1512 many parts of the kernel can be built as modules (by
1513 answering M instead of Y where indicated): this is most
1514 useful for infrequently used options which are not required
1515 for booting. For more information, see the man pages for
1516 modprobe, lsmod, modinfo, insmod and rmmod.
1518 If you say Y here, you will need to run "make
1519 modules_install" to put the modules under /lib/modules/
1520 where modprobe can find them (you may need to be root to do
1527 config MODULE_FORCE_LOAD
1528 bool "Forced module loading"
1531 Allow loading of modules without version information (ie. modprobe
1532 --force). Forced module loading sets the 'F' (forced) taint flag and
1533 is usually a really bad idea.
1535 config MODULE_UNLOAD
1536 bool "Module unloading"
1538 Without this option you will not be able to unload any
1539 modules (note that some modules may not be unloadable
1540 anyway), which makes your kernel smaller, faster
1541 and simpler. If unsure, say Y.
1543 config MODULE_FORCE_UNLOAD
1544 bool "Forced module unloading"
1545 depends on MODULE_UNLOAD && EXPERIMENTAL
1547 This option allows you to force a module to unload, even if the
1548 kernel believes it is unsafe: the kernel will remove the module
1549 without waiting for anyone to stop using it (using the -f option to
1550 rmmod). This is mainly for kernel developers and desperate users.
1554 bool "Module versioning support"
1556 Usually, you have to use modules compiled with your kernel.
1557 Saying Y here makes it sometimes possible to use modules
1558 compiled for different kernels, by adding enough information
1559 to the modules to (hopefully) spot any changes which would
1560 make them incompatible with the kernel you are running. If
1563 config MODULE_SRCVERSION_ALL
1564 bool "Source checksum for all modules"
1566 Modules which contain a MODULE_VERSION get an extra "srcversion"
1567 field inserted into their modinfo section, which contains a
1568 sum of the source files which made it. This helps maintainers
1569 see exactly which source was used to build a module (since
1570 others sometimes change the module source without updating
1571 the version). With this option, such a "srcversion" field
1572 will be created for all modules. If unsure, say N.
1576 config INIT_ALL_POSSIBLE
1579 Back when each arch used to define their own cpu_online_mask and
1580 cpu_possible_mask, some of them chose to initialize cpu_possible_mask
1581 with all 1s, and others with all 0s. When they were centralised,
1582 it was better to provide this option than to break all the archs
1583 and have several arch maintainers pursuing me down dark alleys.
1588 depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
1590 Need stop_machine() primitive.
1592 source "block/Kconfig"
1594 config PREEMPT_NOTIFIERS
1601 source "kernel/Kconfig.locks"