1 # Copyright (C) 2006-2014 OpenWrt.org
3 # This is free software, licensed under the GNU General Public License v2.
4 # See /LICENSE for more information.
8 bool "Enable support for printk"
11 config KERNEL_CRASHLOG
13 depends on !(arm || powerpc || sparc || TARGET_uml)
17 bool "Support for paging of anonymous memory (swap)"
20 config KERNEL_DEBUG_FS
21 bool "Compile the kernel with debug filesystem enabled"
24 debugfs is a virtual file system that kernel developers use to put
25 debugging files into. Enable this option to be able to read and
26 write to these files. Many common debugging facilities, such as
27 ftrace, require the existence of debugfs.
29 config KERNEL_PERF_EVENTS
33 config KERNEL_PROFILING
34 bool "Compile the kernel with profiling enabled"
36 select KERNEL_PERF_EVENTS
38 Enable the extended profiling support mechanisms used by profilers such
41 config KERNEL_KALLSYMS
42 bool "Compile the kernel with symbol table information"
45 This will give you more information in stack traces from kernel oopses.
48 bool "Compile the kernel with tracing support"
51 config KERNEL_FTRACE_SYSCALLS
52 bool "Trace system calls"
53 depends on KERNEL_FTRACE
56 config KERNEL_ENABLE_DEFAULT_TRACERS
57 bool "Trace process context switches and events"
58 depends on KERNEL_FTRACE
61 config KERNEL_DEBUG_KERNEL
65 config KERNEL_DEBUG_INFO
66 bool "Compile the kernel with debug information"
68 select KERNEL_DEBUG_KERNEL
70 This will compile your kernel and modules with debug information.
72 config KERNEL_DEBUG_LL_UART_NONE
77 config KERNEL_DEBUG_LL
81 select KERNEL_DEBUG_LL_UART_NONE
83 ARM low level debugging.
85 config KERNEL_DYNAMIC_DEBUG
86 bool "Compile the kernel with dynamic printk"
87 select KERNEL_DEBUG_FS
90 Compiles debug level messages into the kernel, which would not
91 otherwise be available at runtime. These messages can then be
92 enabled/disabled based on various levels of scope - per source file,
93 function, module, format string, and line number. This mechanism
94 implicitly compiles in all pr_debug() and dev_dbg() calls, which
95 enlarges the kernel text size by about 2%.
97 config KERNEL_EARLY_PRINTK
98 bool "Compile the kernel with early printk"
101 select KERNEL_DEBUG_KERNEL
102 select KERNEL_DEBUG_LL if arm
104 Compile the kernel with early printk support. This is only useful for
105 debugging purposes to send messages over the serial console in early boot.
106 Enable this to debug early boot problems.
109 bool "Compile the kernel with asynchronous IO support"
112 config KERNEL_DIRECT_IO
113 bool "Compile the kernel with direct IO support"
116 config KERNEL_MAGIC_SYSRQ
117 bool "Compile the kernel with SysRq support"
120 config KERNEL_COREDUMP
123 config KERNEL_ELF_CORE
124 bool "Enable process core dump support"
125 select KERNEL_COREDUMP
128 config KERNEL_PROVE_LOCKING
129 bool "Enable kernel lock checking"
130 select KERNEL_DEBUG_KERNEL
133 config KERNEL_PRINTK_TIME
134 bool "Enable printk timestamps"
137 config KERNEL_SLUB_DEBUG
140 config KERNEL_SLUB_DEBUG_ON
143 config KERNEL_SLABINFO
144 select KERNEL_SLUB_DEBUG
145 select KERNEL_SLUB_DEBUG_ON
146 bool "Enable /proc slab debug info"
148 config KERNEL_PROC_PAGE_MONITOR
149 bool "Enable /proc page monitoring"
155 bool "Enable kexec support"
158 bool "Enable rfkill support"
159 default RFKILL_SUPPORT
162 bool "Enable sparse check during kernel build"
166 # CGROUP support symbols
169 config KERNEL_CGROUPS
170 bool "Enable kernel cgroups"
175 config KERNEL_CGROUP_DEBUG
176 bool "Example debug cgroup subsystem"
179 This option enables a simple cgroup subsystem that
180 exports useful debugging information about the cgroups
183 config KERNEL_FREEZER
185 default y if KERNEL_CGROUP_FREEZER
187 config KERNEL_CGROUP_FREEZER
188 bool "Freezer cgroup subsystem"
191 Provides a way to freeze and unfreeze all tasks in a
194 config KERNEL_CGROUP_DEVICE
195 bool "Device controller for cgroups"
198 Provides a cgroup implementing whitelists for devices which
199 a process in the cgroup can mknod or open.
201 config KERNEL_CPUSETS
202 bool "Cpuset support"
205 This option will let you create and manage CPUSETs which
206 allow dynamically partitioning a system into sets of CPUs and
207 Memory Nodes and assigning tasks to run only within those sets.
208 This is primarily useful on large SMP or NUMA systems.
210 config KERNEL_PROC_PID_CPUSET
211 bool "Include legacy /proc/<pid>/cpuset file"
213 depends on KERNEL_CPUSETS
215 config KERNEL_CGROUP_CPUACCT
216 bool "Simple CPU accounting cgroup subsystem"
219 Provides a simple Resource Controller for monitoring the
220 total CPU consumed by the tasks in a cgroup.
222 config KERNEL_RESOURCE_COUNTERS
223 bool "Resource counters"
226 This option enables controller independent resource accounting
227 infrastructure that works with cgroups.
229 config KERNEL_MM_OWNER
231 default y if KERNEL_MEMCG
234 bool "Memory Resource Controller for Control Groups"
236 depends on KERNEL_RESOURCE_COUNTERS
238 Provides a memory resource controller that manages both anonymous
239 memory and page cache. (See Documentation/cgroups/memory.txt)
241 Note that setting this option increases fixed memory overhead
242 associated with each page of memory in the system. By this,
243 20(40)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
244 usage tracking struct at boot. Total amount of this is printed out
247 Only enable when you're ok with these tradeoffs and really
248 sure you need the memory resource controller. Even when you enable
249 this, you can set "cgroup_disable=memory" at your boot option to
250 disable memory resource controller and you can avoid overheads
251 (but lose benefits of memory resource controller).
253 This config option also selects MM_OWNER config option, which
254 could in turn add some fork/exit overhead.
256 config KERNEL_MEMCG_SWAP
257 bool "Memory Resource Controller Swap Extension"
259 depends on KERNEL_MEMCG
261 Add swap management feature to memory resource controller. When you
262 enable this, you can limit mem+swap usage per cgroup. In other words,
263 when you disable this, memory resource controller has no cares to
264 usage of swap...a process can exhaust all of the swap. This extension
265 is useful when you want to avoid exhaustion swap but this itself
266 adds more overheads and consumes memory for remembering information.
267 Especially if you use 32bit system or small memory system, please
268 be careful about enabling this. When memory resource controller
269 is disabled by boot option, this will be automatically disabled and
270 there will be no overhead from this. Even when you set this config=y,
271 if boot option "swapaccount=0" is set, swap will not be accounted.
272 Now, memory usage of swap_cgroup is 2 bytes per entry. If swap page
273 size is 4096bytes, 512k per 1Gbytes of swap.
275 config KERNEL_MEMCG_SWAP_ENABLED
276 bool "Memory Resource Controller Swap Extension enabled by default"
278 depends on KERNEL_MEMCG_SWAP
280 Memory Resource Controller Swap Extension comes with its price in
281 a bigger memory consumption. General purpose distribution kernels
282 which want to enable the feature but keep it disabled by default
283 and let the user enable it by swapaccount boot command line
284 parameter should have this option unselected.
286 Those who want to have the feature enabled by default should
287 select this option (if, for some reason, they need to disable it,
288 then swapaccount=0 does the trick).
291 config KERNEL_MEMCG_KMEM
292 bool "Memory Resource Controller Kernel Memory accounting (EXPERIMENTAL)"
294 depends on KERNEL_MEMCG
296 The Kernel Memory extension for Memory Resource Controller can limit
297 the amount of memory used by kernel objects in the system. Those are
298 fundamentally different from the entities handled by the standard
299 Memory Controller, which are page-based, and can be swapped. Users of
300 the kmem extension can use it to guarantee that no group of processes
301 will ever exhaust kernel resources alone.
303 config KERNEL_CGROUP_PERF
304 bool "Enable perf_event per-cpu per-container group (cgroup) monitoring"
305 select KERNEL_PERF_EVENTS
308 This option extends the per-cpu mode to restrict monitoring to
309 threads which belong to the cgroup specified and run on the
312 menuconfig KERNEL_CGROUP_SCHED
313 bool "Group CPU scheduler"
316 This feature lets CPU scheduler recognize task groups and control CPU
317 bandwidth allocation to such task groups. It uses cgroups to group
320 if KERNEL_CGROUP_SCHED
322 config KERNEL_FAIR_GROUP_SCHED
323 bool "Group scheduling for SCHED_OTHER"
326 config KERNEL_CFS_BANDWIDTH
327 bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED"
329 depends on KERNEL_FAIR_GROUP_SCHED
331 This option allows users to define CPU bandwidth rates (limits) for
332 tasks running within the fair group scheduler. Groups with no limit
333 set are considered to be unconstrained and will run with no
335 See tip/Documentation/scheduler/sched-bwc.txt for more information.
337 config KERNEL_RT_GROUP_SCHED
338 bool "Group scheduling for SCHED_RR/FIFO"
341 This feature lets you explicitly allocate real CPU bandwidth
342 to task groups. If enabled, it will also make it impossible to
343 schedule realtime tasks for non-root users until you allocate
344 realtime bandwidth for them.
348 config KERNEL_BLK_CGROUP
349 bool "Block IO controller"
352 Generic block IO controller cgroup interface. This is the common
353 cgroup interface which should be used by various IO controlling
356 Currently, CFQ IO scheduler uses it to recognize task groups and
357 control disk bandwidth allocation (proportional time slice allocation)
358 to such task groups. It is also used by bio throttling logic in
359 block layer to implement upper limit in IO rates on a device.
361 This option only enables generic Block IO controller infrastructure.
362 One needs to also enable actual IO controlling logic/policy. For
363 enabling proportional weight division of disk bandwidth in CFQ, set
364 CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
365 CONFIG_BLK_DEV_THROTTLING=y.
367 config KERNEL_DEBUG_BLK_CGROUP
368 bool "Enable Block IO controller debugging"
370 depends on KERNEL_BLK_CGROUP
372 Enable some debugging help. Currently it exports additional stat
373 files in a cgroup which can be useful for debugging.
375 config KERNEL_NET_CLS_CGROUP
376 bool "Control Group Classifier"
379 config KERNEL_NETPRIO_CGROUP
380 bool "Network priority cgroup"
386 # Namespace support symbols
389 config KERNEL_NAMESPACES
390 bool "Enable kernel namespaces"
399 In this namespace, tasks see different info provided
400 with the uname() system call.
406 In this namespace, tasks work with IPC ids which correspond to
407 different IPC objects in different namespaces.
409 config KERNEL_USER_NS
410 bool "User namespace (EXPERIMENTAL)"
413 This allows containers, i.e. vservers, to use user namespaces
414 to provide different user info for different servers.
417 bool "PID Namespaces"
420 Support process id namespaces. This allows having multiple
421 processes with the same pid as long as they are in different
422 pid namespaces. This is a building block of containers.
425 bool "Network namespace"
428 Allow user space to create what appear to be multiple instances
429 of the network stack.
434 # LXC related symbols
437 config KERNEL_LXC_MISC
438 bool "Enable miscellaneous LXC related options"
443 config KERNEL_DEVPTS_MULTIPLE_INSTANCES
444 bool "Support multiple instances of devpts"
447 Enable support for multiple instances of devpts filesystem.
448 If you want to have isolated PTY namespaces (eg: in containers),
449 say Y here. Otherwise, say N. If enabled, each mount of devpts
450 filesystem with the '-o newinstance' option will create an
451 independent PTY namespace.
453 config KERNEL_POSIX_MQUEUE
454 bool "POSIX Message Queues"
457 POSIX variant of message queues is a part of IPC. In POSIX message
458 queues every message has a priority which decides about succession
459 of receiving it by a process. If you want to compile and run
460 programs written e.g. for Solaris with use of its POSIX message
461 queues (functions mq_*) say Y here.
463 POSIX message queues are visible as a filesystem called 'mqueue'
464 and can be mounted somewhere if you want to do filesystem
465 operations on message queues.