Kconfig 64.4 KB
Newer Older
Roman Zippel's avatar
Roman Zippel committed
1
2
3
4
5
6
7
8
config ARCH
	string
	option env="ARCH"

config KERNELVERSION
	string
	option env="KERNELVERSION"

9
10
config DEFCONFIG_LIST
	string
11
	depends on !UML
12
13
14
15
	option defconfig_list
	default "/lib/modules/$UNAME_RELEASE/.config"
	default "/etc/kernel-config"
	default "/boot/config-$UNAME_RELEASE"
16
	default "$ARCH_DEFCONFIG"
17
18
	default "arch/$ARCH/defconfig"

19
20
21
22
config CONSTRUCTORS
	bool
	depends on !UML

23
24
25
config IRQ_WORK
	bool

26
27
28
config BUILDTIME_EXTABLE_SORT
	bool

29
menu "General setup"
Linus Torvalds's avatar
Linus Torvalds committed
30
31
32
33
34
35
36
37
38
39
40

config BROKEN
	bool

config BROKEN_ON_SMP
	bool
	depends on BROKEN || !SMP
	default y

config INIT_ENV_ARG_LIMIT
	int
41
42
	default 32 if !UML
	default 128 if UML
Linus Torvalds's avatar
Linus Torvalds committed
43
	help
44
45
	  Maximum of each of the number of arguments and environment
	  variables passed to init from the kernel command line.
Linus Torvalds's avatar
Linus Torvalds committed
46
47


Roland McGrath's avatar
Roland McGrath committed
48
49
50
51
52
53
54
55
config CROSS_COMPILE
	string "Cross-compiler tool prefix"
	help
	  Same as running 'make CROSS_COMPILE=prefix-' but stored for
	  default make runs in this kernel build directory.  You don't
	  need to set this unless you want the configured kernel build
	  directory to select the cross-compiler automatically.

56
57
58
59
60
61
62
63
64
65
66
67
68
69
config COMPILE_TEST
	bool "Compile also drivers which will not load"
	default n
	help
	  Some drivers can be compiled on a different platform than they are
	  intended to be run on. Despite they cannot be loaded there (or even
	  when they load they cannot be used due to missing HW support),
	  developers still, opposing to distributors, might want to build such
	  drivers to compile-test them.

	  If you are a developer and want to build everything available, say Y
	  here. If you are a user/distributor, say N here to exclude useless
	  drivers to be distributed.

Linus Torvalds's avatar
Linus Torvalds committed
70
71
72
73
74
75
76
77
78
79
config LOCALVERSION
	string "Local version - append to kernel release"
	help
	  Append an extra string to the end of your kernel version.
	  This will show up when you type uname, for example.
	  The string you set here will be appended after the contents of
	  any files with a filename matching localversion* in your
	  object and source tree, in that order.  Your total string can
	  be a maximum of 64 characters.

80
81
82
83
84
config LOCALVERSION_AUTO
	bool "Automatically append version information to the version string"
	default y
	help
	  This will try to automatically determine if the current tree is a
85
86
	  release tree by looking for git tags that belong to the current
	  top of tree revision.
87
88

	  A string of the format -gxxxxxxxx will be added to the localversion
89
	  if a git-based tree is found.  The string generated by this will be
90
	  appended after any matching localversion* files, and after the value
91
	  set in CONFIG_LOCALVERSION.
92

93
94
95
96
97
98
	  (The actual string used here is the first eight characters produced
	  by running the command:

	    $ git rev-parse --verify HEAD

	  which is done within the script "scripts/setlocalversion".)
99

100
101
102
103
104
105
106
107
108
config HAVE_KERNEL_GZIP
	bool

config HAVE_KERNEL_BZIP2
	bool

config HAVE_KERNEL_LZMA
	bool

109
110
111
config HAVE_KERNEL_XZ
	bool

112
113
114
config HAVE_KERNEL_LZO
	bool

115
116
117
config HAVE_KERNEL_LZ4
	bool

118
choice
119
120
	prompt "Kernel compression mode"
	default KERNEL_GZIP
121
	depends on HAVE_KERNEL_GZIP || HAVE_KERNEL_BZIP2 || HAVE_KERNEL_LZMA || HAVE_KERNEL_XZ || HAVE_KERNEL_LZO || HAVE_KERNEL_LZ4
122
	help
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
	  The linux kernel is a kind of self-extracting executable.
	  Several compression algorithms are available, which differ
	  in efficiency, compression and decompression speed.
	  Compression speed is only relevant when building a kernel.
	  Decompression speed is relevant at each boot.

	  If you have any problems with bzip2 or lzma compressed
	  kernels, mail me (Alain Knaff) <alain@knaff.lu>. (An older
	  version of this functionality (bzip2 only), for 2.4, was
	  supplied by Christian Ludwig)

	  High compression options are mostly useful for users, who
	  are low on disk space (embedded systems), but for whom ram
	  size matters less.

	  If in doubt, select 'gzip'

config KERNEL_GZIP
141
142
143
	bool "Gzip"
	depends on HAVE_KERNEL_GZIP
	help
144
145
	  The old and tried gzip compression. It provides a good balance
	  between compression ratio and decompression speed.
146
147
148

config KERNEL_BZIP2
	bool "Bzip2"
149
	depends on HAVE_KERNEL_BZIP2
150
151
	help
	  Its compression ratio and speed is intermediate.
152
	  Decompression speed is slowest among the choices.  The kernel
153
154
155
	  size is about 10% smaller with bzip2, in comparison to gzip.
	  Bzip2 uses a large amount of memory. For modern kernels you
	  will need at least 8MB RAM or more for booting.
156
157

config KERNEL_LZMA
158
159
160
	bool "LZMA"
	depends on HAVE_KERNEL_LZMA
	help
161
162
163
	  This compression algorithm's ratio is best.  Decompression speed
	  is between gzip and bzip2.  Compression is slowest.
	  The kernel size is about 33% smaller with LZMA in comparison to gzip.
164

165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
config KERNEL_XZ
	bool "XZ"
	depends on HAVE_KERNEL_XZ
	help
	  XZ uses the LZMA2 algorithm and instruction set specific
	  BCJ filters which can improve compression ratio of executable
	  code. The size of the kernel is about 30% smaller with XZ in
	  comparison to gzip. On architectures for which there is a BCJ
	  filter (i386, x86_64, ARM, IA-64, PowerPC, and SPARC), XZ
	  will create a few percent smaller kernel than plain LZMA.

	  The speed is about the same as with LZMA: The decompression
	  speed of XZ is better than that of bzip2 but worse than gzip
	  and LZO. Compression is slow.

180
181
182
183
config KERNEL_LZO
	bool "LZO"
	depends on HAVE_KERNEL_LZO
	help
184
	  Its compression ratio is the poorest among the choices. The kernel
185
	  size is about 10% bigger than gzip; however its speed
186
187
	  (both compression and decompression) is the fastest.

188
189
190
191
192
193
194
195
196
197
198
199
config KERNEL_LZ4
	bool "LZ4"
	depends on HAVE_KERNEL_LZ4
	help
	  LZ4 is an LZ77-type compressor with a fixed, byte-oriented encoding.
	  A preliminary version of LZ4 de/compression tool is available at
	  <https://code.google.com/p/lz4/>.

	  Its compression ratio is worse than LZO. The size of the kernel
	  is about 8% bigger than LZO. But the decompression speed is
	  faster than LZO.

200
201
endchoice

202
203
204
205
206
207
208
209
210
config DEFAULT_HOSTNAME
	string "Default hostname"
	default "(none)"
	help
	  This option determines the default system hostname before userspace
	  calls sethostname(2). The kernel traditionally uses "(none)" here,
	  but you may wish to use a different default here to make a minimal
	  system more usable with less configuration.

