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"
329 config VIRT_CPU_ACCOUNTING
333 prompt "Cputime accounting"
334 default TICK_CPU_ACCOUNTING if !PPC64
335 default VIRT_CPU_ACCOUNTING_NATIVE if PPC64
337 # Kind of a stub config for the pure tick based cputime accounting
338 config TICK_CPU_ACCOUNTING
339 bool "Simple tick based cputime accounting"
342 This is the basic tick based cputime accounting that maintains
343 statistics about user, system and idle time spent on per jiffies
348 config VIRT_CPU_ACCOUNTING_NATIVE
349 bool "Deterministic task and CPU time accounting"
350 depends on HAVE_VIRT_CPU_ACCOUNTING
351 select VIRT_CPU_ACCOUNTING
353 Select this option to enable more accurate task and CPU time
354 accounting. This is done by reading a CPU counter on each
355 kernel entry and exit and on transitions within the kernel
356 between system, softirq and hardirq state, so there is a
357 small performance impact. In the case of s390 or IBM POWER > 5,
358 this also enables accounting of stolen time on logically-partitioned
361 config VIRT_CPU_ACCOUNTING_GEN
362 bool "Full dynticks CPU time accounting"
363 depends on HAVE_CONTEXT_TRACKING && 64BIT
364 select VIRT_CPU_ACCOUNTING
365 select CONTEXT_TRACKING
367 Select this option to enable task and CPU time accounting on full
368 dynticks systems. This accounting is implemented by watching every
369 kernel-user boundaries using the context tracking subsystem.
370 The accounting is thus performed at the expense of some significant
373 For now this is only useful if you are working on the full
374 dynticks subsystem development.
378 config IRQ_TIME_ACCOUNTING
379 bool "Fine granularity task level IRQ time accounting"
380 depends on HAVE_IRQ_TIME_ACCOUNTING
382 Select this option to enable fine granularity task irq time
383 accounting. This is done by reading a timestamp on each
384 transitions between softirq and hardirq state, so there can be a
385 small performance impact.
387 If in doubt, say N here.
391 config BSD_PROCESS_ACCT
392 bool "BSD Process Accounting"
394 If you say Y here, a user level program will be able to instruct the
395 kernel (via a special system call) to write process accounting
396 information to a file: whenever a process exits, information about
397 that process will be appended to the file by the kernel. The
398 information includes things such as creation time, owning user,
399 command name, memory usage, controlling terminal etc. (the complete
400 list is in the struct acct in <file:include/linux/acct.h>). It is
401 up to the user level program to do useful things with this
402 information. This is generally a good idea, so say Y.
404 config BSD_PROCESS_ACCT_V3
405 bool "BSD Process Accounting version 3 file format"
406 depends on BSD_PROCESS_ACCT
409 If you say Y here, the process accounting information is written
410 in a new file format that also logs the process IDs of each
411 process and it's parent. Note that this file format is incompatible
412 with previous v0/v1/v2 file formats, so you will need updated tools
413 for processing it. A preliminary version of these tools is available
414 at <http://www.gnu.org/software/acct/>.
417 bool "Export task/process statistics through netlink (EXPERIMENTAL)"
421 Export selected statistics for tasks/processes through the
422 generic netlink interface. Unlike BSD process accounting, the
423 statistics are available during the lifetime of tasks/processes as
424 responses to commands. Like BSD accounting, they are sent to user
429 config TASK_DELAY_ACCT
430 bool "Enable per-task delay accounting (EXPERIMENTAL)"
433 Collect information on time spent by a task waiting for system
434 resources like cpu, synchronous block I/O completion and swapping
435 in pages. Such statistics can help in setting a task's priorities
436 relative to other tasks for cpu, io, rss limits etc.
441 bool "Enable extended accounting over taskstats (EXPERIMENTAL)"
444 Collect extended task accounting data and send the data
445 to userland for processing over the taskstats interface.
449 config TASK_IO_ACCOUNTING
450 bool "Enable per-task storage I/O accounting (EXPERIMENTAL)"
451 depends on TASK_XACCT
453 Collect information on the number of bytes of storage I/O which this
458 endmenu # "CPU/Task time and stats accounting"
463 prompt "RCU Implementation"
467 bool "Tree-based hierarchical RCU"
468 depends on !PREEMPT && SMP
470 This option selects the RCU implementation that is
471 designed for very large SMP system with hundreds or
472 thousands of CPUs. It also scales down nicely to
475 config TREE_PREEMPT_RCU
476 bool "Preemptible tree-based hierarchical RCU"
477 depends on PREEMPT && SMP
479 This option selects the RCU implementation that is
480 designed for very large SMP systems with hundreds or
481 thousands of CPUs, but for which real-time response
482 is also required. It also scales down nicely to
486 bool "UP-only small-memory-footprint RCU"
487 depends on !PREEMPT && !SMP
489 This option selects the RCU implementation that is
490 designed for UP systems from which real-time response
491 is not required. This option greatly reduces the
492 memory footprint of RCU.
494 config TINY_PREEMPT_RCU
495 bool "Preemptible UP-only small-memory-footprint RCU"
496 depends on PREEMPT && !SMP
498 This option selects the RCU implementation that is designed
499 for real-time UP systems. This option greatly reduces the
500 memory footprint of RCU.
505 def_bool ( TREE_PREEMPT_RCU || TINY_PREEMPT_RCU )
507 This option enables preemptible-RCU code that is common between
508 the TREE_PREEMPT_RCU and TINY_PREEMPT_RCU implementations.
510 config CONTEXT_TRACKING
514 bool "Consider userspace as in RCU extended quiescent state"
515 depends on HAVE_CONTEXT_TRACKING && SMP
516 select CONTEXT_TRACKING
518 This option sets hooks on kernel / userspace boundaries and
519 puts RCU in extended quiescent state when the CPU runs in
520 userspace. It means that when a CPU runs in userspace, it is
521 excluded from the global RCU state machine and thus doesn't
522 try to keep the timer tick on for RCU.
524 Unless you want to hack and help the development of the full
525 dynticks mode, you shouldn't enable this option. It also
526 adds unnecessary overhead.
530 config CONTEXT_TRACKING_FORCE
531 bool "Force context tracking"
532 depends on CONTEXT_TRACKING
534 Probe on user/kernel boundaries by default in order to
535 test the features that rely on it such as userspace RCU extended
537 This test is there for debugging until we have a real user like the
541 int "Tree-based hierarchical RCU fanout value"
544 depends on TREE_RCU || TREE_PREEMPT_RCU
548 This option controls the fanout of hierarchical implementations
549 of RCU, allowing RCU to work efficiently on machines with
550 large numbers of CPUs. This value must be at least the fourth
551 root of NR_CPUS, which allows NR_CPUS to be insanely large.
552 The default value of RCU_FANOUT should be used for production
553 systems, but if you are stress-testing the RCU implementation
554 itself, small RCU_FANOUT values allow you to test large-system
555 code paths on small(er) systems.
557 Select a specific number if testing RCU itself.
558 Take the default if unsure.
560 config RCU_FANOUT_LEAF
561 int "Tree-based hierarchical RCU leaf-level fanout value"
562 range 2 RCU_FANOUT if 64BIT
563 range 2 RCU_FANOUT if !64BIT
564 depends on TREE_RCU || TREE_PREEMPT_RCU
567 This option controls the leaf-level fanout of hierarchical
568 implementations of RCU, and allows trading off cache misses
569 against lock contention. Systems that synchronize their
570 scheduling-clock interrupts for energy-efficiency reasons will
571 want the default because the smaller leaf-level fanout keeps
572 lock contention levels acceptably low. Very large systems
573 (hundreds or thousands of CPUs) will instead want to set this
574 value to the maximum value possible in order to reduce the
575 number of cache misses incurred during RCU's grace-period
576 initialization. These systems tend to run CPU-bound, and thus
577 are not helped by synchronized interrupts, and thus tend to
578 skew them, which reduces lock contention enough that large
579 leaf-level fanouts work well.
581 Select a specific number if testing RCU itself.
583 Select the maximum permissible value for large systems.
585 Take the default if unsure.
587 config RCU_FANOUT_EXACT
588 bool "Disable tree-based hierarchical RCU auto-balancing"
589 depends on TREE_RCU || TREE_PREEMPT_RCU
592 This option forces use of the exact RCU_FANOUT value specified,
593 regardless of imbalances in the hierarchy. This is useful for
594 testing RCU itself, and might one day be useful on systems with
595 strong NUMA behavior.
597 Without RCU_FANOUT_EXACT, the code will balance the hierarchy.
601 config RCU_FAST_NO_HZ
602 bool "Accelerate last non-dyntick-idle CPU's grace periods"
603 depends on NO_HZ && SMP
606 This option causes RCU to attempt to accelerate grace periods in
607 order to allow CPUs to enter dynticks-idle state more quickly.
608 On the other hand, this option increases the overhead of the
609 dynticks-idle checking, thus degrading scheduling latency.
611 Say Y if energy efficiency is critically important, and you don't
612 care about real-time response.
614 Say N if you are unsure.
616 config TREE_RCU_TRACE
617 def_bool RCU_TRACE && ( TREE_RCU || TREE_PREEMPT_RCU )
620 This option provides tracing for the TREE_RCU and
621 TREE_PREEMPT_RCU implementations, permitting Makefile to
622 trivially select kernel/rcutree_trace.c.
625 bool "Enable RCU priority boosting"
626 depends on RT_MUTEXES && PREEMPT_RCU
629 This option boosts the priority of preempted RCU readers that
630 block the current preemptible RCU grace period for too long.
631 This option also prevents heavy loads from blocking RCU
632 callback invocation for all flavors of RCU.
634 Say Y here if you are working with real-time apps or heavy loads
635 Say N here if you are unsure.
637 config RCU_BOOST_PRIO
638 int "Real-time priority to boost RCU readers to"
643 This option specifies the real-time priority to which long-term
644 preempted RCU readers are to be boosted. If you are working
645 with a real-time application that has one or more CPU-bound
646 threads running at a real-time priority level, you should set
647 RCU_BOOST_PRIO to a priority higher then the highest-priority
648 real-time CPU-bound thread. The default RCU_BOOST_PRIO value
649 of 1 is appropriate in the common case, which is real-time
650 applications that do not have any CPU-bound threads.
652 Some real-time applications might not have a single real-time
653 thread that saturates a given CPU, but instead might have
654 multiple real-time threads that, taken together, fully utilize
655 that CPU. In this case, you should set RCU_BOOST_PRIO to
656 a priority higher than the lowest-priority thread that is
657 conspiring to prevent the CPU from running any non-real-time
658 tasks. For example, if one thread at priority 10 and another
659 thread at priority 5 are between themselves fully consuming
660 the CPU time on a given CPU, then RCU_BOOST_PRIO should be
661 set to priority 6 or higher.
663 Specify the real-time priority, or take the default if unsure.
665 config RCU_BOOST_DELAY
666 int "Milliseconds to delay boosting after RCU grace-period start"
671 This option specifies the time to wait after the beginning of
672 a given grace period before priority-boosting preempted RCU
673 readers blocking that grace period. Note that any RCU reader
674 blocking an expedited RCU grace period is boosted immediately.
676 Accept the default if unsure.
679 bool "Offload RCU callback processing from boot-selected CPUs"
680 depends on TREE_RCU || TREE_PREEMPT_RCU
683 Use this option to reduce OS jitter for aggressive HPC or
684 real-time workloads. It can also be used to offload RCU
685 callback invocation to energy-efficient CPUs in battery-powered
686 asymmetric multiprocessors.
688 This option offloads callback invocation from the set of
689 CPUs specified at boot time by the rcu_nocbs parameter.
690 For each such CPU, a kthread ("rcuoN") will be created to
691 invoke callbacks, where the "N" is the CPU being offloaded.
692 Nothing prevents this kthread from running on the specified
693 CPUs, but (1) the kthreads may be preempted between each
694 callback, and (2) affinity or cgroups can be used to force
695 the kthreads to run on whatever set of CPUs is desired.
697 Say Y here if you want reduced OS jitter on selected CPUs.
698 Say N here if you are unsure.
700 endmenu # "RCU Subsystem"
703 tristate "Kernel .config support"
705 This option enables the complete Linux kernel ".config" file
706 contents to be saved in the kernel. It provides documentation
707 of which kernel options are used in a running kernel or in an
708 on-disk kernel. This information can be extracted from the kernel
709 image file with the script scripts/extract-ikconfig and used as
710 input to rebuild the current kernel or to build another kernel.
711 It can also be extracted from a running kernel by reading
712 /proc/config.gz if enabled (below).
715 bool "Enable access to .config through /proc/config.gz"
716 depends on IKCONFIG && PROC_FS
718 This option enables access to the kernel configuration file
719 through /proc/config.gz.
722 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
726 Select kernel log buffer size as a power of 2.
736 # Architectures with an unreliable sched_clock() should select this:
738 config HAVE_UNSTABLE_SCHED_CLOCK
742 # For architectures that want to enable the support for NUMA-affine scheduler
745 config ARCH_SUPPORTS_NUMA_BALANCING
748 # For architectures that (ab)use NUMA to represent different memory regions
749 # all cpu-local but of different latencies, such as SuperH.
751 config ARCH_WANT_NUMA_VARIABLE_LOCALITY
755 # For architectures that are willing to define _PAGE_NUMA as _PAGE_PROTNONE
756 config ARCH_WANTS_PROT_NUMA_PROT_NONE
759 config ARCH_USES_NUMA_PROT_NONE
762 depends on ARCH_WANTS_PROT_NUMA_PROT_NONE
763 depends on NUMA_BALANCING
765 config NUMA_BALANCING_DEFAULT_ENABLED
766 bool "Automatically enable NUMA aware memory/task placement"
768 depends on NUMA_BALANCING
770 If set, autonumic NUMA balancing will be enabled if running on a NUMA
773 config NUMA_BALANCING
774 bool "Memory placement aware NUMA scheduler"
775 depends on ARCH_SUPPORTS_NUMA_BALANCING
776 depends on !ARCH_WANT_NUMA_VARIABLE_LOCALITY
777 depends on SMP && NUMA && MIGRATION
779 This option adds support for automatic NUMA aware memory/task placement.
780 The mechanism is quite primitive and is based on migrating memory when
781 it is references to the node the task is running on.
783 This system will be inactive on UMA systems.
786 boolean "Control Group support"
789 This option adds support for grouping sets of processes together, for
790 use with process control subsystems such as Cpusets, CFS, memory
791 controls or device isolation.
793 - Documentation/scheduler/sched-design-CFS.txt (CFS)
794 - Documentation/cgroups/ (features for grouping, isolation
795 and resource control)
802 bool "Example debug cgroup subsystem"
805 This option enables a simple cgroup subsystem that
806 exports useful debugging information about the cgroups
811 config CGROUP_FREEZER
812 bool "Freezer cgroup subsystem"
814 Provides a way to freeze and unfreeze all tasks in a
818 bool "Device controller for cgroups"
820 Provides a cgroup implementing whitelists for devices which
821 a process in the cgroup can mknod or open.
824 bool "Cpuset support"
826 This option will let you create and manage CPUSETs which
827 allow dynamically partitioning a system into sets of CPUs and
828 Memory Nodes and assigning tasks to run only within those sets.
829 This is primarily useful on large SMP or NUMA systems.
833 config PROC_PID_CPUSET
834 bool "Include legacy /proc/<pid>/cpuset file"
838 config CGROUP_CPUACCT
839 bool "Simple CPU accounting cgroup subsystem"
841 Provides a simple Resource Controller for monitoring the
842 total CPU consumed by the tasks in a cgroup.
844 config RESOURCE_COUNTERS
845 bool "Resource counters"
847 This option enables controller independent resource accounting
848 infrastructure that works with cgroups.
851 bool "Memory Resource Controller for Control Groups"
852 depends on RESOURCE_COUNTERS
855 Provides a memory resource controller that manages both anonymous
856 memory and page cache. (See Documentation/cgroups/memory.txt)
858 Note that setting this option increases fixed memory overhead
859 associated with each page of memory in the system. By this,
860 20(40)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
861 usage tracking struct at boot. Total amount of this is printed out
864 Only enable when you're ok with these trade offs and really
865 sure you need the memory resource controller. Even when you enable
866 this, you can set "cgroup_disable=memory" at your boot option to
867 disable memory resource controller and you can avoid overheads.
868 (and lose benefits of memory resource controller)
870 This config option also selects MM_OWNER config option, which
871 could in turn add some fork/exit overhead.
874 bool "Memory Resource Controller Swap Extension"
875 depends on MEMCG && SWAP
877 Add swap management feature to memory resource controller. When you
878 enable this, you can limit mem+swap usage per cgroup. In other words,
879 when you disable this, memory resource controller has no cares to
880 usage of swap...a process can exhaust all of the swap. This extension
881 is useful when you want to avoid exhaustion swap but this itself
882 adds more overheads and consumes memory for remembering information.
883 Especially if you use 32bit system or small memory system, please
884 be careful about enabling this. When memory resource controller
885 is disabled by boot option, this will be automatically disabled and
886 there will be no overhead from this. Even when you set this config=y,
887 if boot option "swapaccount=0" is set, swap will not be accounted.
888 Now, memory usage of swap_cgroup is 2 bytes per entry. If swap page
889 size is 4096bytes, 512k per 1Gbytes of swap.
890 config MEMCG_SWAP_ENABLED
891 bool "Memory Resource Controller Swap Extension enabled by default"
892 depends on MEMCG_SWAP
895 Memory Resource Controller Swap Extension comes with its price in
896 a bigger memory consumption. General purpose distribution kernels
897 which want to enable the feature but keep it disabled by default
898 and let the user enable it by swapaccount boot command line
899 parameter should have this option unselected.
900 For those who want to have the feature enabled by default should
901 select this option (if, for some reason, they need to disable it
902 then swapaccount=0 does the trick).
904 bool "Memory Resource Controller Kernel Memory accounting (EXPERIMENTAL)"
905 depends on MEMCG && EXPERIMENTAL
906 depends on SLUB || SLAB
908 The Kernel Memory extension for Memory Resource Controller can limit
909 the amount of memory used by kernel objects in the system. Those are
910 fundamentally different from the entities handled by the standard
911 Memory Controller, which are page-based, and can be swapped. Users of
912 the kmem extension can use it to guarantee that no group of processes
913 will ever exhaust kernel resources alone.
915 config CGROUP_HUGETLB
916 bool "HugeTLB Resource Controller for Control Groups"
917 depends on RESOURCE_COUNTERS && HUGETLB_PAGE && EXPERIMENTAL
920 Provides a cgroup Resource Controller for HugeTLB pages.
921 When you enable this, you can put a per cgroup limit on HugeTLB usage.
922 The limit is enforced during page fault. Since HugeTLB doesn't
923 support page reclaim, enforcing the limit at page fault time implies
924 that, the application will get SIGBUS signal if it tries to access
925 HugeTLB pages beyond its limit. This requires the application to know
926 beforehand how much HugeTLB pages it would require for its use. The
927 control group is tracked in the third page lru pointer. This means
928 that we cannot use the controller with huge page less than 3 pages.
931 bool "Enable perf_event per-cpu per-container group (cgroup) monitoring"
932 depends on PERF_EVENTS && CGROUPS
934 This option extends the per-cpu mode to restrict monitoring to
935 threads which belong to the cgroup specified and run on the
940 menuconfig CGROUP_SCHED
941 bool "Group CPU scheduler"
944 This feature lets CPU scheduler recognize task groups and control CPU
945 bandwidth allocation to such task groups. It uses cgroups to group
949 config FAIR_GROUP_SCHED
950 bool "Group scheduling for SCHED_OTHER"
951 depends on CGROUP_SCHED
955 bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED"
956 depends on EXPERIMENTAL
957 depends on FAIR_GROUP_SCHED
960 This option allows users to define CPU bandwidth rates (limits) for
961 tasks running within the fair group scheduler. Groups with no limit
962 set are considered to be unconstrained and will run with no
964 See tip/Documentation/scheduler/sched-bwc.txt for more information.
966 config RT_GROUP_SCHED
967 bool "Group scheduling for SCHED_RR/FIFO"
968 depends on EXPERIMENTAL
969 depends on CGROUP_SCHED
972 This feature lets you explicitly allocate real CPU bandwidth
973 to task groups. If enabled, it will also make it impossible to
974 schedule realtime tasks for non-root users until you allocate
975 realtime bandwidth for them.
976 See Documentation/scheduler/sched-rt-group.txt for more information.
981 bool "Block IO controller"
985 Generic block IO controller cgroup interface. This is the common
986 cgroup interface which should be used by various IO controlling
989 Currently, CFQ IO scheduler uses it to recognize task groups and
990 control disk bandwidth allocation (proportional time slice allocation)
991 to such task groups. It is also used by bio throttling logic in
992 block layer to implement upper limit in IO rates on a device.
994 This option only enables generic Block IO controller infrastructure.
995 One needs to also enable actual IO controlling logic/policy. For
996 enabling proportional weight division of disk bandwidth in CFQ, set
997 CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
998 CONFIG_BLK_DEV_THROTTLING=y.
1000 See Documentation/cgroups/blkio-controller.txt for more information.
1002 config DEBUG_BLK_CGROUP
1003 bool "Enable Block IO controller debugging"
1004 depends on BLK_CGROUP
1007 Enable some debugging help. Currently it exports additional stat
1008 files in a cgroup which can be useful for debugging.
1012 config CHECKPOINT_RESTORE
1013 bool "Checkpoint/restore support" if EXPERT
1016 Enables additional kernel features in a sake of checkpoint/restore.
1017 In particular it adds auxiliary prctl codes to setup process text,
1018 data and heap segment sizes, and a few additional /proc filesystem
1021 If unsure, say N here.
1023 menuconfig NAMESPACES
1024 bool "Namespaces support" if EXPERT
1027 Provides the way to make tasks work with different objects using
1028 the same id. For example same IPC id may refer to different objects
1029 or same user id or pid may refer to different tasks when used in
1030 different namespaces.
1035 bool "UTS namespace"
1038 In this namespace tasks see different info provided with the
1042 bool "IPC namespace"
1043 depends on (SYSVIPC || POSIX_MQUEUE)
1046 In this namespace tasks work with IPC ids which correspond to
1047 different IPC objects in different namespaces.
1050 bool "User namespace (EXPERIMENTAL)"
1051 depends on EXPERIMENTAL
1052 depends on UIDGID_CONVERTED
1053 select UIDGID_STRICT_TYPE_CHECKS
1057 This allows containers, i.e. vservers, to use user namespaces
1058 to provide different user info for different servers.
1062 bool "PID Namespaces"
1065 Support process id namespaces. This allows having multiple
1066 processes with the same pid as long as they are in different
1067 pid namespaces. This is a building block of containers.
1070 bool "Network namespace"
1074 Allow user space to create what appear to be multiple instances
1075 of the network stack.
1079 config UIDGID_CONVERTED
1080 # True if all of the selected software conmponents are known
1081 # to have uid_t and gid_t converted to kuid_t and kgid_t
1082 # where appropriate and are otherwise safe to use with
1083 # the user namespace.
1088 depends on NET_9P = n
1091 depends on 9P_FS = n
1092 depends on AFS_FS = n
1093 depends on CEPH_FS = n
1095 depends on CODA_FS = n
1096 depends on GFS2_FS = n
1097 depends on NCP_FS = n
1099 depends on NFS_FS = n
1100 depends on OCFS2_FS = n
1101 depends on XFS_FS = n
1103 config UIDGID_STRICT_TYPE_CHECKS
1104 bool "Require conversions between uid/gids and their internal representation"
1105 depends on UIDGID_CONVERTED
1108 While the nececessary conversions are being added to all subsystems this option allows
1109 the code to continue to build for unconverted subsystems.
1111 Say Y here if you want the strict type checking enabled
1113 config SCHED_AUTOGROUP
1114 bool "Automatic process group scheduling"
1118 select FAIR_GROUP_SCHED
1120 This option optimizes the scheduler for common desktop workloads by
1121 automatically creating and populating task groups. This separation
1122 of workloads isolates aggressive CPU burners (like build jobs) from
1123 desktop applications. Task group autogeneration is currently based
1129 config SYSFS_DEPRECATED
1130 bool "Enable deprecated sysfs features to support old userspace tools"
1134 This option adds code that switches the layout of the "block" class
1135 devices, to not show up in /sys/class/block/, but only in
1138 This switch is only active when the sysfs.deprecated=1 boot option is
1139 passed or the SYSFS_DEPRECATED_V2 option is set.
1141 This option allows new kernels to run on old distributions and tools,
1142 which might get confused by /sys/class/block/. Since 2007/2008 all
1143 major distributions and tools handle this just fine.
1145 Recent distributions and userspace tools after 2009/2010 depend on
1146 the existence of /sys/class/block/, and will not work with this
1149 Only if you are using a new kernel on an old distribution, you might
1152 config SYSFS_DEPRECATED_V2
1153 bool "Enable deprecated sysfs features by default"
1156 depends on SYSFS_DEPRECATED
1158 Enable deprecated sysfs by default.
1160 See the CONFIG_SYSFS_DEPRECATED option for more details about this
1163 Only if you are using a new kernel on an old distribution, you might
1164 need to say Y here. Even then, odds are you would not need it
1165 enabled, you can always pass the boot option if absolutely necessary.
1168 bool "Kernel->user space relay support (formerly relayfs)"
1170 This option enables support for relay interface support in
1171 certain file systems (such as debugfs).
1172 It is designed to provide an efficient mechanism for tools and
1173 facilities to relay large amounts of data from kernel space to
1178 config BLK_DEV_INITRD
1179 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
1180 depends on BROKEN || !FRV
1182 The initial RAM filesystem is a ramfs which is loaded by the
1183 boot loader (loadlin or lilo) and that is mounted as root
1184 before the normal boot procedure. It is typically used to
1185 load modules needed to mount the "real" root file system,
1186 etc. See <file:Documentation/initrd.txt> for details.
1188 If RAM disk support (BLK_DEV_RAM) is also included, this
1189 also enables initial RAM disk (initrd) support and adds
1190 15 Kbytes (more on some other architectures) to the kernel size.
1196 source "usr/Kconfig"
1200 config CC_OPTIMIZE_FOR_SIZE
1201 bool "Optimize for size"
1203 Enabling this option will pass "-Os" instead of "-O2" to gcc
1204 resulting in a smaller kernel.
1215 bool "Configure standard kernel features (expert users)"
1216 # Unhide debug options, to make the on-by-default options visible
1219 This option allows certain base kernel options and settings
1220 to be disabled or tweaked. This is for specialized
1221 environments which can tolerate a "non-standard" kernel.
1222 Only use this if you really know what you are doing.
1228 bool "Enable 16-bit UID system calls" if EXPERT
1229 depends on HAVE_UID16
1232 This enables the legacy 16-bit UID syscall wrappers.
1234 config SYSCTL_SYSCALL
1235 bool "Sysctl syscall support" if EXPERT
1236 depends on PROC_SYSCTL
1240 sys_sysctl uses binary paths that have been found challenging
1241 to properly maintain and use. The interface in /proc/sys
1242 using paths with ascii names is now the primary path to this
1245 Almost nothing using the binary sysctl interface so if you are
1246 trying to save some space it is probably safe to disable this,
1247 making your kernel marginally smaller.
1249 If unsure say N here.
1251 config SYSCTL_EXCEPTION_TRACE
1254 Enable support for /proc/sys/debug/exception-trace.
1257 bool "Load all symbols for debugging/ksymoops" if EXPERT
1260 Say Y here to let the kernel print out symbolic crash information and
1261 symbolic stack backtraces. This increases the size of the kernel
1262 somewhat, as all symbols have to be loaded into the kernel image.
1265 bool "Include all symbols in kallsyms"
1266 depends on DEBUG_KERNEL && KALLSYMS
1268 Normally kallsyms only contains the symbols of functions for nicer
1269 OOPS messages and backtraces (i.e., symbols from the text and inittext
1270 sections). This is sufficient for most cases. And only in very rare
1271 cases (e.g., when a debugger is used) all symbols are required (e.g.,
1272 names of variables from the data sections, etc).
1274 This option makes sure that all symbols are loaded into the kernel
1275 image (i.e., symbols from all sections) in cost of increased kernel
1276 size (depending on the kernel configuration, it may be 300KiB or
1277 something like this).
1279 Say N unless you really need all symbols.
1286 bool "Enable support for printk" if EXPERT
1288 This option enables normal printk support. Removing it
1289 eliminates most of the message strings from the kernel image
1290 and makes the kernel more or less silent. As this makes it
1291 very difficult to diagnose system problems, saying N here is
1292 strongly discouraged.
1295 bool "BUG() support" if EXPERT
1298 Disabling this option eliminates support for BUG and WARN, reducing
1299 the size of your kernel image and potentially quietly ignoring
1300 numerous fatal conditions. You should only consider disabling this
1301 option for embedded systems with no facilities for reporting errors.
1307 bool "Enable ELF core dumps" if EXPERT
1309 Enable support for generating core dumps. Disabling saves about 4k.
1312 config PCSPKR_PLATFORM
1313 bool "Enable PC-Speaker support" if EXPERT
1314 depends on HAVE_PCSPKR_PLATFORM
1318 This option allows to disable the internal PC-Speaker
1319 support, saving some memory.
1321 config HAVE_PCSPKR_PLATFORM
1326 bool "Enable full-sized data structures for core" if EXPERT
1328 Disabling this option reduces the size of miscellaneous core
1329 kernel data structures. This saves memory on small machines,
1330 but may reduce performance.
1333 bool "Enable futex support" if EXPERT
1337 Disabling this option will cause the kernel to be built without
1338 support for "fast userspace mutexes". The resulting kernel may not
1339 run glibc-based applications correctly.
1342 bool "Enable eventpoll support" if EXPERT
1346 Disabling this option will cause the kernel to be built without
1347 support for epoll family of system calls.
1350 bool "Enable signalfd() system call" if EXPERT
1354 Enable the signalfd() system call that allows to receive signals
1355 on a file descriptor.
1360 bool "Enable timerfd() system call" if EXPERT
1364 Enable the timerfd() system call that allows to receive timer
1365 events on a file descriptor.
1370 bool "Enable eventfd() system call" if EXPERT
1374 Enable the eventfd() system call that allows to receive both
1375 kernel notification (ie. KAIO) or userspace notifications.
1380 bool "Use full shmem filesystem" if EXPERT
1384 The shmem is an internal filesystem used to manage shared memory.
1385 It is backed by swap and manages resource limits. It is also exported
1386 to userspace as tmpfs if TMPFS is enabled. Disabling this
1387 option replaces shmem and tmpfs with the much simpler ramfs code,
1388 which may be appropriate on small systems without swap.
1391 bool "Enable AIO support" if EXPERT
1394 This option enables POSIX asynchronous I/O which may by used
1395 by some high performance threaded applications. Disabling
1396 this option saves about 7k.
1399 bool "Embedded system"
1402 This option should be enabled if compiling the kernel for
1403 an embedded system so certain expert options are available
1406 config HAVE_PERF_EVENTS
1409 See tools/perf/design.txt for details.
1411 config PERF_USE_VMALLOC
1414 See tools/perf/design.txt for details
1416 menu "Kernel Performance Events And Counters"
1419 bool "Kernel performance events and counters"
1420 default y if PROFILING
1421 depends on HAVE_PERF_EVENTS
1425 Enable kernel support for various performance events provided
1426 by software and hardware.
1428 Software events are supported either built-in or via the
1429 use of generic tracepoints.
1431 Most modern CPUs support performance events via performance
1432 counter registers. These registers count the number of certain
1433 types of hw events: such as instructions executed, cachemisses
1434 suffered, or branches mis-predicted - without slowing down the
1435 kernel or applications. These registers can also trigger interrupts
1436 when a threshold number of events have passed - and can thus be
1437 used to profile the code that runs on that CPU.
1439 The Linux Performance Event subsystem provides an abstraction of
1440 these software and hardware event capabilities, available via a
1441 system call and used by the "perf" utility in tools/perf/. It
1442 provides per task and per CPU counters, and it provides event
1443 capabilities on top of those.
1447 config DEBUG_PERF_USE_VMALLOC
1449 bool "Debug: use vmalloc to back perf mmap() buffers"
1450 depends on PERF_EVENTS && DEBUG_KERNEL
1451 select PERF_USE_VMALLOC
1453 Use vmalloc memory to back perf mmap() buffers.
1455 Mostly useful for debugging the vmalloc code on platforms
1456 that don't require it.
1462 config VM_EVENT_COUNTERS
1464 bool "Enable VM event counters for /proc/vmstat" if EXPERT
1466 VM event counters are needed for event counts to be shown.
1467 This option allows the disabling of the VM event counters
1468 on EXPERT systems. /proc/vmstat will only show page counts
1469 if VM event counters are disabled.
1473 bool "Enable PCI quirk workarounds" if EXPERT
1476 This enables workarounds for various PCI chipset
1477 bugs/quirks. Disable this only if your target machine is
1478 unaffected by PCI quirks.
1482 bool "Enable SLUB debugging support" if EXPERT
1483 depends on SLUB && SYSFS
1485 SLUB has extensive debug support features. Disabling these can
1486 result in significant savings in code size. This also disables
1487 SLUB sysfs support. /sys/slab will not exist and there will be
1488 no support for cache validation etc.
1491 bool "Disable heap randomization"
1494 Randomizing heap placement makes heap exploits harder, but it
1495 also breaks ancient binaries (including anything libc5 based).
1496 This option changes the bootup default to heap randomization
1497 disabled, and can be overridden at runtime by setting
1498 /proc/sys/kernel/randomize_va_space to 2.
1500 On non-ancient distros (post-2000 ones) N is usually a safe choice.
1503 prompt "Choose SLAB allocator"
1506 This option allows to select a slab allocator.
1511 The regular slab allocator that is established and known to work
1512 well in all environments. It organizes cache hot objects in
1513 per cpu and per node queues.
1516 bool "SLUB (Unqueued Allocator)"
1518 SLUB is a slab allocator that minimizes cache line usage
1519 instead of managing queues of cached objects (SLAB approach).
1520 Per cpu caching is realized using slabs of objects instead
1521 of queues of objects. SLUB can use memory efficiently
1522 and has enhanced diagnostics. SLUB is the default choice for
1527 bool "SLOB (Simple Allocator)"
1529 SLOB replaces the stock allocator with a drastically simpler
1530 allocator. SLOB is generally more space efficient but
1531 does not perform as well on large systems.
1535 config MMAP_ALLOW_UNINITIALIZED
1536 bool "Allow mmapped anonymous memory to be uninitialized"
1537 depends on EXPERT && !MMU
1540 Normally, and according to the Linux spec, anonymous memory obtained
1541 from mmap() has it's contents cleared before it is passed to
1542 userspace. Enabling this config option allows you to request that
1543 mmap() skip that if it is given an MAP_UNINITIALIZED flag, thus
1544 providing a huge performance boost. If this option is not enabled,
1545 then the flag will be ignored.
1547 This is taken advantage of by uClibc's malloc(), and also by
1548 ELF-FDPIC binfmt's brk and stack allocator.
1550 Because of the obvious security issues, this option should only be
1551 enabled on embedded devices where you control what is run in
1552 userspace. Since that isn't generally a problem on no-MMU systems,
1553 it is normally safe to say Y here.
1555 See Documentation/nommu-mmap.txt for more information.
1558 bool "Profiling support"
1560 Say Y here to enable the extended profiling support mechanisms used
1561 by profilers such as OProfile.
1564 # Place an empty function call at each tracepoint site. Can be
1565 # dynamically changed for a probe function.
1570 source "arch/Kconfig"
1572 endmenu # General setup
1574 config HAVE_GENERIC_DMA_COHERENT
1581 depends on SLAB || SLUB_DEBUG
1589 default 0 if BASE_FULL
1590 default 1 if !BASE_FULL
1593 bool "Enable loadable module support"
1595 Kernel modules are small pieces of compiled code which can
1596 be inserted in the running kernel, rather than being
1597 permanently built into the kernel. You use the "modprobe"
1598 tool to add (and sometimes remove) them. If you say Y here,
1599 many parts of the kernel can be built as modules (by
1600 answering M instead of Y where indicated): this is most
1601 useful for infrequently used options which are not required
1602 for booting. For more information, see the man pages for
1603 modprobe, lsmod, modinfo, insmod and rmmod.
1605 If you say Y here, you will need to run "make
1606 modules_install" to put the modules under /lib/modules/
1607 where modprobe can find them (you may need to be root to do
1614 config MODULE_FORCE_LOAD
1615 bool "Forced module loading"
1618 Allow loading of modules without version information (ie. modprobe
1619 --force). Forced module loading sets the 'F' (forced) taint flag and
1620 is usually a really bad idea.
1622 config MODULE_UNLOAD
1623 bool "Module unloading"
1625 Without this option you will not be able to unload any
1626 modules (note that some modules may not be unloadable
1627 anyway), which makes your kernel smaller, faster
1628 and simpler. If unsure, say Y.
1630 config MODULE_FORCE_UNLOAD
1631 bool "Forced module unloading"
1632 depends on MODULE_UNLOAD && EXPERIMENTAL
1634 This option allows you to force a module to unload, even if the
1635 kernel believes it is unsafe: the kernel will remove the module
1636 without waiting for anyone to stop using it (using the -f option to
1637 rmmod). This is mainly for kernel developers and desperate users.
1641 bool "Module versioning support"
1643 Usually, you have to use modules compiled with your kernel.
1644 Saying Y here makes it sometimes possible to use modules
1645 compiled for different kernels, by adding enough information
1646 to the modules to (hopefully) spot any changes which would
1647 make them incompatible with the kernel you are running. If
1650 config MODULE_SRCVERSION_ALL
1651 bool "Source checksum for all modules"
1653 Modules which contain a MODULE_VERSION get an extra "srcversion"
1654 field inserted into their modinfo section, which contains a
1655 sum of the source files which made it. This helps maintainers
1656 see exactly which source was used to build a module (since
1657 others sometimes change the module source without updating
1658 the version). With this option, such a "srcversion" field
1659 will be created for all modules. If unsure, say N.
1662 bool "Module signature verification"
1666 select ASYMMETRIC_KEY_TYPE
1667 select ASYMMETRIC_PUBLIC_KEY_SUBTYPE
1668 select PUBLIC_KEY_ALGO_RSA
1671 select X509_CERTIFICATE_PARSER
1673 Check modules for valid signatures upon load: the signature
1674 is simply appended to the module. For more information see
1675 Documentation/module-signing.txt.
1677 !!!WARNING!!! If you enable this option, you MUST make sure that the
1678 module DOES NOT get stripped after being signed. This includes the
1679 debuginfo strip done by some packagers (such as rpmbuild) and
1680 inclusion into an initramfs that wants the module size reduced.
1682 config MODULE_SIG_FORCE
1683 bool "Require modules to be validly signed"
1684 depends on MODULE_SIG
1686 Reject unsigned modules or signed modules for which we don't have a
1687 key. Without this, such modules will simply taint the kernel.
1690 prompt "Which hash algorithm should modules be signed with?"
1691 depends on MODULE_SIG
1693 This determines which sort of hashing algorithm will be used during
1694 signature generation. This algorithm _must_ be built into the kernel
1695 directly so that signature verification can take place. It is not
1696 possible to load a signed module containing the algorithm to check
1697 the signature on that module.
1699 config MODULE_SIG_SHA1
1700 bool "Sign modules with SHA-1"
1703 config MODULE_SIG_SHA224
1704 bool "Sign modules with SHA-224"
1705 select CRYPTO_SHA256
1707 config MODULE_SIG_SHA256
1708 bool "Sign modules with SHA-256"
1709 select CRYPTO_SHA256
1711 config MODULE_SIG_SHA384
1712 bool "Sign modules with SHA-384"
1713 select CRYPTO_SHA512
1715 config MODULE_SIG_SHA512
1716 bool "Sign modules with SHA-512"
1717 select CRYPTO_SHA512
1723 config INIT_ALL_POSSIBLE
1726 Back when each arch used to define their own cpu_online_mask and
1727 cpu_possible_mask, some of them chose to initialize cpu_possible_mask
1728 with all 1s, and others with all 0s. When they were centralised,
1729 it was better to provide this option than to break all the archs
1730 and have several arch maintainers pursuing me down dark alleys.
1735 depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
1737 Need stop_machine() primitive.
1739 source "block/Kconfig"
1741 config PREEMPT_NOTIFIERS
1748 # Can be selected by architectures with broken toolchains
1749 # that get confused by correct const<->read_only section
1751 config BROKEN_RODATA
1757 Build a simple ASN.1 grammar compiler that produces a bytecode output
1758 that can be interpreted by the ASN.1 stream decoder and used to
1759 inform it as to what tags are to be expected in a stream and what
1760 functions to call on what tags.
1762 source "kernel/Kconfig.locks"
projects / karo-tx-linux.git / blob