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 choices. 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 This compression algorithm's ratio is best. Decompression speed
180 is between gzip and bzip2. Compression is slowest.
181 The kernel size is about 33% smaller with LZMA in comparison to gzip.
185 depends on HAVE_KERNEL_XZ
187 XZ uses the LZMA2 algorithm and instruction set specific
188 BCJ filters which can improve compression ratio of executable
189 code. The size of the kernel is about 30% smaller with XZ in
190 comparison to gzip. On architectures for which there is a BCJ
191 filter (i386, x86_64, ARM, IA-64, PowerPC, and SPARC), XZ
192 will create a few percent smaller kernel than plain LZMA.
194 The speed is about the same as with LZMA: The decompression
195 speed of XZ is better than that of bzip2 but worse than gzip
196 and LZO. Compression is slow.
200 depends on HAVE_KERNEL_LZO
202 Its compression ratio is the poorest among the choices. The kernel
203 size is about 10% bigger than gzip; however its speed
204 (both compression and decompression) is the fastest.
208 config DEFAULT_HOSTNAME
209 string "Default hostname"
212 This option determines the default system hostname before userspace
213 calls sethostname(2). The kernel traditionally uses "(none)" here,
214 but you may wish to use a different default here to make a minimal
215 system more usable with less configuration.
218 bool "Support for paging of anonymous memory (swap)"
219 depends on MMU && BLOCK
222 This option allows you to choose whether you want to have support
223 for so called swap devices or swap files in your kernel that are
224 used to provide more virtual memory than the actual RAM present
225 in your computer. If unsure say Y.
230 Inter Process Communication is a suite of library functions and
231 system calls which let processes (running programs) synchronize and
232 exchange information. It is generally considered to be a good thing,
233 and some programs won't run unless you say Y here. In particular, if
234 you want to run the DOS emulator dosemu under Linux (read the
235 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
236 you'll need to say Y here.
238 You can find documentation about IPC with "info ipc" and also in
239 section 6.4 of the Linux Programmer's Guide, available from
240 <http://www.tldp.org/guides.html>.
242 config SYSVIPC_SYSCTL
249 bool "POSIX Message Queues"
250 depends on NET && EXPERIMENTAL
252 POSIX variant of message queues is a part of IPC. In POSIX message
253 queues every message has a priority which decides about succession
254 of receiving it by a process. If you want to compile and run
255 programs written e.g. for Solaris with use of its POSIX message
256 queues (functions mq_*) say Y here.
258 POSIX message queues are visible as a filesystem called 'mqueue'
259 and can be mounted somewhere if you want to do filesystem
260 operations on message queues.
264 config POSIX_MQUEUE_SYSCTL
266 depends on POSIX_MQUEUE
271 bool "open by fhandle syscalls"
274 If you say Y here, a user level program will be able to map
275 file names to handle and then later use the handle for
276 different file system operations. This is useful in implementing
277 userspace file servers, which now track files using handles instead
278 of names. The handle would remain the same even if file names
279 get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2)
283 bool "Auditing support"
286 Enable auditing infrastructure that can be used with another
287 kernel subsystem, such as SELinux (which requires this for
288 logging of avc messages output). Does not do system-call
289 auditing without CONFIG_AUDITSYSCALL.
292 bool "Enable system-call auditing support"
293 depends on AUDIT && (X86 || PPC || S390 || IA64 || UML || SPARC64 || SUPERH || (ARM && AEABI && !OABI_COMPAT))
294 default y if SECURITY_SELINUX
296 Enable low-overhead system-call auditing infrastructure that
297 can be used independently or with another kernel subsystem,
302 depends on AUDITSYSCALL
307 depends on AUDITSYSCALL
310 config AUDIT_LOGINUID_IMMUTABLE
311 bool "Make audit loginuid immutable"
314 The config option toggles if a task setting its loginuid requires
315 CAP_SYS_AUDITCONTROL or if that task should require no special permissions
316 but should instead only allow setting its loginuid if it was never
317 previously set. On systems which use systemd or a similar central
318 process to restart login services this should be set to true. On older
319 systems in which an admin would typically have to directly stop and
320 start processes this should be set to false. Setting this to true allows
321 one to drop potentially dangerous capabilites from the login tasks,
322 but may not be backwards compatible with older init systems.
324 source "kernel/irq/Kconfig"
325 source "kernel/time/Kconfig"
327 menu "CPU/Task time and stats accounting"
330 prompt "Cputime accounting"
331 default TICK_CPU_ACCOUNTING if !PPC64
332 default VIRT_CPU_ACCOUNTING if PPC64
334 # Kind of a stub config for the pure tick based cputime accounting
335 config TICK_CPU_ACCOUNTING
336 bool "Simple tick based cputime accounting"
339 This is the basic tick based cputime accounting that maintains
340 statistics about user, system and idle time spent on per jiffies
345 config VIRT_CPU_ACCOUNTING
346 bool "Deterministic task and CPU time accounting"
347 depends on HAVE_VIRT_CPU_ACCOUNTING
349 Select this option to enable more accurate task and CPU time
350 accounting. This is done by reading a CPU counter on each
351 kernel entry and exit and on transitions within the kernel
352 between system, softirq and hardirq state, so there is a
353 small performance impact. In the case of s390 or IBM POWER > 5,
354 this also enables accounting of stolen time on logically-partitioned
357 config IRQ_TIME_ACCOUNTING
358 bool "Fine granularity task level IRQ time accounting"
359 depends on HAVE_IRQ_TIME_ACCOUNTING
361 Select this option to enable fine granularity task irq time
362 accounting. This is done by reading a timestamp on each
363 transitions between softirq and hardirq state, so there can be a
364 small performance impact.
366 If in doubt, say N here.
370 config BSD_PROCESS_ACCT
371 bool "BSD Process Accounting"
373 If you say Y here, a user level program will be able to instruct the
374 kernel (via a special system call) to write process accounting
375 information to a file: whenever a process exits, information about
376 that process will be appended to the file by the kernel. The
377 information includes things such as creation time, owning user,
378 command name, memory usage, controlling terminal etc. (the complete
379 list is in the struct acct in <file:include/linux/acct.h>). It is
380 up to the user level program to do useful things with this
381 information. This is generally a good idea, so say Y.
383 config BSD_PROCESS_ACCT_V3
384 bool "BSD Process Accounting version 3 file format"
385 depends on BSD_PROCESS_ACCT
388 If you say Y here, the process accounting information is written
389 in a new file format that also logs the process IDs of each
390 process and it's parent. Note that this file format is incompatible
391 with previous v0/v1/v2 file formats, so you will need updated tools
392 for processing it. A preliminary version of these tools is available
393 at <http://www.gnu.org/software/acct/>.
396 bool "Export task/process statistics through netlink (EXPERIMENTAL)"
400 Export selected statistics for tasks/processes through the
401 generic netlink interface. Unlike BSD process accounting, the
402 statistics are available during the lifetime of tasks/processes as
403 responses to commands. Like BSD accounting, they are sent to user
408 config TASK_DELAY_ACCT
409 bool "Enable per-task delay accounting (EXPERIMENTAL)"
412 Collect information on time spent by a task waiting for system
413 resources like cpu, synchronous block I/O completion and swapping
414 in pages. Such statistics can help in setting a task's priorities
415 relative to other tasks for cpu, io, rss limits etc.
420 bool "Enable extended accounting over taskstats (EXPERIMENTAL)"
423 Collect extended task accounting data and send the data
424 to userland for processing over the taskstats interface.
428 config TASK_IO_ACCOUNTING
429 bool "Enable per-task storage I/O accounting (EXPERIMENTAL)"
430 depends on TASK_XACCT
432 Collect information on the number of bytes of storage I/O which this
437 endmenu # "CPU/Task time and stats accounting"
442 prompt "RCU Implementation"
446 bool "Tree-based hierarchical RCU"
447 depends on !PREEMPT && SMP
449 This option selects the RCU implementation that is
450 designed for very large SMP system with hundreds or
451 thousands of CPUs. It also scales down nicely to
454 config TREE_PREEMPT_RCU
455 bool "Preemptible tree-based hierarchical RCU"
456 depends on PREEMPT && SMP
458 This option selects the RCU implementation that is
459 designed for very large SMP systems with hundreds or
460 thousands of CPUs, but for which real-time response
461 is also required. It also scales down nicely to
465 bool "UP-only small-memory-footprint RCU"
466 depends on !PREEMPT && !SMP
468 This option selects the RCU implementation that is
469 designed for UP systems from which real-time response
470 is not required. This option greatly reduces the
471 memory footprint of RCU.
473 config TINY_PREEMPT_RCU
474 bool "Preemptible UP-only small-memory-footprint RCU"
475 depends on PREEMPT && !SMP
477 This option selects the RCU implementation that is designed
478 for real-time UP systems. This option greatly reduces the
479 memory footprint of RCU.
484 def_bool ( TREE_PREEMPT_RCU || TINY_PREEMPT_RCU )
486 This option enables preemptible-RCU code that is common between
487 the TREE_PREEMPT_RCU and TINY_PREEMPT_RCU implementations.
490 bool "Consider userspace as in RCU extended quiescent state"
491 depends on HAVE_RCU_USER_QS && SMP
493 This option sets hooks on kernel / userspace boundaries and
494 puts RCU in extended quiescent state when the CPU runs in
495 userspace. It means that when a CPU runs in userspace, it is
496 excluded from the global RCU state machine and thus doesn't
497 to keep the timer tick on for RCU.
499 config RCU_USER_QS_FORCE
500 bool "Force userspace extended QS by default"
501 depends on RCU_USER_QS
503 Set the hooks in user/kernel boundaries by default in order to
504 test this feature that treats userspace as an extended quiescent
505 state until we have a real user like a full adaptive nohz option.
508 int "Tree-based hierarchical RCU fanout value"
511 depends on TREE_RCU || TREE_PREEMPT_RCU
515 This option controls the fanout of hierarchical implementations
516 of RCU, allowing RCU to work efficiently on machines with
517 large numbers of CPUs. This value must be at least the fourth
518 root of NR_CPUS, which allows NR_CPUS to be insanely large.
519 The default value of RCU_FANOUT should be used for production
520 systems, but if you are stress-testing the RCU implementation
521 itself, small RCU_FANOUT values allow you to test large-system
522 code paths on small(er) systems.
524 Select a specific number if testing RCU itself.
525 Take the default if unsure.
527 config RCU_FANOUT_LEAF
528 int "Tree-based hierarchical RCU leaf-level fanout value"
529 range 2 RCU_FANOUT if 64BIT
530 range 2 RCU_FANOUT if !64BIT
531 depends on TREE_RCU || TREE_PREEMPT_RCU
534 This option controls the leaf-level fanout of hierarchical
535 implementations of RCU, and allows trading off cache misses
536 against lock contention. Systems that synchronize their
537 scheduling-clock interrupts for energy-efficiency reasons will
538 want the default because the smaller leaf-level fanout keeps
539 lock contention levels acceptably low. Very large systems
540 (hundreds or thousands of CPUs) will instead want to set this
541 value to the maximum value possible in order to reduce the
542 number of cache misses incurred during RCU's grace-period
543 initialization. These systems tend to run CPU-bound, and thus
544 are not helped by synchronized interrupts, and thus tend to
545 skew them, which reduces lock contention enough that large
546 leaf-level fanouts work well.
548 Select a specific number if testing RCU itself.
550 Select the maximum permissible value for large systems.
552 Take the default if unsure.
554 config RCU_FANOUT_EXACT
555 bool "Disable tree-based hierarchical RCU auto-balancing"
556 depends on TREE_RCU || TREE_PREEMPT_RCU
559 This option forces use of the exact RCU_FANOUT value specified,
560 regardless of imbalances in the hierarchy. This is useful for
561 testing RCU itself, and might one day be useful on systems with
562 strong NUMA behavior.
564 Without RCU_FANOUT_EXACT, the code will balance the hierarchy.
568 config RCU_FAST_NO_HZ
569 bool "Accelerate last non-dyntick-idle CPU's grace periods"
570 depends on NO_HZ && SMP
573 This option causes RCU to attempt to accelerate grace periods
574 in order to allow CPUs to enter dynticks-idle state more
575 quickly. On the other hand, this option increases the overhead
576 of the dynticks-idle checking, particularly on systems with
577 large numbers of CPUs.
579 Say Y if energy efficiency is critically important, particularly
580 if you have relatively few CPUs.
582 Say N if you are unsure.
584 config TREE_RCU_TRACE
585 def_bool RCU_TRACE && ( TREE_RCU || TREE_PREEMPT_RCU )
588 This option provides tracing for the TREE_RCU and
589 TREE_PREEMPT_RCU implementations, permitting Makefile to
590 trivially select kernel/rcutree_trace.c.
593 bool "Enable RCU priority boosting"
594 depends on RT_MUTEXES && PREEMPT_RCU
597 This option boosts the priority of preempted RCU readers that
598 block the current preemptible RCU grace period for too long.
599 This option also prevents heavy loads from blocking RCU
600 callback invocation for all flavors of RCU.
602 Say Y here if you are working with real-time apps or heavy loads
603 Say N here if you are unsure.
605 config RCU_BOOST_PRIO
606 int "Real-time priority to boost RCU readers to"
611 This option specifies the real-time priority to which long-term
612 preempted RCU readers are to be boosted. If you are working
613 with a real-time application that has one or more CPU-bound
614 threads running at a real-time priority level, you should set
615 RCU_BOOST_PRIO to a priority higher then the highest-priority
616 real-time CPU-bound thread. The default RCU_BOOST_PRIO value
617 of 1 is appropriate in the common case, which is real-time
618 applications that do not have any CPU-bound threads.
620 Some real-time applications might not have a single real-time
621 thread that saturates a given CPU, but instead might have
622 multiple real-time threads that, taken together, fully utilize
623 that CPU. In this case, you should set RCU_BOOST_PRIO to
624 a priority higher than the lowest-priority thread that is
625 conspiring to prevent the CPU from running any non-real-time
626 tasks. For example, if one thread at priority 10 and another
627 thread at priority 5 are between themselves fully consuming
628 the CPU time on a given CPU, then RCU_BOOST_PRIO should be
629 set to priority 6 or higher.
631 Specify the real-time priority, or take the default if unsure.
633 config RCU_BOOST_DELAY
634 int "Milliseconds to delay boosting after RCU grace-period start"
639 This option specifies the time to wait after the beginning of
640 a given grace period before priority-boosting preempted RCU
641 readers blocking that grace period. Note that any RCU reader
642 blocking an expedited RCU grace period is boosted immediately.
644 Accept the default if unsure.
646 endmenu # "RCU Subsystem"
649 tristate "Kernel .config support"
651 This option enables the complete Linux kernel ".config" file
652 contents to be saved in the kernel. It provides documentation
653 of which kernel options are used in a running kernel or in an
654 on-disk kernel. This information can be extracted from the kernel
655 image file with the script scripts/extract-ikconfig and used as
656 input to rebuild the current kernel or to build another kernel.
657 It can also be extracted from a running kernel by reading
658 /proc/config.gz if enabled (below).
661 bool "Enable access to .config through /proc/config.gz"
662 depends on IKCONFIG && PROC_FS
664 This option enables access to the kernel configuration file
665 through /proc/config.gz.
668 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
672 Select kernel log buffer size as a power of 2.
682 # Architectures with an unreliable sched_clock() should select this:
684 config HAVE_UNSTABLE_SCHED_CLOCK
688 boolean "Control Group support"
691 This option adds support for grouping sets of processes together, for
692 use with process control subsystems such as Cpusets, CFS, memory
693 controls or device isolation.
695 - Documentation/scheduler/sched-design-CFS.txt (CFS)
696 - Documentation/cgroups/ (features for grouping, isolation
697 and resource control)
704 bool "Example debug cgroup subsystem"
707 This option enables a simple cgroup subsystem that
708 exports useful debugging information about the cgroups
713 config CGROUP_FREEZER
714 bool "Freezer cgroup subsystem"
716 Provides a way to freeze and unfreeze all tasks in a
720 bool "Device controller for cgroups"
722 Provides a cgroup implementing whitelists for devices which
723 a process in the cgroup can mknod or open.
726 bool "Cpuset support"
728 This option will let you create and manage CPUSETs which
729 allow dynamically partitioning a system into sets of CPUs and
730 Memory Nodes and assigning tasks to run only within those sets.
731 This is primarily useful on large SMP or NUMA systems.
735 config PROC_PID_CPUSET
736 bool "Include legacy /proc/<pid>/cpuset file"
740 config CGROUP_CPUACCT
741 bool "Simple CPU accounting cgroup subsystem"
743 Provides a simple Resource Controller for monitoring the
744 total CPU consumed by the tasks in a cgroup.
746 config RESOURCE_COUNTERS
747 bool "Resource counters"
749 This option enables controller independent resource accounting
750 infrastructure that works with cgroups.
753 bool "Memory Resource Controller for Control Groups"
754 depends on RESOURCE_COUNTERS
757 Provides a memory resource controller that manages both anonymous
758 memory and page cache. (See Documentation/cgroups/memory.txt)
760 Note that setting this option increases fixed memory overhead
761 associated with each page of memory in the system. By this,
762 20(40)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
763 usage tracking struct at boot. Total amount of this is printed out
766 Only enable when you're ok with these trade offs and really
767 sure you need the memory resource controller. Even when you enable
768 this, you can set "cgroup_disable=memory" at your boot option to
769 disable memory resource controller and you can avoid overheads.
770 (and lose benefits of memory resource controller)
772 This config option also selects MM_OWNER config option, which
773 could in turn add some fork/exit overhead.
776 bool "Memory Resource Controller Swap Extension"
777 depends on MEMCG && SWAP
779 Add swap management feature to memory resource controller. When you
780 enable this, you can limit mem+swap usage per cgroup. In other words,
781 when you disable this, memory resource controller has no cares to
782 usage of swap...a process can exhaust all of the swap. This extension
783 is useful when you want to avoid exhaustion swap but this itself
784 adds more overheads and consumes memory for remembering information.
785 Especially if you use 32bit system or small memory system, please
786 be careful about enabling this. When memory resource controller
787 is disabled by boot option, this will be automatically disabled and
788 there will be no overhead from this. Even when you set this config=y,
789 if boot option "swapaccount=0" is set, swap will not be accounted.
790 Now, memory usage of swap_cgroup is 2 bytes per entry. If swap page
791 size is 4096bytes, 512k per 1Gbytes of swap.
792 config MEMCG_SWAP_ENABLED
793 bool "Memory Resource Controller Swap Extension enabled by default"
794 depends on MEMCG_SWAP
797 Memory Resource Controller Swap Extension comes with its price in
798 a bigger memory consumption. General purpose distribution kernels
799 which want to enable the feature but keep it disabled by default
800 and let the user enable it by swapaccount boot command line
801 parameter should have this option unselected.
802 For those who want to have the feature enabled by default should
803 select this option (if, for some reason, they need to disable it
804 then swapaccount=0 does the trick).
806 bool "Memory Resource Controller Kernel Memory accounting (EXPERIMENTAL)"
807 depends on MEMCG && EXPERIMENTAL
810 The Kernel Memory extension for Memory Resource Controller can limit
811 the amount of memory used by kernel objects in the system. Those are
812 fundamentally different from the entities handled by the standard
813 Memory Controller, which are page-based, and can be swapped. Users of
814 the kmem extension can use it to guarantee that no group of processes
815 will ever exhaust kernel resources alone.
817 config CGROUP_HUGETLB
818 bool "HugeTLB Resource Controller for Control Groups"
819 depends on RESOURCE_COUNTERS && HUGETLB_PAGE && EXPERIMENTAL
822 Provides a cgroup Resource Controller for HugeTLB pages.
823 When you enable this, you can put a per cgroup limit on HugeTLB usage.
824 The limit is enforced during page fault. Since HugeTLB doesn't
825 support page reclaim, enforcing the limit at page fault time implies
826 that, the application will get SIGBUS signal if it tries to access
827 HugeTLB pages beyond its limit. This requires the application to know
828 beforehand how much HugeTLB pages it would require for its use. The
829 control group is tracked in the third page lru pointer. This means
830 that we cannot use the controller with huge page less than 3 pages.
833 bool "Enable perf_event per-cpu per-container group (cgroup) monitoring"
834 depends on PERF_EVENTS && CGROUPS
836 This option extends the per-cpu mode to restrict monitoring to
837 threads which belong to the cgroup specified and run on the
842 menuconfig CGROUP_SCHED
843 bool "Group CPU scheduler"
846 This feature lets CPU scheduler recognize task groups and control CPU
847 bandwidth allocation to such task groups. It uses cgroups to group
851 config FAIR_GROUP_SCHED
852 bool "Group scheduling for SCHED_OTHER"
853 depends on CGROUP_SCHED
857 bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED"
858 depends on EXPERIMENTAL
859 depends on FAIR_GROUP_SCHED
862 This option allows users to define CPU bandwidth rates (limits) for
863 tasks running within the fair group scheduler. Groups with no limit
864 set are considered to be unconstrained and will run with no
866 See tip/Documentation/scheduler/sched-bwc.txt for more information.
868 config RT_GROUP_SCHED
869 bool "Group scheduling for SCHED_RR/FIFO"
870 depends on EXPERIMENTAL
871 depends on CGROUP_SCHED
874 This feature lets you explicitly allocate real CPU bandwidth
875 to task groups. If enabled, it will also make it impossible to
876 schedule realtime tasks for non-root users until you allocate
877 realtime bandwidth for them.
878 See Documentation/scheduler/sched-rt-group.txt for more information.
883 bool "Block IO controller"
887 Generic block IO controller cgroup interface. This is the common
888 cgroup interface which should be used by various IO controlling
891 Currently, CFQ IO scheduler uses it to recognize task groups and
892 control disk bandwidth allocation (proportional time slice allocation)
893 to such task groups. It is also used by bio throttling logic in
894 block layer to implement upper limit in IO rates on a device.
896 This option only enables generic Block IO controller infrastructure.
897 One needs to also enable actual IO controlling logic/policy. For
898 enabling proportional weight division of disk bandwidth in CFQ, set
899 CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
900 CONFIG_BLK_DEV_THROTTLING=y.
902 See Documentation/cgroups/blkio-controller.txt for more information.
904 config DEBUG_BLK_CGROUP
905 bool "Enable Block IO controller debugging"
906 depends on BLK_CGROUP
909 Enable some debugging help. Currently it exports additional stat
910 files in a cgroup which can be useful for debugging.
914 config CHECKPOINT_RESTORE
915 bool "Checkpoint/restore support" if EXPERT
918 Enables additional kernel features in a sake of checkpoint/restore.
919 In particular it adds auxiliary prctl codes to setup process text,
920 data and heap segment sizes, and a few additional /proc filesystem
923 If unsure, say N here.
925 menuconfig NAMESPACES
926 bool "Namespaces support" if EXPERT
929 Provides the way to make tasks work with different objects using
930 the same id. For example same IPC id may refer to different objects
931 or same user id or pid may refer to different tasks when used in
932 different namespaces.
940 In this namespace tasks see different info provided with the
945 depends on (SYSVIPC || POSIX_MQUEUE)
948 In this namespace tasks work with IPC ids which correspond to
949 different IPC objects in different namespaces.
952 bool "User namespace (EXPERIMENTAL)"
953 depends on EXPERIMENTAL
954 depends on UIDGID_CONVERTED
955 select UIDGID_STRICT_TYPE_CHECKS
959 This allows containers, i.e. vservers, to use user namespaces
960 to provide different user info for different servers.
964 bool "PID Namespaces"
967 Support process id namespaces. This allows having multiple
968 processes with the same pid as long as they are in different
969 pid namespaces. This is a building block of containers.
972 bool "Network namespace"
976 Allow user space to create what appear to be multiple instances
977 of the network stack.
981 config UIDGID_CONVERTED
982 # True if all of the selected software conmponents are known
983 # to have uid_t and gid_t converted to kuid_t and kgid_t
984 # where appropriate and are otherwise safe to use with
985 # the user namespace.
990 depends on NET_9P = n
994 depends on AFS_FS = n
995 depends on AUTOFS4_FS = n
996 depends on CEPH_FS = n
998 depends on CODA_FS = n
999 depends on FUSE_FS = n
1000 depends on GFS2_FS = n
1001 depends on NCP_FS = n
1003 depends on NFS_FS = n
1004 depends on OCFS2_FS = n
1005 depends on XFS_FS = n
1007 config UIDGID_STRICT_TYPE_CHECKS
1008 bool "Require conversions between uid/gids and their internal representation"
1009 depends on UIDGID_CONVERTED
1012 While the nececessary conversions are being added to all subsystems this option allows
1013 the code to continue to build for unconverted subsystems.
1015 Say Y here if you want the strict type checking enabled
1017 config SCHED_AUTOGROUP
1018 bool "Automatic process group scheduling"
1022 select FAIR_GROUP_SCHED
1024 This option optimizes the scheduler for common desktop workloads by
1025 automatically creating and populating task groups. This separation
1026 of workloads isolates aggressive CPU burners (like build jobs) from
1027 desktop applications. Task group autogeneration is currently based
1033 config SYSFS_DEPRECATED
1034 bool "Enable deprecated sysfs features to support old userspace tools"
1038 This option adds code that switches the layout of the "block" class
1039 devices, to not show up in /sys/class/block/, but only in
1042 This switch is only active when the sysfs.deprecated=1 boot option is
1043 passed or the SYSFS_DEPRECATED_V2 option is set.
1045 This option allows new kernels to run on old distributions and tools,
1046 which might get confused by /sys/class/block/. Since 2007/2008 all
1047 major distributions and tools handle this just fine.
1049 Recent distributions and userspace tools after 2009/2010 depend on
1050 the existence of /sys/class/block/, and will not work with this
1053 Only if you are using a new kernel on an old distribution, you might
1056 config SYSFS_DEPRECATED_V2
1057 bool "Enable deprecated sysfs features by default"
1060 depends on SYSFS_DEPRECATED
1062 Enable deprecated sysfs by default.
1064 See the CONFIG_SYSFS_DEPRECATED option for more details about this
1067 Only if you are using a new kernel on an old distribution, you might
1068 need to say Y here. Even then, odds are you would not need it
1069 enabled, you can always pass the boot option if absolutely necessary.
1072 bool "Kernel->user space relay support (formerly relayfs)"
1074 This option enables support for relay interface support in
1075 certain file systems (such as debugfs).
1076 It is designed to provide an efficient mechanism for tools and
1077 facilities to relay large amounts of data from kernel space to
1082 config BLK_DEV_INITRD
1083 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
1084 depends on BROKEN || !FRV
1086 The initial RAM filesystem is a ramfs which is loaded by the
1087 boot loader (loadlin or lilo) and that is mounted as root
1088 before the normal boot procedure. It is typically used to
1089 load modules needed to mount the "real" root file system,
1090 etc. See <file:Documentation/initrd.txt> for details.
1092 If RAM disk support (BLK_DEV_RAM) is also included, this
1093 also enables initial RAM disk (initrd) support and adds
1094 15 Kbytes (more on some other architectures) to the kernel size.
1100 source "usr/Kconfig"
1104 config CC_OPTIMIZE_FOR_SIZE
1105 bool "Optimize for size"
1107 Enabling this option will pass "-Os" instead of "-O2" to gcc
1108 resulting in a smaller kernel.
1119 bool "Configure standard kernel features (expert users)"
1120 # Unhide debug options, to make the on-by-default options visible
1123 This option allows certain base kernel options and settings
1124 to be disabled or tweaked. This is for specialized
1125 environments which can tolerate a "non-standard" kernel.
1126 Only use this if you really know what you are doing.
1132 bool "Enable 16-bit UID system calls" if EXPERT
1133 depends on HAVE_UID16
1136 This enables the legacy 16-bit UID syscall wrappers.
1138 config SYSCTL_SYSCALL
1139 bool "Sysctl syscall support" if EXPERT
1140 depends on PROC_SYSCTL
1144 sys_sysctl uses binary paths that have been found challenging
1145 to properly maintain and use. The interface in /proc/sys
1146 using paths with ascii names is now the primary path to this
1149 Almost nothing using the binary sysctl interface so if you are
1150 trying to save some space it is probably safe to disable this,
1151 making your kernel marginally smaller.
1153 If unsure say N here.
1155 config SYSCTL_EXCEPTION_TRACE
1158 Enable support for /proc/sys/debug/exception-trace.
1161 bool "Load all symbols for debugging/ksymoops" if EXPERT
1164 Say Y here to let the kernel print out symbolic crash information and
1165 symbolic stack backtraces. This increases the size of the kernel
1166 somewhat, as all symbols have to be loaded into the kernel image.
1169 bool "Include all symbols in kallsyms"
1170 depends on DEBUG_KERNEL && KALLSYMS
1172 Normally kallsyms only contains the symbols of functions for nicer
1173 OOPS messages and backtraces (i.e., symbols from the text and inittext
1174 sections). This is sufficient for most cases. And only in very rare
1175 cases (e.g., when a debugger is used) all symbols are required (e.g.,
1176 names of variables from the data sections, etc).
1178 This option makes sure that all symbols are loaded into the kernel
1179 image (i.e., symbols from all sections) in cost of increased kernel
1180 size (depending on the kernel configuration, it may be 300KiB or
1181 something like this).
1183 Say N unless you really need all symbols.
1190 bool "Enable support for printk" if EXPERT
1192 This option enables normal printk support. Removing it
1193 eliminates most of the message strings from the kernel image
1194 and makes the kernel more or less silent. As this makes it
1195 very difficult to diagnose system problems, saying N here is
1196 strongly discouraged.
1199 bool "BUG() support" if EXPERT
1202 Disabling this option eliminates support for BUG and WARN, reducing
1203 the size of your kernel image and potentially quietly ignoring
1204 numerous fatal conditions. You should only consider disabling this
1205 option for embedded systems with no facilities for reporting errors.
1211 bool "Enable ELF core dumps" if EXPERT
1213 Enable support for generating core dumps. Disabling saves about 4k.
1216 config PCSPKR_PLATFORM
1217 bool "Enable PC-Speaker support" if EXPERT
1218 depends on HAVE_PCSPKR_PLATFORM
1222 This option allows to disable the internal PC-Speaker
1223 support, saving some memory.
1225 config HAVE_PCSPKR_PLATFORM
1230 bool "Enable full-sized data structures for core" if EXPERT
1232 Disabling this option reduces the size of miscellaneous core
1233 kernel data structures. This saves memory on small machines,
1234 but may reduce performance.
1237 bool "Enable futex support" if EXPERT
1241 Disabling this option will cause the kernel to be built without
1242 support for "fast userspace mutexes". The resulting kernel may not
1243 run glibc-based applications correctly.
1246 bool "Enable eventpoll support" if EXPERT
1250 Disabling this option will cause the kernel to be built without
1251 support for epoll family of system calls.
1254 bool "Enable signalfd() system call" if EXPERT
1258 Enable the signalfd() system call that allows to receive signals
1259 on a file descriptor.
1264 bool "Enable timerfd() system call" if EXPERT
1268 Enable the timerfd() system call that allows to receive timer
1269 events on a file descriptor.
1274 bool "Enable eventfd() system call" if EXPERT
1278 Enable the eventfd() system call that allows to receive both
1279 kernel notification (ie. KAIO) or userspace notifications.
1284 bool "Use full shmem filesystem" if EXPERT
1288 The shmem is an internal filesystem used to manage shared memory.
1289 It is backed by swap and manages resource limits. It is also exported
1290 to userspace as tmpfs if TMPFS is enabled. Disabling this
1291 option replaces shmem and tmpfs with the much simpler ramfs code,
1292 which may be appropriate on small systems without swap.
1295 bool "Enable AIO support" if EXPERT
1298 This option enables POSIX asynchronous I/O which may by used
1299 by some high performance threaded applications. Disabling
1300 this option saves about 7k.
1303 bool "Embedded system"
1306 This option should be enabled if compiling the kernel for
1307 an embedded system so certain expert options are available
1310 config HAVE_PERF_EVENTS
1313 See tools/perf/design.txt for details.
1315 config PERF_USE_VMALLOC
1318 See tools/perf/design.txt for details
1320 menu "Kernel Performance Events And Counters"
1323 bool "Kernel performance events and counters"
1324 default y if PROFILING
1325 depends on HAVE_PERF_EVENTS
1329 Enable kernel support for various performance events provided
1330 by software and hardware.
1332 Software events are supported either built-in or via the
1333 use of generic tracepoints.
1335 Most modern CPUs support performance events via performance
1336 counter registers. These registers count the number of certain
1337 types of hw events: such as instructions executed, cachemisses
1338 suffered, or branches mis-predicted - without slowing down the
1339 kernel or applications. These registers can also trigger interrupts
1340 when a threshold number of events have passed - and can thus be
1341 used to profile the code that runs on that CPU.
1343 The Linux Performance Event subsystem provides an abstraction of
1344 these software and hardware event capabilities, available via a
1345 system call and used by the "perf" utility in tools/perf/. It
1346 provides per task and per CPU counters, and it provides event
1347 capabilities on top of those.
1351 config DEBUG_PERF_USE_VMALLOC
1353 bool "Debug: use vmalloc to back perf mmap() buffers"
1354 depends on PERF_EVENTS && DEBUG_KERNEL
1355 select PERF_USE_VMALLOC
1357 Use vmalloc memory to back perf mmap() buffers.
1359 Mostly useful for debugging the vmalloc code on platforms
1360 that don't require it.
1366 config VM_EVENT_COUNTERS
1368 bool "Enable VM event counters for /proc/vmstat" if EXPERT
1370 VM event counters are needed for event counts to be shown.
1371 This option allows the disabling of the VM event counters
1372 on EXPERT systems. /proc/vmstat will only show page counts
1373 if VM event counters are disabled.
1377 bool "Enable PCI quirk workarounds" if EXPERT
1380 This enables workarounds for various PCI chipset
1381 bugs/quirks. Disable this only if your target machine is
1382 unaffected by PCI quirks.
1386 bool "Enable SLUB debugging support" if EXPERT
1387 depends on SLUB && SYSFS
1389 SLUB has extensive debug support features. Disabling these can
1390 result in significant savings in code size. This also disables
1391 SLUB sysfs support. /sys/slab will not exist and there will be
1392 no support for cache validation etc.
1395 bool "Disable heap randomization"
1398 Randomizing heap placement makes heap exploits harder, but it
1399 also breaks ancient binaries (including anything libc5 based).
1400 This option changes the bootup default to heap randomization
1401 disabled, and can be overridden at runtime by setting
1402 /proc/sys/kernel/randomize_va_space to 2.
1404 On non-ancient distros (post-2000 ones) N is usually a safe choice.
1407 prompt "Choose SLAB allocator"
1410 This option allows to select a slab allocator.
1415 The regular slab allocator that is established and known to work
1416 well in all environments. It organizes cache hot objects in
1417 per cpu and per node queues.
1420 bool "SLUB (Unqueued Allocator)"
1422 SLUB is a slab allocator that minimizes cache line usage
1423 instead of managing queues of cached objects (SLAB approach).
1424 Per cpu caching is realized using slabs of objects instead
1425 of queues of objects. SLUB can use memory efficiently
1426 and has enhanced diagnostics. SLUB is the default choice for
1431 bool "SLOB (Simple Allocator)"
1433 SLOB replaces the stock allocator with a drastically simpler
1434 allocator. SLOB is generally more space efficient but
1435 does not perform as well on large systems.
1439 config MMAP_ALLOW_UNINITIALIZED
1440 bool "Allow mmapped anonymous memory to be uninitialized"
1441 depends on EXPERT && !MMU
1444 Normally, and according to the Linux spec, anonymous memory obtained
1445 from mmap() has it's contents cleared before it is passed to
1446 userspace. Enabling this config option allows you to request that
1447 mmap() skip that if it is given an MAP_UNINITIALIZED flag, thus
1448 providing a huge performance boost. If this option is not enabled,
1449 then the flag will be ignored.
1451 This is taken advantage of by uClibc's malloc(), and also by
1452 ELF-FDPIC binfmt's brk and stack allocator.
1454 Because of the obvious security issues, this option should only be
1455 enabled on embedded devices where you control what is run in
1456 userspace. Since that isn't generally a problem on no-MMU systems,
1457 it is normally safe to say Y here.
1459 See Documentation/nommu-mmap.txt for more information.
1462 bool "Profiling support"
1464 Say Y here to enable the extended profiling support mechanisms used
1465 by profilers such as OProfile.
1468 # Place an empty function call at each tracepoint site. Can be
1469 # dynamically changed for a probe function.
1474 source "arch/Kconfig"
1476 endmenu # General setup
1478 config HAVE_GENERIC_DMA_COHERENT
1485 depends on SLAB || SLUB_DEBUG
1493 default 0 if BASE_FULL
1494 default 1 if !BASE_FULL
1497 bool "Enable loadable module support"
1499 Kernel modules are small pieces of compiled code which can
1500 be inserted in the running kernel, rather than being
1501 permanently built into the kernel. You use the "modprobe"
1502 tool to add (and sometimes remove) them. If you say Y here,
1503 many parts of the kernel can be built as modules (by
1504 answering M instead of Y where indicated): this is most
1505 useful for infrequently used options which are not required
1506 for booting. For more information, see the man pages for
1507 modprobe, lsmod, modinfo, insmod and rmmod.
1509 If you say Y here, you will need to run "make
1510 modules_install" to put the modules under /lib/modules/
1511 where modprobe can find them (you may need to be root to do
1518 config MODULE_FORCE_LOAD
1519 bool "Forced module loading"
1522 Allow loading of modules without version information (ie. modprobe
1523 --force). Forced module loading sets the 'F' (forced) taint flag and
1524 is usually a really bad idea.
1526 config MODULE_UNLOAD
1527 bool "Module unloading"
1529 Without this option you will not be able to unload any
1530 modules (note that some modules may not be unloadable
1531 anyway), which makes your kernel smaller, faster
1532 and simpler. If unsure, say Y.
1534 config MODULE_FORCE_UNLOAD
1535 bool "Forced module unloading"
1536 depends on MODULE_UNLOAD && EXPERIMENTAL
1538 This option allows you to force a module to unload, even if the
1539 kernel believes it is unsafe: the kernel will remove the module
1540 without waiting for anyone to stop using it (using the -f option to
1541 rmmod). This is mainly for kernel developers and desperate users.
1545 bool "Module versioning support"
1547 Usually, you have to use modules compiled with your kernel.
1548 Saying Y here makes it sometimes possible to use modules
1549 compiled for different kernels, by adding enough information
1550 to the modules to (hopefully) spot any changes which would
1551 make them incompatible with the kernel you are running. If
1554 config MODULE_SRCVERSION_ALL
1555 bool "Source checksum for all modules"
1557 Modules which contain a MODULE_VERSION get an extra "srcversion"
1558 field inserted into their modinfo section, which contains a
1559 sum of the source files which made it. This helps maintainers
1560 see exactly which source was used to build a module (since
1561 others sometimes change the module source without updating
1562 the version). With this option, such a "srcversion" field
1563 will be created for all modules. If unsure, say N.
1567 config INIT_ALL_POSSIBLE
1570 Back when each arch used to define their own cpu_online_mask and
1571 cpu_possible_mask, some of them chose to initialize cpu_possible_mask
1572 with all 1s, and others with all 0s. When they were centralised,
1573 it was better to provide this option than to break all the archs
1574 and have several arch maintainers pursuing me down dark alleys.
1579 depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
1581 Need stop_machine() primitive.
1583 source "block/Kconfig"
1585 config PREEMPT_NOTIFIERS
1592 # Can be selected by architectures with broken toolchains
1593 # that get confused by correct const<->read_only section
1595 config BROKEN_RODATA
1598 source "kernel/Kconfig.locks"
projects / profile / ivi / kernel-adaptation-intel-automotive.git / blob