Linus Torvalds's avatar
Linus Torvalds committed
211
212
config SWAP
	bool "Support for paging of anonymous memory (swap)"
213
	depends on MMU && BLOCK
Linus Torvalds's avatar
Linus Torvalds committed
214
215
216
	default y
	help
	  This option allows you to choose whether you want to have support
217
	  for so called swap devices or swap files in your kernel that are
Linus Torvalds's avatar
Linus Torvalds committed
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
	  used to provide more virtual memory than the actual RAM present
	  in your computer.  If unsure say Y.

config SYSVIPC
	bool "System V IPC"
	---help---
	  Inter Process Communication is a suite of library functions and
	  system calls which let processes (running programs) synchronize and
	  exchange information. It is generally considered to be a good thing,
	  and some programs won't run unless you say Y here. In particular, if
	  you want to run the DOS emulator dosemu under Linux (read the
	  DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
	  you'll need to say Y here.

	  You can find documentation about IPC with "info ipc" and also in
	  section 6.4 of the Linux Programmer's Guide, available from
	  <http://www.tldp.org/guides.html>.

236
237
238
239
240
241
config SYSVIPC_SYSCTL
	bool
	depends on SYSVIPC
	depends on SYSCTL
	default y

Linus Torvalds's avatar
Linus Torvalds committed
242
243
config POSIX_MQUEUE
	bool "POSIX Message Queues"
244
	depends on NET
Linus Torvalds's avatar
Linus Torvalds committed
245
246
247
248
249
	---help---
	  POSIX variant of message queues is a part of IPC. In POSIX message
	  queues every message has a priority which decides about succession
	  of receiving it by a process. If you want to compile and run
	  programs written e.g. for Solaris with use of its POSIX message
250
	  queues (functions mq_*) say Y here.
Linus Torvalds's avatar
Linus Torvalds committed
251
252
253
254
255
256
257

	  POSIX message queues are visible as a filesystem called 'mqueue'
	  and can be mounted somewhere if you want to do filesystem
	  operations on message queues.

	  If unsure, say Y.

258
259
260
261
262
263
config POSIX_MQUEUE_SYSCTL
	bool
	depends on POSIX_MQUEUE
	depends on SYSCTL
	default y

264
265
266
267
268
269
270
config CROSS_MEMORY_ATTACH
	bool "Enable process_vm_readv/writev syscalls"
	depends on MMU
	default y
	help
	  Enabling this option adds the system calls process_vm_readv and
	  process_vm_writev which allow a process with the correct privileges
271
	  to directly read from or write to another process' address space.
272
273
	  See the man page for more details.

274
275
276
277
278
279
280
281
282
283
284
285
config FHANDLE
	bool "open by fhandle syscalls"
	select EXPORTFS
	help
	  If you say Y here, a user level program will be able to map
	  file names to handle and then later use the handle for
	  different file system operations. This is useful in implementing
	  userspace file servers, which now track files using handles instead
	  of names. The handle would remain the same even if file names
	  get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2)
	  syscalls.

286
287
288
289
290
291
292
293
294
295
config USELIB
	bool "uselib syscall"
	default y
	help
	  This option enables the uselib syscall, a system call used in the
	  dynamic linker from libc5 and earlier.  glibc does not use this
	  system call.  If you intend to run programs built on libc5 or
	  earlier, you may need to enable this syscall.  Current systems
	  running glibc can safely disable this.

296
297
298
299
300
301
302
303
304
config AUDIT
	bool "Auditing support"
	depends on NET
	help
	  Enable auditing infrastructure that can be used with another
	  kernel subsystem, such as SELinux (which requires this for
	  logging of avc messages output).  Does not do system-call
	  auditing without CONFIG_AUDITSYSCALL.

305
306
307
config HAVE_ARCH_AUDITSYSCALL
	bool

308
309
config AUDITSYSCALL
	bool "Enable system-call auditing support"
310
	depends on AUDIT && HAVE_ARCH_AUDITSYSCALL
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
	default y if SECURITY_SELINUX
	help
	  Enable low-overhead system-call auditing infrastructure that
	  can be used independently or with another kernel subsystem,
	  such as SELinux.

config AUDIT_WATCH
	def_bool y
	depends on AUDITSYSCALL
	select FSNOTIFY

config AUDIT_TREE
	def_bool y
	depends on AUDITSYSCALL
	select FSNOTIFY

source "kernel/irq/Kconfig"
source "kernel/time/Kconfig"

menu "CPU/Task time and stats accounting"

332
333
334
config VIRT_CPU_ACCOUNTING
	bool

335
336
337
choice
	prompt "Cputime accounting"
	default TICK_CPU_ACCOUNTING if !PPC64
338
	default VIRT_CPU_ACCOUNTING_NATIVE if PPC64
339
340
341
342

# Kind of a stub config for the pure tick based cputime accounting
config TICK_CPU_ACCOUNTING
	bool "Simple tick based cputime accounting"
343
	depends on !S390 && !NO_HZ_FULL
344
345
346
347
348
349
350
	help
	  This is the basic tick based cputime accounting that maintains
	  statistics about user, system and idle time spent on per jiffies
	  granularity.

	  If unsure, say Y.

351
config VIRT_CPU_ACCOUNTING_NATIVE
352
	bool "Deterministic task and CPU time accounting"
353
	depends on HAVE_VIRT_CPU_ACCOUNTING && !NO_HZ_FULL
354
	select VIRT_CPU_ACCOUNTING
355
356
357
358
359
360
361
362
363
	help
	  Select this option to enable more accurate task and CPU time
	  accounting.  This is done by reading a CPU counter on each
	  kernel entry and exit and on transitions within the kernel
	  between system, softirq and hardirq state, so there is a
	  small performance impact.  In the case of s390 or IBM POWER > 5,
	  this also enables accounting of stolen time on logically-partitioned
	  systems.

364
365
config VIRT_CPU_ACCOUNTING_GEN
	bool "Full dynticks CPU time accounting"
366
	depends on HAVE_CONTEXT_TRACKING
367
	depends on HAVE_VIRT_CPU_ACCOUNTING_GEN
368
369
370
371
372
373
374
375
376
377
378
379
380
381
	select VIRT_CPU_ACCOUNTING
	select CONTEXT_TRACKING
	help
	  Select this option to enable task and CPU time accounting on full
	  dynticks systems. This accounting is implemented by watching every
	  kernel-user boundaries using the context tracking subsystem.
	  The accounting is thus performed at the expense of some significant
	  overhead.

	  For now this is only useful if you are working on the full
	  dynticks subsystem development.

	  If unsure, say N.

382
383
config IRQ_TIME_ACCOUNTING
	bool "Fine granularity task level IRQ time accounting"
384
	depends on HAVE_IRQ_TIME_ACCOUNTING && !NO_HZ_FULL
385
386
387
388
389
390
391
392
393
394
	help
	  Select this option to enable fine granularity task irq time
	  accounting. This is done by reading a timestamp on each
	  transitions between softirq and hardirq state, so there can be a
	  small performance impact.

	  If in doubt, say N here.

endchoice

Linus Torvalds's avatar
Linus Torvalds committed
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
config BSD_PROCESS_ACCT
	bool "BSD Process Accounting"
	help
	  If you say Y here, a user level program will be able to instruct the
	  kernel (via a special system call) to write process accounting
	  information to a file: whenever a process exits, information about
	  that process will be appended to the file by the kernel.  The
	  information includes things such as creation time, owning user,
	  command name, memory usage, controlling terminal etc. (the complete
	  list is in the struct acct in <file:include/linux/acct.h>).  It is
	  up to the user level program to do useful things with this
	  information.  This is generally a good idea, so say Y.

config BSD_PROCESS_ACCT_V3
	bool "BSD Process Accounting version 3 file format"
	depends on BSD_PROCESS_ACCT
	default n
	help
	  If you say Y here, the process accounting information is written
	  in a new file format that also logs the process IDs of each
	  process and it's parent. Note that this file format is incompatible
	  with previous v0/v1/v2 file formats, so you will need updated tools
	  for processing it. A preliminary version of these tools is available
418
	  at <http://www.gnu.org/software/acct/>.
Linus Torvalds's avatar
Linus Torvalds committed
419

420
config TASKSTATS
421
	bool "Export task/process statistics through netlink"
422
423
424
425
426
427
428
429
430
431
432
	depends on NET
	default n
	help
	  Export selected statistics for tasks/processes through the
	  generic netlink interface. Unlike BSD process accounting, the
	  statistics are available during the lifetime of tasks/processes as
	  responses to commands. Like BSD accounting, they are sent to user
	  space on task exit.

	  Say N if unsure.

433
config TASK_DELAY_ACCT
434
	bool "Enable per-task delay accounting"
435
	depends on TASKSTATS
436
437
438
439
440
441
442
443
	help
	  Collect information on time spent by a task waiting for system
	  resources like cpu, synchronous block I/O completion and swapping
	  in pages. Such statistics can help in setting a task's priorities
	  relative to other tasks for cpu, io, rss limits etc.

	  Say N if unsure.

444
config TASK_XACCT
445
	bool "Enable extended accounting over taskstats"
446
447
448
449
450
451
452
453
	depends on TASKSTATS
	help
	  Collect extended task accounting data and send the data
	  to userland for processing over the taskstats interface.

	  Say N if unsure.

config TASK_IO_ACCOUNTING
454
	bool "Enable per-task storage I/O accounting"
455
456
457
458
459
460
461
	depends on TASK_XACCT
	help
	  Collect information on the number of bytes of storage I/O which this
	  task has caused.

	  Say N if unsure.

462
endmenu # "CPU/Task time and stats accounting"
Thomas Gleixner's avatar
Thomas Gleixner committed
463

Mike Travis's avatar
Mike Travis committed
464
465
466
467
menu "RCU Subsystem"

choice
	prompt "RCU Implementation"
468
	default TREE_RCU
Mike Travis's avatar
Mike Travis committed
469
470
471

config TREE_RCU
	bool "Tree-based hierarchical RCU"
472
	depends on !PREEMPT && SMP
473
	select IRQ_WORK
Mike Travis's avatar
Mike Travis committed
474
475
476
	help
	  This option selects the RCU implementation that is
	  designed for very large SMP system with hundreds or
Paul E. McKenney's avatar
Paul E. McKenney committed
477
478
	  thousands of CPUs.  It also scales down nicely to
	  smaller systems.
Mike Travis's avatar
Mike Travis committed
479

480
config PREEMPT_RCU
Paul E. McKenney's avatar
Paul E. McKenney committed
481
	bool "Preemptible tree-based hierarchical RCU"
482
	depends on PREEMPT
483
	select IRQ_WORK
484
485
486
487
	help
	  This option selects the RCU implementation that is
	  designed for very large SMP systems with hundreds or
	  thousands of CPUs, but for which real-time response
488
489
	  is also required.  It also scales down nicely to
	  smaller systems.
490

491
492
	  Select this option if you are unsure.

493
494
config TINY_RCU
	bool "UP-only small-memory-footprint RCU"
495
	depends on !PREEMPT && !SMP
496
497
498
499
500
501
	help
	  This option selects the RCU implementation that is
	  designed for UP systems from which real-time response
	  is not required.  This option greatly reduces the
	  memory footprint of RCU.

Mike Travis's avatar
Mike Travis committed
502
503
endchoice

Paul E. McKenney's avatar
Paul E. McKenney committed
504
505
506
507
508
509
510
511
512
513
config TASKS_RCU
	bool "Task_based RCU implementation using voluntary context switch"
	default n
	help
	  This option enables a task-based RCU implementation that uses
	  only voluntary context switch (not preemption!), idle, and
	  user-mode execution as quiescent states.

	  If unsure, say N.

514
config RCU_STALL_COMMON
515
	def_bool ( TREE_RCU || PREEMPT_RCU || RCU_TRACE )
516
517
518
519
520
521
	help
	  This option enables RCU CPU stall code that is common between
	  the TINY and TREE variants of RCU.  The purpose is to allow
	  the tiny variants to disable RCU CPU stall warnings, while
	  making these warnings mandatory for the tree variants.

522
523
524
config CONTEXT_TRACKING
       bool

525
526
config RCU_USER_QS
	bool "Consider userspace as in RCU extended quiescent state"
527
528
	depends on HAVE_CONTEXT_TRACKING && SMP
	select CONTEXT_TRACKING
529
530
531
532
533
	help
	  This option sets hooks on kernel / userspace boundaries and
	  puts RCU in extended quiescent state when the CPU runs in
	  userspace. It means that when a CPU runs in userspace, it is
	  excluded from the global RCU state machine and thus doesn't
534
	  try to keep the timer tick on for RCU.
535

536
	  Unless you want to hack and help the development of the full
537
	  dynticks mode, you shouldn't enable this option.  It also
538
	  adds unnecessary overhead.
539
540
541

	  If unsure say N

542
543
544
config CONTEXT_TRACKING_FORCE
	bool "Force context tracking"
	depends on CONTEXT_TRACKING
545
	default y if !NO_HZ_FULL
546
	help
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
	  The major pre-requirement for full dynticks to work is to
	  support the context tracking subsystem. But there are also
	  other dependencies to provide in order to make the full
	  dynticks working.

	  This option stands for testing when an arch implements the
	  context tracking backend but doesn't yet fullfill all the
	  requirements to make the full dynticks feature working.
	  Without the full dynticks, there is no way to test the support
	  for context tracking and the subsystems that rely on it: RCU
	  userspace extended quiescent state and tickless cputime
	  accounting. This option copes with the absence of the full
	  dynticks subsystem by forcing the context tracking on all
	  CPUs in the system.

562
	  Say Y only if you're working on the development of an
563
564
565
566
567
	  architecture backend for the context tracking.

	  Say N otherwise, this option brings an overhead that you
	  don't want in production.

568

Mike Travis's avatar
Mike Travis committed
569
570
571
572
config RCU_FANOUT
	int "Tree-based hierarchical RCU fanout value"
	range 2 64 if 64BIT
	range 2 32 if !64BIT
573
	depends on TREE_RCU || PREEMPT_RCU
Mike Travis's avatar
Mike Travis committed
574
575
576
577
578
	default 64 if 64BIT
	default 32 if !64BIT
	help
	  This option controls the fanout of hierarchical implementations
	  of RCU, allowing RCU to work efficiently on machines with
579
580
581
582
583
584
	  large numbers of CPUs.  This value must be at least the fourth
	  root of NR_CPUS, which allows NR_CPUS to be insanely large.
	  The default value of RCU_FANOUT should be used for production
	  systems, but if you are stress-testing the RCU implementation
	  itself, small RCU_FANOUT values allow you to test large-system
	  code paths on small(er) systems.
Mike Travis's avatar
Mike Travis committed
585
586
587
588

	  Select a specific number if testing RCU itself.
	  Take the default if unsure.

589
590
591
592
config RCU_FANOUT_LEAF
	int "Tree-based hierarchical RCU leaf-level fanout value"
	range 2 RCU_FANOUT if 64BIT
	range 2 RCU_FANOUT if !64BIT
593
	depends on TREE_RCU || PREEMPT_RCU
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
	default 16
	help
	  This option controls the leaf-level fanout of hierarchical
	  implementations of RCU, and allows trading off cache misses
	  against lock contention.  Systems that synchronize their
	  scheduling-clock interrupts for energy-efficiency reasons will
	  want the default because the smaller leaf-level fanout keeps
	  lock contention levels acceptably low.  Very large systems
	  (hundreds or thousands of CPUs) will instead want to set this
	  value to the maximum value possible in order to reduce the
	  number of cache misses incurred during RCU's grace-period
	  initialization.  These systems tend to run CPU-bound, and thus
	  are not helped by synchronized interrupts, and thus tend to
	  skew them, which reduces lock contention enough that large
	  leaf-level fanouts work well.

	  Select a specific number if testing RCU itself.

	  Select the maximum permissible value for large systems.

	  Take the default if unsure.

Mike Travis's avatar
Mike Travis committed
616
617
config RCU_FANOUT_EXACT
	bool "Disable tree-based hierarchical RCU auto-balancing"
618
	depends on TREE_RCU || PREEMPT_RCU
Mike Travis's avatar
Mike Travis committed
619
620
621
622
623
624
625
626
627
628
629
	default n
	help
	  This option forces use of the exact RCU_FANOUT value specified,
	  regardless of imbalances in the hierarchy.  This is useful for
	  testing RCU itself, and might one day be useful on systems with
	  strong NUMA behavior.

	  Without RCU_FANOUT_EXACT, the code will balance the hierarchy.

	  Say N if unsure.

630
631
config RCU_FAST_NO_HZ
	bool "Accelerate last non-dyntick-idle CPU's grace periods"
632
	depends on NO_HZ_COMMON && SMP
633
634
	default n
	help
635
636
637
638
639
640
641
	  This option permits CPUs to enter dynticks-idle state even if
	  they have RCU callbacks queued, and prevents RCU from waking
	  these CPUs up more than roughly once every four jiffies (by
	  default, you can adjust this using the rcutree.rcu_idle_gp_delay
	  parameter), thus improving energy efficiency.  On the other
	  hand, this option increases the duration of RCU grace periods,
	  for example, slowing down synchronize_rcu().
642

643
644
	  Say Y if energy efficiency is critically important, and you
	  	don't care about increased grace-period durations.
645
646
647

	  Say N if you are unsure.

Mike Travis's avatar
Mike Travis committed
648
config TREE_RCU_TRACE
649
	def_bool RCU_TRACE && ( TREE_RCU || PREEMPT_RCU )
Mike Travis's avatar
Mike Travis committed
650
651
	select DEBUG_FS
	help
652
	  This option provides tracing for the TREE_RCU and
653
	  PREEMPT_RCU implementations, permitting Makefile to
654
	  trivially select kernel/rcutree_trace.c.
Mike Travis's avatar
Mike Travis committed
655

656
657
config RCU_BOOST
	bool "Enable RCU priority boosting"
658
	depends on RT_MUTEXES && PREEMPT_RCU
659
660
661
662
663
664
665
666
667
668
	default n
	help
	  This option boosts the priority of preempted RCU readers that
	  block the current preemptible RCU grace period for too long.
	  This option also prevents heavy loads from blocking RCU
	  callback invocation for all flavors of RCU.

	  Say Y here if you are working with real-time apps or heavy loads
	  Say N here if you are unsure.

669
670
config RCU_KTHREAD_PRIO
	int "Real-time priority to use for RCU worker threads"
671
672
673
674
	range 1 99
	depends on RCU_BOOST
	default 1
	help
675
676
677
678
679
680
681
682
	  This option specifies the SCHED_FIFO priority value that will be
	  assigned to the rcuc/n and rcub/n threads and is also the value
	  used for RCU_BOOST (if enabled). If you are working with a
	  real-time application that has one or more CPU-bound threads
	  running at a real-time priority level, you should set
	  RCU_KTHREAD_PRIO to a priority higher than the highest-priority
	  real-time CPU-bound application thread.  The default RCU_KTHREAD_PRIO
	  value of 1 is appropriate in the common case, which is real-time
683
684
685
686
687
	  applications that do not have any CPU-bound threads.

	  Some real-time applications might not have a single real-time
	  thread that saturates a given CPU, but instead might have
	  multiple real-time threads that, taken together, fully utilize
688
	  that CPU.  In this case, you should set RCU_KTHREAD_PRIO to
689
690
691
692
	  a priority higher than the lowest-priority thread that is
	  conspiring to prevent the CPU from running any non-real-time
	  tasks.  For example, if one thread at priority 10 and another
	  thread at priority 5 are between themselves fully consuming
693
	  the CPU time on a given CPU, then RCU_KTHREAD_PRIO should be
694
	  set to priority 6 or higher.
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710

	  Specify the real-time priority, or take the default if unsure.

config RCU_BOOST_DELAY
	int "Milliseconds to delay boosting after RCU grace-period start"
	range 0 3000
	depends on RCU_BOOST
	default 500
	help
	  This option specifies the time to wait after the beginning of
	  a given grace period before priority-boosting preempted RCU
	  readers blocking that grace period.  Note that any RCU reader
	  blocking an expedited RCU grace period is boosted immediately.

	  Accept the default if unsure.

Paul E. McKenney's avatar
Paul E. McKenney committed
711
config RCU_NOCB_CPU
712
	bool "Offload RCU callback processing from boot-selected CPUs"
713
	depends on TREE_RCU || PREEMPT_RCU
Paul E. McKenney's avatar
Paul E. McKenney committed
714
715
716
717
718
719
720
721
722
	default n
	help
	  Use this option to reduce OS jitter for aggressive HPC or
	  real-time workloads.	It can also be used to offload RCU
	  callback invocation to energy-efficient CPUs in battery-powered
	  asymmetric multiprocessors.

	  This option offloads callback invocation from the set of
	  CPUs specified at boot time by the rcu_nocbs parameter.
723
724
725
726
727
728
729
	  For each such CPU, a kthread ("rcuox/N") will be created to
	  invoke callbacks, where the "N" is the CPU being offloaded,
	  and where the "x" is "b" for RCU-bh, "p" for RCU-preempt, and
	  "s" for RCU-sched.  Nothing prevents this kthread from running
	  on the specified CPUs, but (1) the kthreads may be preempted
	  between each callback, and (2) affinity or cgroups can be used
	  to force the kthreads to run on whatever set of CPUs is desired.
Paul E. McKenney's avatar
Paul E. McKenney committed
730

731
	  Say Y here if you want to help to debug reduced OS jitter.
Paul E. McKenney's avatar
Paul E. McKenney committed
732
733
	  Say N here if you are unsure.

734
735
736
choice
	prompt "Build-forced no-CBs CPUs"
	default RCU_NOCB_CPU_NONE
737
	depends on RCU_NOCB_CPU
738
	help
739
740
741
742
	  This option allows no-CBs CPUs (whose RCU callbacks are invoked
	  from kthreads rather than from softirq context) to be specified
	  at build time.  Additional no-CBs CPUs may be specified by
	  the rcu_nocbs= boot parameter.
743
744
745
746
747
748

config RCU_NOCB_CPU_NONE
	bool "No build_forced no-CBs CPUs"
	help
	  This option does not force any of the CPUs to be no-CBs CPUs.
	  Only CPUs designated by the rcu_nocbs= boot parameter will be
749
750
751
752
753
754
755
	  no-CBs CPUs, whose RCU callbacks will be invoked by per-CPU
	  kthreads whose names begin with "rcuo".  All other CPUs will
	  invoke their own RCU callbacks in softirq context.

	  Select this option if you want to choose no-CBs CPUs at
	  boot time, for example, to allow testing of different no-CBs
	  configurations without having to rebuild the kernel each time.
756
757
758
759

config RCU_NOCB_CPU_ZERO
	bool "CPU 0 is a build_forced no-CBs CPU"
	help
760
761
762
763
764
765
	  This option forces CPU 0 to be a no-CBs CPU, so that its RCU
	  callbacks are invoked by a per-CPU kthread whose name begins
	  with "rcuo".	Additional CPUs may be designated as no-CBs
	  CPUs using the rcu_nocbs= boot parameter will be no-CBs CPUs.
	  All other CPUs will invoke their own RCU callbacks in softirq
	  context.
766
767

	  Select this if CPU 0 needs to be a no-CBs CPU for real-time
768
769
	  or energy-efficiency reasons, but the real reason it exists
	  is to ensure that randconfig testing covers mixed systems.
770
771
772
773
774

config RCU_NOCB_CPU_ALL
	bool "All CPUs are build_forced no-CBs CPUs"
	help
	  This option forces all CPUs to be no-CBs CPUs.  The rcu_nocbs=
775
776
777
778
779
780
	  boot parameter will be ignored.  All CPUs' RCU callbacks will
	  be executed in the context of per-CPU rcuo kthreads created for
	  this purpose.  Assuming that the kthreads whose names start with
	  "rcuo" are bound to "housekeeping" CPUs, this reduces OS jitter
	  on the remaining CPUs, but might decrease memory locality during
	  RCU-callback invocation, thus potentially degrading throughput.
781
782
783
784
785
786

	  Select this if all CPUs need to be no-CBs CPUs for real-time
	  or energy-efficiency reasons.

endchoice

Mike Travis's avatar
Mike Travis committed
787
788
endmenu # "RCU Subsystem"

789
790
791
792
config BUILD_BIN2C
	bool
	default n

Linus Torvalds's avatar
Linus Torvalds committed
793
config IKCONFIG
794
	tristate "Kernel .config support"
795
	select BUILD_BIN2C
Linus Torvalds's avatar
Linus Torvalds committed
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
	---help---
	  This option enables the complete Linux kernel ".config" file
	  contents to be saved in the kernel. It provides documentation
	  of which kernel options are used in a running kernel or in an
	  on-disk kernel.  This information can be extracted from the kernel
	  image file with the script scripts/extract-ikconfig and used as
	  input to rebuild the current kernel or to build another kernel.
	  It can also be extracted from a running kernel by reading
	  /proc/config.gz if enabled (below).

config IKCONFIG_PROC
	bool "Enable access to .config through /proc/config.gz"
	depends on IKCONFIG && PROC_FS
	---help---
	  This option enables access to the kernel configuration file
	  through /proc/config.gz.

813
814
815
config LOG_BUF_SHIFT
	int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
	range 12 21
Adrian Bunk's avatar
Adrian Bunk committed
816
	default 17
817
	depends on PRINTK
818
	help
819
820
821
822
823
	  Select the minimal kernel log buffer size as a power of 2.
	  The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
	  parameter, see below. Any higher size also might be forced
	  by "log_buf_len" boot parameter.

Adrian Bunk's avatar
Adrian Bunk committed
824
	  Examples:
825
		     17 => 128 KB
Adrian Bunk's avatar
Adrian Bunk committed
826
		     16 => 64 KB
827
828
		     15 => 32 KB
		     14 => 16 KB
829
830
831
		     13 =>  8 KB
		     12 =>  4 KB

832
833
config LOG_CPU_MAX_BUF_SHIFT
	int "CPU kernel log buffer size contribution (13 => 8 KB, 17 => 128KB)"
834
	depends on SMP
835
836
837
	range 0 21
	default 12 if !BASE_SMALL
	default 0 if BASE_SMALL
838
	depends on PRINTK
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
	help
	  This option allows to increase the default ring buffer size
	  according to the number of CPUs. The value defines the contribution
	  of each CPU as a power of 2. The used space is typically only few
	  lines however it might be much more when problems are reported,
	  e.g. backtraces.

	  The increased size means that a new buffer has to be allocated and
	  the original static one is unused. It makes sense only on systems
	  with more CPUs. Therefore this value is used only when the sum of
	  contributions is greater than the half of the default kernel ring
	  buffer as defined by LOG_BUF_SHIFT. The default values are set
	  so that more than 64 CPUs are needed to trigger the allocation.

	  Also this option is ignored when "log_buf_len" kernel parameter is
	  used as it forces an exact (power of two) size of the ring buffer.

	  The number of possible CPUs is used for this computation ignoring
	  hotplugging making the compuation optimal for the the worst case
	  scenerio while allowing a simple algorithm to be used from bootup.

	  Examples shift values and their meaning:
		     17 => 128 KB for each CPU
		     16 =>  64 KB for each CPU
		     15 =>  32 KB for each CPU
		     14 =>  16 KB for each CPU
		     13 =>   8 KB for each CPU
		     12 =>   4 KB for each CPU

868
869
870
871
872
873
#
# Architectures with an unreliable sched_clock() should select this:
#
config HAVE_UNSTABLE_SCHED_CLOCK
	bool

874
875
876
config GENERIC_SCHED_CLOCK
	bool

877
878
879
880
881
882
883
#
# For architectures that want to enable the support for NUMA-affine scheduler
# balancing logic:
#
config ARCH_SUPPORTS_NUMA_BALANCING
	bool

Peter Zijlstra's avatar
Peter Zijlstra committed
884
885
886
887
888
889
#
# For architectures that know their GCC __int128 support is sound
#
config ARCH_SUPPORTS_INT128
	bool

890
891
892
893
894
895
# For architectures that (ab)use NUMA to represent different memory regions
# all cpu-local but of different latencies, such as SuperH.
#
config ARCH_WANT_NUMA_VARIABLE_LOCALITY
	bool

896
897
898
899
900
config NUMA_BALANCING_DEFAULT_ENABLED
	bool "Automatically enable NUMA aware memory/task placement"
	default y
	depends on NUMA_BALANCING
	help
901
	  If set, automatic NUMA balancing will be enabled if running on a NUMA
902
903
	  machine.

904
905
906
907
908
909
910
911
config NUMA_BALANCING
	bool "Memory placement aware NUMA scheduler"
	depends on ARCH_SUPPORTS_NUMA_BALANCING
	depends on !ARCH_WANT_NUMA_VARIABLE_LOCALITY
	depends on SMP && NUMA && MIGRATION
	help
	  This option adds support for automatic NUMA aware memory/task placement.
	  The mechanism is quite primitive and is based on migrating memory when
912
	  it has references to the node the task is running on.
913
914
915

	  This system will be inactive on UMA systems.

Li Zefan's avatar
Li Zefan committed
916
917
menuconfig CGROUPS
	boolean "Control Group support"
Tejun Heo's avatar
Tejun Heo committed
918
	select KERNFS
919
	help
Li Zefan's avatar
Li Zefan committed
920
	  This option adds support for grouping sets of processes together, for
921
922
923
924
	  use with process control subsystems such as Cpusets, CFS, memory
	  controls or device isolation.
	  See
		- Documentation/scheduler/sched-design-CFS.txt	(CFS)
925
926
		- Documentation/cgroups/ (features for grouping, isolation
					  and resource control)
927
928
929

	  Say N if unsure.

Li Zefan's avatar
Li Zefan committed
930
931
if CGROUPS

932
933
934
935
936
937
config CGROUP_DEBUG
	bool "Example debug cgroup subsystem"
	default n
	help
	  This option enables a simple cgroup subsystem that
	  exports useful debugging information about the cgroups
Li Zefan's avatar
Li Zefan committed
938
	  framework.
939

Li Zefan's avatar
Li Zefan committed
940
	  Say N if unsure.
941
942

config CGROUP_FREEZER
Li Zefan's avatar
Li Zefan committed
943
944
945
	bool "Freezer cgroup subsystem"
	help
	  Provides a way to freeze and unfreeze all tasks in a
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
	  cgroup.

config CGROUP_DEVICE
	bool "Device controller for cgroups"
	help
	  Provides a cgroup implementing whitelists for devices which
	  a process in the cgroup can mknod or open.

config CPUSETS
	bool "Cpuset support"
	help
	  This option will let you create and manage CPUSETs which
	  allow dynamically partitioning a system into sets of CPUs and
	  Memory Nodes and assigning tasks to run only within those sets.
	  This is primarily useful on large SMP or NUMA systems.

	  Say N if unsure.

Li Zefan's avatar
Li Zefan committed
964
965
966
967
968
config PROC_PID_CPUSET
	bool "Include legacy /proc/<pid>/cpuset file"
	depends on CPUSETS
	default y

969
970
971
972
config CGROUP_CPUACCT
	bool "Simple CPU accounting cgroup subsystem"
	help
	  Provides a simple Resource Controller for monitoring the
Li Zefan's avatar
Li Zefan committed
973
	  total CPU consumed by the tasks in a cgroup.
974

975
976
977
978
config RESOURCE_COUNTERS
	bool "Resource counters"
	help
	  This option enables controller independent resource accounting
Li Zefan's avatar
Li Zefan committed
979
	  infrastructure that works with cgroups.
980

981
982
983
config PAGE_COUNTER
       bool

Andrew Morton's avatar
Andrew Morton committed
984
config MEMCG
985
	bool "Memory Resource Controller for Control Groups"
986
	select PAGE_COUNTER
987
	select EVENTFD
988
	help
989
	  Provides a memory resource controller that manages both anonymous
990
	  memory and page cache. (See Documentation/cgroups/memory.txt)
991
992

	  Note that setting this option increases fixed memory overhead
993
	  associated with each page of memory in the system. By this,
Sergey Dyasly's avatar
Sergey Dyasly committed
994
	  8(16)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
995
996
	  usage tracking struct at boot. Total amount of this is printed out
	  at boot.
997
998

	  Only enable when you're ok with these trade offs and really
999
1000
1001
	  sure you need the memory resource controller. Even when you enable
	  this, you can set "cgroup_disable=memory" at your boot option to
	  disable memory resource controller and you can avoid overheads.
Li Zefan's avatar
Li Zefan committed
1002
	  (and lose benefits of memory resource controller)
1003

Andrew Morton's avatar
Andrew Morton committed
1004
config MEMCG_SWAP
1005
	bool "Memory Resource Controller Swap Extension"
Andrew Morton's avatar
Andrew Morton committed
1006
	depends on MEMCG && SWAP
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
	help
	  Add swap management feature to memory resource controller. When you
	  enable this, you can limit mem+swap usage per cgroup. In other words,
	  when you disable this, memory resource controller has no cares to
	  usage of swap...a process can exhaust all of the swap. This extension
	  is useful when you want to avoid exhaustion swap but this itself
	  adds more overheads and consumes memory for remembering information.
	  Especially if you use 32bit system or small memory system, please
	  be careful about enabling this. When memory resource controller
	  is disabled by boot option, this will be automatically disabled and
	  there will be no overhead from this. Even when you set this config=y,
1018
	  if boot option "swapaccount=0" is set, swap will not be accounted.
1019
1020
	  Now, memory usage of swap_cgroup is 2 bytes per entry. If swap page
	  size is 4096bytes, 512k per 1Gbytes of swap.
Andrew Morton's avatar
Andrew Morton committed
1021
config MEMCG_SWAP_ENABLED
1022
	bool "Memory Resource Controller Swap Extension enabled by default"
Andrew Morton's avatar
Andrew Morton committed
1023
	depends on MEMCG_SWAP
1024
1025
1026
1027
	default y
	help
	  Memory Resource Controller Swap Extension comes with its price in
	  a bigger memory consumption. General purpose distribution kernels
Jim Cromie's avatar
Jim Cromie committed
1028
	  which want to enable the feature but keep it disabled by default
1029
	  and let the user enable it by swapaccount=1 boot command line
1030
1031
1032
	  parameter should have this option unselected.
	  For those who want to have the feature enabled by default should
	  select this option (if, for some reason, they need to disable it
1033
	  then swapaccount=0 does the trick).
Andrew Morton's avatar
Andrew Morton committed
1034
config MEMCG_KMEM
1035
1036
	bool "Memory Resource Controller Kernel Memory accounting"
	depends on MEMCG
1037
	depends on SLUB || SLAB
1038
1039
1040
1041
1042
1043
1044
	help
	  The Kernel Memory extension for Memory Resource Controller can limit
	  the amount of memory used by kernel objects in the system. Those are
	  fundamentally different from the entities handled by the standard
	  Memory Controller, which are page-based, and can be swapped. Users of
	  the kmem extension can use it to guarantee that no group of processes
	  will ever exhaust kernel resources alone.
1045

1046
1047
1048
1049
1050
1051
	  WARNING: Current implementation lacks reclaim support. That means
	  allocation attempts will fail when close to the limit even if there
	  are plenty of kmem available for reclaim. That makes this option
	  unusable in real life so DO NOT SELECT IT unless for development
	  purposes.

1052
1053
config CGROUP_HUGETLB
	bool "HugeTLB Resource Controller for Control Groups"
1054
	depends on RESOURCE_COUNTERS && HUGETLB_PAGE
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
	default n
	help
	  Provides a cgroup Resource Controller for HugeTLB pages.
	  When you enable this, you can put a per cgroup limit on HugeTLB usage.
	  The limit is enforced during page fault. Since HugeTLB doesn't
	  support page reclaim, enforcing the limit at page fault time implies
	  that, the application will get SIGBUS signal if it tries to access
	  HugeTLB pages beyond its limit. This requires the application to know
	  beforehand how much HugeTLB pages it would require for its use. The
	  control group is tracked in the third page lru pointer. This means
	  that we cannot use the controller with huge page less than 3 pages.

Stephane Eranian's avatar
Stephane Eranian committed
1067
1068
1069
1070
1071
config CGROUP_PERF
	bool "Enable perf_event per-cpu per-container group (cgroup) monitoring"
	depends on PERF_EVENTS && CGROUPS
	help
	  This option extends the per-cpu mode to restrict monitoring to
1072
	  threads which belong to the cgroup specified and run on the
Stephane Eranian's avatar
Stephane Eranian committed
1073
1074
1075
1076
	  designated cpu.

	  Say N if unsure.

Dhaval Giani's avatar
Dhaval Giani committed
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
menuconfig CGROUP_SCHED
	bool "Group CPU scheduler"
	default n
	help
	  This feature lets CPU scheduler recognize task groups and control CPU
	  bandwidth allocation to such task groups. It uses cgroups to group
	  tasks.

if CGROUP_SCHED
config FAIR_GROUP_SCHED
	bool "Group scheduling for SCHED_OTHER"
	depends on CGROUP_SCHED
	default CGROUP_SCHED

1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
config CFS_BANDWIDTH
	bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED"
	depends on FAIR_GROUP_SCHED
	default n
	help
	  This option allows users to define CPU bandwidth rates (limits) for
	  tasks running within the fair group scheduler.  Groups with no limit
	  set are considered to be unconstrained and will run with no
	  restriction.
	  See tip/Documentation/scheduler/sched-bwc.txt for more information.

Dhaval Giani's avatar
Dhaval Giani committed
1102
1103
1104
1105
1106
1107
config RT_GROUP_SCHED
	bool "Group scheduling for SCHED_RR/FIFO"
	depends on CGROUP_SCHED
	default n
	help
	  This feature lets you explicitly allocate real CPU bandwidth
1108
	  to task groups. If enabled, it will also make it impossible to
Dhaval Giani's avatar
Dhaval Giani committed
1109
1110
1111
1112
1113
1114
	  schedule realtime tasks for non-root users until you allocate
	  realtime bandwidth for them.
	  See Documentation/scheduler/sched-rt-group.txt for more information.

endif #CGROUP_SCHED

1115
config BLK_CGROUP
Tejun Heo's avatar
Tejun Heo committed
1116
	bool "Block IO controller"
1117
	depends on BLOCK
1118
1119
1120
1121
1122
1123
1124
1125
	default n
	---help---
	Generic block IO controller cgroup interface. This is the common
	cgroup interface which should be used by various IO controlling
	policies.

	Currently, CFQ IO scheduler uses it to recognize task groups and
	control disk bandwidth allocation (proportional time slice allocation)
1126
1127
	to such task groups. It is also used by bio throttling logic in
	block layer to implement upper limit in IO rates on a device.
1128
1129

	This option only enables generic Block IO controller infrastructure.
1130
	One needs to also enable actual IO controlling logic/policy. For
Michael Witten's avatar
Michael Witten committed
1131
1132
	enabling proportional weight division of disk bandwidth in CFQ, set
	CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
1133
	CONFIG_BLK_DEV_THROTTLING=y.
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144

	See Documentation/cgroups/blkio-controller.txt for more information.

config DEBUG_BLK_CGROUP
	bool "Enable Block IO controller debugging"
	depends on BLK_CGROUP
	default n
	---help---
	Enable some debugging help. Currently it exports additional stat
	files in a cgroup which can be useful for debugging.

Li Zefan's avatar
Li Zefan committed
1145
endif # CGROUPS
1146

1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
config CHECKPOINT_RESTORE
	bool "Checkpoint/restore support" if EXPERT
	default n
	help
	  Enables additional kernel features in a sake of checkpoint/restore.
	  In particular it adds auxiliary prctl codes to setup process text,
	  data and heap segment sizes, and a few additional /proc filesystem
	  entries.

	  If unsure, say N here.

1158
menuconfig NAMESPACES
1159
1160
	bool "Namespaces support" if EXPERT
	default !EXPERT
1161
1162
1163
1164
1165
1166
	help
	  Provides the way to make tasks work with different objects using
	  the same id. For example same IPC id may refer to different objects
	  or same user id or pid may refer to different tasks when used in
	  different namespaces.

1167
1168
if NAMESPACES

1169
1170
config UTS_NS
	bool "UTS namespace"
1171
	default y
1172
1173
1174
1175
	help
	  In this namespace tasks see different info provided with the
	  uname() system call

1176
1177
config IPC_NS
	bool "IPC namespace"
1178
	depends on (SYSVIPC || POSIX_MQUEUE)
1179
	default y
1180
1181
	help
	  In this namespace tasks work with IPC ids which correspond to
1182
	  different IPC objects in different namespaces.
1183

1184
config USER_NS
1185
	bool "User namespace"
1186
	default n
1187
1188
1189
	help
	  This allows containers, i.e. vservers, to use user namespaces
	  to provide different user info for different servers.
1190
1191
1192
1193
1194
1195
1196

	  When user namespaces are enabled in the kernel it is
	  recommended that the MEMCG and MEMCG_KMEM options also be
	  enabled and that user-space use the memory control groups to
	  limit the amount of memory a memory unprivileged users can
	  use.

1197
1198
	  If unsure, say N.

1199
config PID_NS
1200
	bool "PID Namespaces"
1201
	default y
1202
	help
1203
	  Support process id namespaces.  This allows having multiple
1204
	  processes with the same pid as long as they are in different
1205
1206
	  pid namespaces.  This is a building block of containers.

1207
1208
config NET_NS
	bool "Network namespace"
1209
	depends on NET
1210
	default y
1211
1212
1213
1214
	help
	  Allow user space to create what appear to be multiple instances
	  of the network stack.

1215
1216
endif # NAMESPACES

1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
config SCHED_AUTOGROUP
	bool "Automatic process group scheduling"
	select CGROUPS
	select CGROUP_SCHED
	select FAIR_GROUP_SCHED
	help
	  This option optimizes the scheduler for common desktop workloads by
	  automatically creating and populating task groups.  This separation
	  of workloads isolates aggressive CPU burners (like build jobs) from
	  desktop applications.  Task group autogeneration is currently based
	  upon task session.

1229
config SYSFS_DEPRECATED
1230
	bool "Enable deprecated sysfs features to support old userspace tools"
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
	depends on SYSFS
	default n
	help
	  This option adds code that switches the layout of the "block" class
	  devices, to not show up in /sys/class/block/, but only in
	  /sys/block/.

	  This switch is only active when the sysfs.deprecated=1 boot option is
	  passed or the SYSFS_DEPRECATED_V2 option is set.

	  This option allows new kernels to run on old distributions and tools,
	  which might get confused by /sys/class/block/. Since 2007/2008 all
	  major distributions and tools handle this just fine.

	  Recent distributions and userspace tools after 2009/2010 depend on
	  the existence of /sys/class/block/, and will not work with this
	  option enabled.

	  Only if you are using a new kernel on an old distribution, you might
	  need to say Y here.

config SYSFS_DEPRECATED_V2
1253
	bool "Enable deprecated sysfs features by default"
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
	default n
	depends on SYSFS
	depends on SYSFS_DEPRECATED
	help
	  Enable deprecated sysfs by default.

	  See the CONFIG_SYSFS_DEPRECATED option for more details about this
	  option.

	  Only if you are using a new kernel on an old distribution, you might
	  need to say Y here. Even then, odds are you would not need it
	  enabled, you can always pass the boot option if absolutely necessary.

config RELAY
	bool "Kernel->user space relay support (formerly relayfs)"
	help
	  This option enables support for relay interface support in
	  certain file systems (such as debugfs).
	  It is designed to provide an efficient mechanism for tools and
	  facilities to relay large amounts of data from kernel space to
	  user space.

	  If unsure, say N.

1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
config BLK_DEV_INITRD
	bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
	depends on BROKEN || !FRV
	help
	  The initial RAM filesystem is a ramfs which is loaded by the
	  boot loader (loadlin or lilo) and that is mounted as root
	  before the normal boot procedure. It is typically used to
	  load modules needed to mount the "real" root file system,
	  etc. See <file:Documentation/initrd.txt> for details.

	  If RAM disk support (BLK_DEV_RAM) is also included, this
	  also enables initial RAM disk (initrd) support and adds
	  15 Kbytes (more on some other architectures) to the kernel size.

	  If unsure say Y.

1294
1295
if BLK_DEV_INITRD

1296
1297
source "usr/Kconfig"

1298
1299
endif

1300
config CC_OPTIMIZE_FOR_SIZE
1301
	bool "Optimize for size"
1302
1303
1304
1305
	help
	  Enabling this option will pass "-Os" instead of "-O2" to gcc
	  resulting in a smaller kernel.

1306
	  If unsure, say N.
1307

1308
1309
1310
config SYSCTL
	bool

Randy Dunlap's avatar
Randy Dunlap committed
1311
1312
1313
config ANON_INODES
	bool

1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
config HAVE_UID16
	bool

config SYSCTL_EXCEPTION_TRACE
	bool
	help
	  Enable support for /proc/sys/debug/exception-trace.

config SYSCTL_ARCH_UNALIGN_NO_WARN
	bool
	help
	  Enable support for /proc/sys/kernel/ignore-unaligned-usertrap
	  Allows arch to define/use @no_unaligned_warning to possibly warn
	  about unaligned access emulation going on under the hood.

config SYSCTL_ARCH_UNALIGN_ALLOW
	bool
	help
	  Enable support for /proc/sys/kernel/unaligned-trap
	  Allows arches to define/use @unaligned_enabled to runtime toggle
	  the unaligned access emulation.
	  see arch/parisc/kernel/unaligned.c for reference

config HAVE_PCSPKR_PLATFORM
	bool

1340
1341
1342
1343
# interpreter that classic socket filters depend on
config BPF
	bool

1344
1345
menuconfig EXPERT
	bool "Configure standard kernel features (expert users)"
1346
1347
	# Unhide debug options, to make the on-by-default options visible
	select DEBUG_KERNEL
Linus Torvalds's avatar
Linus Torvalds committed
1348
1349
1350
1351
1352
1353
	help
	  This option allows certain base kernel options and settings
          to be disabled or tweaked. This is for specialized
          environments which can tolerate a "non-standard" kernel.
          Only use this if you really know what you are doing.

1354
config UID16
1355
	bool "Enable 16-bit UID system calls" if EXPERT
1356
	depends on HAVE_UID16
1357
1358
1359
1360
	default y
	help
	  This enables the legacy 16-bit UID syscall wrappers.

1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
config SGETMASK_SYSCALL
	bool "sgetmask/ssetmask syscalls support" if EXPERT
	def_bool PARISC || MN10300 || BLACKFIN || M68K || PPC || MIPS || X86 || SPARC || CRIS || MICROBLAZE || SUPERH
	---help---
	  sys_sgetmask and sys_ssetmask are obsolete system calls
	  no longer supported in libc but still enabled by default in some
	  architectures.

	  If unsure, leave the default option here.

1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
config SYSFS_SYSCALL
	bool "Sysfs syscall support" if EXPERT
	default y
	---help---
	  sys_sysfs is an obsolete system call no longer supported in libc.
	  Note that disabling this option is more secure but might break
	  compatibility with some systems.

	  If unsure say Y here.

1381
config SYSCTL_SYSCALL
1382
	bool "Sysctl syscall support" if EXPERT
1383
	depends on PROC_SYSCTL
1384
	default n
1385
	select SYSCTL
1386
	---help---
1387
1388
1389
1390
	  sys_sysctl uses binary paths that have been found challenging
	  to properly maintain and use.  The interface in /proc/sys
	  using paths with ascii names is now the primary path to this
	  information.
1391

1392
1393
1394
	  Almost nothing using the binary sysctl interface so if you are
	  trying to save some space it is probably safe to disable this,
	  making your kernel marginally smaller.
1395

1396
	  If unsure say N here.
1397

Linus Torvalds's avatar
Linus Torvalds committed
1398
config KALLSYMS
1399
	 bool "Load all symbols for debugging/ksymoops" if EXPERT
Linus Torvalds's avatar
Linus Torvalds committed
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
	 default y
	 help
	   Say Y here to let the kernel print out symbolic crash information and
	   symbolic stack backtraces. This increases the size of the kernel
	   somewhat, as all symbols have to be loaded into the kernel image.

config KALLSYMS_ALL
	bool "Include all symbols in kallsyms"
	depends on DEBUG_KERNEL && KALLSYMS
	help
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
	   Normally kallsyms only contains the symbols of functions for nicer
	   OOPS messages and backtraces (i.e., symbols from the text and inittext
	   sections). This is sufficient for most cases. And only in very rare
	   cases (e.g., when a debugger is used) all symbols are required (e.g.,
	   names of variables from the data sections, etc).

	   This option makes sure that all symbols are loaded into the kernel
	   image (i.e., symbols from all sections) in cost of increased kernel
	   size (depending on the kernel configuration, it may be 300KiB or
	   something like this).

	   Say N unless you really need all symbols.
1422
1423
1424

config PRINTK
	default y
1425
	bool "Enable support for printk" if EXPERT
1426
	select IRQ_WORK
1427
1428
1429
1430
1431
1432
1433
	help
	  This option enables normal printk support. Removing it
	  eliminates most of the message strings from the kernel image
	  and makes the kernel more or less silent. As this makes it
	  very difficult to diagnose system problems, saying N here is
	  strongly discouraged.

Matt Mackall's avatar
Matt Mackall committed
1434
config BUG
1435
	bool "BUG() support" if EXPERT
Matt Mackall's avatar
Matt Mackall committed
1436
1437
1438
1439
1440
1441
1442
1443
	default y
	help
          Disabling this option eliminates support for BUG and WARN, reducing
          the size of your kernel image and potentially quietly ignoring
          numerous fatal conditions. You should only consider disabling this
          option for embedded systems with no facilities for reporting errors.
          Just say Y.

1444
config ELF_CORE
1445
	depends on COREDUMP
1446
	default y
1447
	bool "Enable ELF core dumps" if EXPERT
1448
1449
1450
	help
	  Enable support for generating core dumps. Disabling saves about 4k.

1451

Stas Sergeev's avatar
Stas Sergeev committed
1452
config PCSPKR_PLATFORM
1453
	bool "Enable PC-Speaker support" if EXPERT
1454
	depends on HAVE_PCSPKR_PLATFORM
1455
	select I8253_LOCK
Stas Sergeev's avatar
Stas Sergeev committed
1456
1457
1458
1459
1460
	default y
	help
          This option allows to disable the internal PC-Speaker
          support, saving some memory.

Linus Torvalds's avatar
Linus Torvalds committed
1461
1462
config BASE_FULL
	default y
1463
	bool "Enable full-sized data structures for core" if EXPERT
Linus Torvalds's avatar
Linus Torvalds committed
1464
1465
1466
1467
1468
1469
	help
	  Disabling this option reduces the size of miscellaneous core
	  kernel data structures. This saves memory on small machines,
	  but may reduce performance.

config FUTEX
1470
	bool "Enable futex support" if EXPERT
Linus Torvalds's avatar
Linus Torvalds committed
1471
	default y
Ingo Molnar's avatar
Ingo Molnar committed
1472
	select RT_MUTEXES
Linus Torvalds's avatar
Linus Torvalds committed
1473
1474
1475
1476
1477
	help
	  Disabling this option will cause the kernel to be built without
	  support for "fast userspace mutexes".  The resulting kernel may not
	  run glibc-based applications correctly.

1478
1479
config HAVE_FUTEX_CMPXCHG
	bool
1480
	depends on FUTEX
1481
1482
1483
1484
1485
	help
	  Architectures should select this if futex_atomic_cmpxchg_inatomic()
	  is implemented and always working. This removes a couple of runtime
	  checks.

Linus Torvalds's avatar
Linus Torvalds committed
1486
config EPOLL
1487
	bool "Enable eventpoll support" if EXPERT
Linus Torvalds's avatar
Linus Torvalds committed
1488
	default y
1489
	select ANON_INODES
Linus Torvalds's avatar
Linus Torvalds committed
1490
1491
1492
1493
	help
	  Disabling this option will cause the kernel to be built without
	  support for epoll family of system calls.

1494
config SIGNALFD
1495
	bool "Enable signalfd() system call" if EXPERT
Adrian Bunk's avatar