Kconfig 60.9 KB
Newer Older
R
Roman Zippel 已提交
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"
L
Linus Torvalds 已提交
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
L
Linus Torvalds 已提交
43
	help
44 45
	  Maximum of each of the number of arguments and environment
	  variables passed to init from the kernel command line.
L
Linus Torvalds 已提交
46 47


R
Roland McGrath 已提交
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.

L
Linus Torvalds 已提交
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
S
Stephan Sperber 已提交
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.

L
Linus Torvalds 已提交
211 212
config SWAP
	bool "Support for paging of anonymous memory (swap)"
213
	depends on MMU && BLOCK
L
Linus Torvalds 已提交
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
L
Linus Torvalds 已提交
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

L
Linus Torvalds 已提交
242 243
config POSIX_MQUEUE
	bool "POSIX Message Queues"
244
	depends on NET
L
Linus Torvalds 已提交
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.
L
Linus Torvalds 已提交
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 271 272 273
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
	  to directly read from or write to to another process's address space.
	  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

L
Linus Torvalds 已提交
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/>.
L
Linus Torvalds 已提交
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"
T
Thomas Gleixner 已提交
463

M
Mike Travis 已提交
464 465 466 467
menu "RCU Subsystem"

choice
	prompt "RCU Implementation"
P
Paul E. McKenney 已提交
468
	default TREE_RCU
M
Mike Travis 已提交
469 470 471

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

480
config TREE_PREEMPT_RCU
P
Paul E. McKenney 已提交
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.

M
Mike Travis 已提交
502 503
endchoice

P
Paul E. McKenney 已提交
504
config PREEMPT_RCU
P
Paul E. McKenney 已提交
505
	def_bool TREE_PREEMPT_RCU
P
Paul E. McKenney 已提交
506 507
	help
	  This option enables preemptible-RCU code that is common between
508
	  TREE_PREEMPT_RCU and, in the old days, TINY_PREEMPT_RCU.
P
Paul E. McKenney 已提交
509

510 511 512 513 514 515 516 517
config RCU_STALL_COMMON
	def_bool ( TREE_RCU || TREE_PREEMPT_RCU || RCU_TRACE )
	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.

518 519 520
config CONTEXT_TRACKING
       bool

521 522
config RCU_USER_QS
	bool "Consider userspace as in RCU extended quiescent state"
523 524
	depends on HAVE_CONTEXT_TRACKING && SMP
	select CONTEXT_TRACKING
525 526 527 528 529
	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
530
	  try to keep the timer tick on for RCU.
531

532
	  Unless you want to hack and help the development of the full
533
	  dynticks mode, you shouldn't enable this option.  It also
534
	  adds unnecessary overhead.
535 536 537

	  If unsure say N

538 539 540
config CONTEXT_TRACKING_FORCE
	bool "Force context tracking"
	depends on CONTEXT_TRACKING
541
	default y if !NO_HZ_FULL
542
	help
543 544 545 546 547 548 549 550 551 552 553 554 555 556 557
	  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.

558
	  Say Y only if you're working on the development of an
559 560 561 562 563
	  architecture backend for the context tracking.

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

564

M
Mike Travis 已提交
565 566 567 568
config RCU_FANOUT
	int "Tree-based hierarchical RCU fanout value"
	range 2 64 if 64BIT
	range 2 32 if !64BIT
569
	depends on TREE_RCU || TREE_PREEMPT_RCU
M
Mike Travis 已提交
570 571 572 573 574
	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
575 576 577 578 579 580
	  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.
M
Mike Travis 已提交
581 582 583 584

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

585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611
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
	depends on TREE_RCU || TREE_PREEMPT_RCU
	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.

M
Mike Travis 已提交
612 613
config RCU_FANOUT_EXACT
	bool "Disable tree-based hierarchical RCU auto-balancing"
614
	depends on TREE_RCU || TREE_PREEMPT_RCU
M
Mike Travis 已提交
615 616 617 618 619 620 621 622 623 624 625
	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.

626 627
config RCU_FAST_NO_HZ
	bool "Accelerate last non-dyntick-idle CPU's grace periods"
628
	depends on NO_HZ_COMMON && SMP
629 630
	default n
	help
631 632 633 634 635 636 637
	  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().
638

639 640
	  Say Y if energy efficiency is critically important, and you
	  	don't care about increased grace-period durations.
641 642 643

	  Say N if you are unsure.

M
Mike Travis 已提交
644
config TREE_RCU_TRACE
645
	def_bool RCU_TRACE && ( TREE_RCU || TREE_PREEMPT_RCU )
M
Mike Travis 已提交
646 647
	select DEBUG_FS
	help
648 649 650
	  This option provides tracing for the TREE_RCU and
	  TREE_PREEMPT_RCU implementations, permitting Makefile to
	  trivially select kernel/rcutree_trace.c.
M
Mike Travis 已提交
651

652 653
config RCU_BOOST
	bool "Enable RCU priority boosting"
654
	depends on RT_MUTEXES && PREEMPT_RCU
655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670
	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.

config RCU_BOOST_PRIO
	int "Real-time priority to boost RCU readers to"
	range 1 99
	depends on RCU_BOOST
	default 1
	help
671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689
	  This option specifies the real-time priority to which long-term
	  preempted RCU readers are to be boosted.  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_BOOST_PRIO to a priority higher then the highest-priority
	  real-time CPU-bound thread.  The default RCU_BOOST_PRIO value
	  of 1 is appropriate in the common case, which is real-time
	  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
	  that CPU.  In this case, you should set RCU_BOOST_PRIO to
	  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
	  the CPU time on a given CPU, then RCU_BOOST_PRIO should be
	  set to priority 6 or higher.
690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705

	  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.

P
Paul E. McKenney 已提交
706
config RCU_NOCB_CPU
707
	bool "Offload RCU callback processing from boot-selected CPUs"
P
Paul E. McKenney 已提交
708 709 710 711 712 713 714 715 716 717
	depends on TREE_RCU || TREE_PREEMPT_RCU
	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.
718 719 720 721 722 723 724
	  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.
P
Paul E. McKenney 已提交
725

726
	  Say Y here if you want to help to debug reduced OS jitter.
P
Paul E. McKenney 已提交
727 728
	  Say N here if you are unsure.

729 730 731 732
choice
	prompt "Build-forced no-CBs CPUs"
	default RCU_NOCB_CPU_NONE
	help
733 734 735 736
	  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.
737 738 739

config RCU_NOCB_CPU_NONE
	bool "No build_forced no-CBs CPUs"
740
	depends on RCU_NOCB_CPU && !NO_HZ_FULL_ALL
741 742 743
	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
744 745 746 747 748 749 750
	  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.
751 752 753

config RCU_NOCB_CPU_ZERO
	bool "CPU 0 is a build_forced no-CBs CPU"
754
	depends on RCU_NOCB_CPU && !NO_HZ_FULL_ALL
755
	help
756 757 758 759 760 761
	  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.
762 763

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

config RCU_NOCB_CPU_ALL
	bool "All CPUs are build_forced no-CBs CPUs"
	depends on RCU_NOCB_CPU
	help
	  This option forces all CPUs to be no-CBs CPUs.  The rcu_nocbs=
772 773 774 775 776 777
	  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.
778 779 780 781 782 783

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

endchoice

M
Mike Travis 已提交
784 785
endmenu # "RCU Subsystem"

L
Linus Torvalds 已提交
786
config IKCONFIG
787
	tristate "Kernel .config support"
L
Linus Torvalds 已提交
788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804
	---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.

805 806 807
config LOG_BUF_SHIFT
	int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
	range 12 21
A
Adrian Bunk 已提交
808
	default 17
809 810
	help
	  Select kernel log buffer size as a power of 2.
A
Adrian Bunk 已提交
811 812 813 814 815
	  Examples:
	  	     17 => 128 KB
		     16 => 64 KB
	             15 => 32 KB
	             14 => 16 KB
816 817 818
		     13 =>  8 KB
		     12 =>  4 KB

819 820 821 822 823 824
#
# Architectures with an unreliable sched_clock() should select this:
#
config HAVE_UNSTABLE_SCHED_CLOCK
	bool

825 826 827
config GENERIC_SCHED_CLOCK
	bool

828 829 830 831 832 833 834
#
# For architectures that want to enable the support for NUMA-affine scheduler
# balancing logic:
#
config ARCH_SUPPORTS_NUMA_BALANCING
	bool

P
Peter Zijlstra 已提交
835 836 837 838 839 840
#
# For architectures that know their GCC __int128 support is sound
#
config ARCH_SUPPORTS_INT128
	bool

841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857
# 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

#
# For architectures that are willing to define _PAGE_NUMA as _PAGE_PROTNONE
config ARCH_WANTS_PROT_NUMA_PROT_NONE
	bool

config ARCH_USES_NUMA_PROT_NONE
	bool
	default y
	depends on ARCH_WANTS_PROT_NUMA_PROT_NONE
	depends on NUMA_BALANCING

858 859 860 861 862
config NUMA_BALANCING_DEFAULT_ENABLED
	bool "Automatically enable NUMA aware memory/task placement"
	default y
	depends on NUMA_BALANCING
	help
863
	  If set, automatic NUMA balancing will be enabled if running on a NUMA
864 865
	  machine.

866 867 868 869 870 871 872 873
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
874
	  it has references to the node the task is running on.
875 876 877

	  This system will be inactive on UMA systems.

L
Li Zefan 已提交
878 879
menuconfig CGROUPS
	boolean "Control Group support"
T
Tejun Heo 已提交
880
	select KERNFS
881
	help
L
Li Zefan 已提交
882
	  This option adds support for grouping sets of processes together, for
883 884 885 886
	  use with process control subsystems such as Cpusets, CFS, memory
	  controls or device isolation.
	  See
		- Documentation/scheduler/sched-design-CFS.txt	(CFS)
L
Li Zefan 已提交
887 888
		- Documentation/cgroups/ (features for grouping, isolation
					  and resource control)
889 890 891

	  Say N if unsure.

L
Li Zefan 已提交
892 893
if CGROUPS

894 895 896 897 898 899
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
L
Li Zefan 已提交
900
	  framework.
901

L
Li Zefan 已提交
902
	  Say N if unsure.
903 904

config CGROUP_FREEZER
L
Li Zefan 已提交
905 906 907
	bool "Freezer cgroup subsystem"
	help
	  Provides a way to freeze and unfreeze all tasks in a
908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925
	  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.

L
Li Zefan 已提交
926 927 928 929 930
config PROC_PID_CPUSET
	bool "Include legacy /proc/<pid>/cpuset file"
	depends on CPUSETS
	default y

931 932 933 934
config CGROUP_CPUACCT
	bool "Simple CPU accounting cgroup subsystem"
	help
	  Provides a simple Resource Controller for monitoring the
L
Li Zefan 已提交
935
	  total CPU consumed by the tasks in a cgroup.
936

937 938 939 940
config RESOURCE_COUNTERS
	bool "Resource counters"
	help
	  This option enables controller independent resource accounting
L
Li Zefan 已提交
941
	  infrastructure that works with cgroups.
942

A
Andrew Morton 已提交
943
config MEMCG
944
	bool "Memory Resource Controller for Control Groups"
945
	depends on RESOURCE_COUNTERS
946
	select EVENTFD
947
	help
948
	  Provides a memory resource controller that manages both anonymous
949
	  memory and page cache. (See Documentation/cgroups/memory.txt)
950 951

	  Note that setting this option increases fixed memory overhead
952
	  associated with each page of memory in the system. By this,
S
Sergey Dyasly 已提交
953
	  8(16)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
954 955
	  usage tracking struct at boot. Total amount of this is printed out
	  at boot.
956 957

	  Only enable when you're ok with these trade offs and really
958 959 960
	  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.
L
Li Zefan 已提交
961
	  (and lose benefits of memory resource controller)
962

A
Andrew Morton 已提交
963
config MEMCG_SWAP
964
	bool "Memory Resource Controller Swap Extension"
A
Andrew Morton 已提交
965
	depends on MEMCG && SWAP
966 967 968 969 970 971 972 973 974 975 976
	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,
977
	  if boot option "swapaccount=0" is set, swap will not be accounted.
978 979
	  Now, memory usage of swap_cgroup is 2 bytes per entry. If swap page
	  size is 4096bytes, 512k per 1Gbytes of swap.
A
Andrew Morton 已提交
980
config MEMCG_SWAP_ENABLED
981
	bool "Memory Resource Controller Swap Extension enabled by default"
A
Andrew Morton 已提交
982
	depends on MEMCG_SWAP
983 984 985 986
	default y
	help
	  Memory Resource Controller Swap Extension comes with its price in
	  a bigger memory consumption. General purpose distribution kernels
J
Jim Cromie 已提交
987
	  which want to enable the feature but keep it disabled by default
988
	  and let the user enable it by swapaccount=1 boot command line
989 990 991
	  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
992
	  then swapaccount=0 does the trick).
A
Andrew Morton 已提交
993
config MEMCG_KMEM
994 995
	bool "Memory Resource Controller Kernel Memory accounting"
	depends on MEMCG
996
	depends on SLUB || SLAB
997 998 999 1000 1001 1002 1003
	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.
1004

1005 1006 1007 1008 1009 1010
	  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.

1011 1012
config CGROUP_HUGETLB
	bool "HugeTLB Resource Controller for Control Groups"
1013
	depends on RESOURCE_COUNTERS && HUGETLB_PAGE
1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025
	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.

S
Stephane Eranian 已提交
1026 1027 1028 1029 1030
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
1031
	  threads which belong to the cgroup specified and run on the
S
Stephane Eranian 已提交
1032 1033 1034 1035
	  designated cpu.

	  Say N if unsure.

D
Dhaval Giani 已提交
1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049
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

1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060
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.

D
Dhaval Giani 已提交
1061 1062 1063 1064 1065 1066
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
1067
	  to task groups. If enabled, it will also make it impossible to
D
Dhaval Giani 已提交
1068 1069 1070 1071 1072 1073
	  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

1074
config BLK_CGROUP
T
Tejun Heo 已提交
1075
	bool "Block IO controller"
1076
	depends on BLOCK
1077 1078 1079 1080 1081 1082 1083 1084
	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)
1085 1086
	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.
1087 1088

	This option only enables generic Block IO controller infrastructure.
1089
	One needs to also enable actual IO controlling logic/policy. For
M
Michael Witten 已提交
1090 1091
	enabling proportional weight division of disk bandwidth in CFQ, set
	CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
1092
	CONFIG_BLK_DEV_THROTTLING=y.
1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103

	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.

L
Li Zefan 已提交
1104
endif # CGROUPS
1105

1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116
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.

1117
menuconfig NAMESPACES
1118 1119
	bool "Namespaces support" if EXPERT
	default !EXPERT
1120 1121 1122 1123 1124 1125
	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.

1126 1127
if NAMESPACES

1128 1129
config UTS_NS
	bool "UTS namespace"
1130
	default y
1131 1132 1133 1134
	help
	  In this namespace tasks see different info provided with the
	  uname() system call

1135 1136
config IPC_NS
	bool "IPC namespace"
1137
	depends on (SYSVIPC || POSIX_MQUEUE)
1138
	default y
1139 1140
	help
	  In this namespace tasks work with IPC ids which correspond to
1141
	  different IPC objects in different namespaces.
1142

1143
config USER_NS
1144
	bool "User namespace"
1145
	default n
1146 1147 1148
	help
	  This allows containers, i.e. vservers, to use user namespaces
	  to provide different user info for different servers.
1149 1150 1151 1152 1153 1154 1155

	  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.

1156 1157
	  If unsure, say N.

1158
config PID_NS
1159
	bool "PID Namespaces"
1160
	default y
1161
	help
1162
	  Support process id namespaces.  This allows having multiple
1163
	  processes with the same pid as long as they are in different
1164 1165
	  pid namespaces.  This is a building block of containers.

1166 1167
config NET_NS
	bool "Network namespace"
1168
	depends on NET
1169
	default y
1170 1171 1172 1173
	help
	  Allow user space to create what appear to be multiple instances
	  of the network stack.

1174 1175
endif # NAMESPACES

1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187
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.

1188
config SYSFS_DEPRECATED
1189
	bool "Enable deprecated sysfs features to support old userspace tools"
1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211
	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
1212
	bool "Enable deprecated sysfs features by default"
1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236
	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.

1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252
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.

1253 1254
if BLK_DEV_INITRD

1255 1256
source "usr/Kconfig"

1257 1258
endif

1259
config CC_OPTIMIZE_FOR_SIZE
1260
	bool "Optimize for size"
1261 1262 1263 1264
	help
	  Enabling this option will pass "-Os" instead of "-O2" to gcc
	  resulting in a smaller kernel.

1265
	  If unsure, say N.
1266

R
Randy Dunlap 已提交
1267 1268 1269
config SYSCTL
	bool

R
Randy Dunlap 已提交
1270 1271 1272
config ANON_INODES
	bool

1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298
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

1299 1300
menuconfig EXPERT
	bool "Configure standard kernel features (expert users)"
1301 1302
	# Unhide debug options, to make the on-by-default options visible
	select DEBUG_KERNEL
L
Linus Torvalds 已提交
1303 1304 1305 1306 1307 1308
	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.

1309
config UID16
1310
	bool "Enable 16-bit UID system calls" if EXPERT
1311
	depends on HAVE_UID16
1312 1313 1314 1315
	default y
	help
	  This enables the legacy 16-bit UID syscall wrappers.

1316 1317 1318 1319 1320 1321 1322 1323 1324 1325
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.

1326 1327 1328 1329 1330 1331 1332 1333 1334 1335
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.

1336
config SYSCTL_SYSCALL
1337
	bool "Sysctl syscall support" if EXPERT
1338
	depends on PROC_SYSCTL
1339
	default n
1340
	select SYSCTL
1341
	---help---
1342 1343 1344 1345
	  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.
1346

1347 1348 1349
	  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.
1350

1351
	  If unsure say N here.
1352

L
Linus Torvalds 已提交
1353
config KALLSYMS
1354
	 bool "Load all symbols for debugging/ksymoops" if EXPERT
L
Linus Torvalds 已提交
1355 1356 1357 1358 1359 1360 1361 1362 1363 1364
	 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
1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376
	   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.
M
Matt Mackall 已提交
1377 1378 1379

config PRINTK
	default y
1380
	bool "Enable support for printk" if EXPERT
1381
	select IRQ_WORK
M
Matt Mackall 已提交
1382 1383 1384 1385 1386 1387 1388
	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.

M
Matt Mackall 已提交
1389
config BUG
1390
	bool "BUG() support" if EXPERT
M
Matt Mackall 已提交
1391 1392 1393 1394 1395 1396 1397 1398
	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.

1399
config ELF_CORE
1400
	depends on COREDUMP
1401
	default y
1402
	bool "Enable ELF core dumps" if EXPERT
1403 1404 1405
	help
	  Enable support for generating core dumps. Disabling saves about 4k.

1406

S
Stas Sergeev 已提交
1407
config PCSPKR_PLATFORM
1408
	bool "Enable PC-Speaker support" if EXPERT
1409
	depends on HAVE_PCSPKR_PLATFORM
1410
	select I8253_LOCK
S
Stas Sergeev 已提交
1411 1412 1413 1414 1415
	default y
	help
          This option allows to disable the internal PC-Speaker
          support, saving some memory.

L
Linus Torvalds 已提交
1416 1417
config BASE_FULL
	default y
1418
	bool "Enable full-sized data structures for core" if EXPERT
L
Linus Torvalds 已提交
1419 1420 1421 1422 1423 1424
	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
1425
	bool "Enable futex support" if EXPERT
L
Linus Torvalds 已提交
1426
	default y
I
Ingo Molnar 已提交
1427
	select RT_MUTEXES
L
Linus Torvalds 已提交
1428 1429 1430 1431 1432
	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.

1433 1434 1435 1436 1437 1438 1439
config HAVE_FUTEX_CMPXCHG
	bool
	help
	  Architectures should select this if futex_atomic_cmpxchg_inatomic()
	  is implemented and always working. This removes a couple of runtime
	  checks.

L
Linus Torvalds 已提交
1440
config EPOLL
1441
	bool "Enable eventpoll support" if EXPERT
L
Linus Torvalds 已提交
1442
	default y
1443
	select ANON_INODES
L
Linus Torvalds 已提交
1444 1445 1446 1447
	help
	  Disabling this option will cause the kernel to be built without
	  support for epoll family of system calls.

1448
config SIGNALFD
1449
	bool "Enable signalfd() system call" if EXPERT
1450
	select ANON_INODES
1451 1452 1453 1454 1455 1456 1457
	default y
	help
	  Enable the signalfd() system call that allows to receive signals
	  on a file descriptor.

	  If unsure, say Y.

1458
config TIMERFD
1459
	bool "Enable timerfd() system call" if EXPERT
1460
	select ANON_INODES
1461 1462 1463 1464 1465 1466 1467
	default y
	help
	  Enable the timerfd() system call that allows to receive timer
	  events on a file descriptor.

	  If unsure, say Y.

1468
config EVENTFD
1469
	bool "Enable eventfd() system call" if EXPERT
1470
	select ANON_INODES
1471 1472 1473 1474 1475 1476 1477
	default y
	help
	  Enable the eventfd() system call that allows to receive both
	  kernel notification (ie. KAIO) or userspace notifications.

	  If unsure, say Y.

L
Linus Torvalds 已提交
1478
config SHMEM
1479
	bool "Use full shmem filesystem" if EXPERT
L
Linus Torvalds 已提交
1480 1481 1482 1483 1484 1485 1486 1487 1488
	default y
	depends on MMU
	help
	  The shmem is an internal filesystem used to manage shared memory.
	  It is backed by swap and manages resource limits. It is also exported
	  to userspace as tmpfs if TMPFS is enabled. Disabling this
	  option replaces shmem and tmpfs with the much simpler ramfs code,
	  which may be appropriate on small systems without swap.

T
Thomas Petazzoni 已提交
1489
config AIO
1490
	bool "Enable AIO support" if EXPERT
T
Thomas Petazzoni 已提交
1491 1492 1493
	default y
	help
	  This option enables POSIX asynchronous I/O which may by used
1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504
	  by some high performance threaded applications. Disabling
	  this option saves about 7k.

config PCI_QUIRKS
	default y
	bool "Enable PCI quirk workarounds" if EXPERT
	depends on PCI
	help
	  This enables workarounds for various PCI chipset
	  bugs/quirks. Disable this only if your target machine is
	  unaffected by PCI quirks.
T
Thomas Petazzoni 已提交
1505

1506 1507
config EMBEDDED
	bool "Embedded system"
1508
	option allnoconfig_y
1509 1510 1511 1512 1513 1514
	select EXPERT
	help
	  This option should be enabled if compiling the kernel for
	  an embedded system so certain expert options are available
	  for configuration.

1515
config HAVE_PERF_EVENTS
T
Thomas Gleixner 已提交
1516
	bool
1517 1518
	help
	  See tools/perf/design.txt for details.
T
Thomas Gleixner 已提交
1519

1520 1521 1522 1523 1524
config PERF_USE_VMALLOC
	bool
	help
	  See tools/perf/design.txt for details

I
Ingo Molnar 已提交
1525
menu "Kernel Performance Events And Counters"
T
Thomas Gleixner 已提交
1526

1527
config PERF_EVENTS
I
Ingo Molnar 已提交
1528
	bool "Kernel performance events and counters"
1529
	default y if PROFILING
1530
	depends on HAVE_PERF_EVENTS
I
Ingo Molnar 已提交
1531
	select ANON_INODES
1532
	select IRQ_WORK
T
Thomas Gleixner 已提交
1533
	help
I
Ingo Molnar 已提交
1534 1535
	  Enable kernel support for various performance events provided
	  by software and hardware.
T
Thomas Gleixner 已提交
1536

1537
	  Software events are supported either built-in or via the
I
Ingo Molnar 已提交
1538
	  use of generic tracepoints.
T
Thomas Gleixner 已提交
1539

I
Ingo Molnar 已提交
1540 1541
	  Most modern CPUs support performance events via performance
	  counter registers. These registers count the number of certain
T
Thomas Gleixner 已提交
1542 1543 1544 1545 1546 1547
	  types of hw events: such as instructions executed, cachemisses
	  suffered, or branches mis-predicted - without slowing down the
	  kernel or applications. These registers can also trigger interrupts
	  when a threshold number of events have passed - and can thus be
	  used to profile the code that runs on that CPU.

I
Ingo Molnar 已提交
1548
	  The Linux Performance Event subsystem provides an abstraction of
1549
	  these software and hardware event capabilities, available via a
I
Ingo Molnar 已提交
1550
	  system call and used by the "perf" utility in tools/perf/. It
T
Thomas Gleixner 已提交
1551 1552 1553 1554 1555
	  provides per task and per CPU counters, and it provides event
	  capabilities on top of those.

	  Say Y if unsure.

1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568
config DEBUG_PERF_USE_VMALLOC
	default n
	bool "Debug: use vmalloc to back perf mmap() buffers"
	depends on PERF_EVENTS && DEBUG_KERNEL
	select PERF_USE_VMALLOC
	help
	 Use vmalloc memory to back perf mmap() buffers.

	 Mostly useful for debugging the vmalloc code on platforms
	 that don't require it.

	 Say N if unsure.

T
Thomas Gleixner 已提交
1569 1570
endmenu

1571 1572
config VM_EVENT_COUNTERS
	default y
1573
	bool "Enable VM event counters for /proc/vmstat" if EXPERT
1574
	help
1575 1576
	  VM event counters are needed for event counts to be shown.
	  This option allows the disabling of the VM event counters
1577
	  on EXPERT systems.  /proc/vmstat will only show page counts
1578
	  if VM event counters are disabled.
1579

C
Christoph Lameter 已提交
1580 1581
config SLUB_DEBUG
	default y
1582
	bool "Enable SLUB debugging support" if EXPERT
C
Christoph Lameter 已提交
1583
	depends on SLUB && SYSFS
C
Christoph Lameter 已提交
1584 1585 1586 1587 1588 1589
	help
	  SLUB has extensive debug support features. Disabling these can
	  result in significant savings in code size. This also disables
	  SLUB sysfs support. /sys/slab will not exist and there will be
	  no support for cache validation etc.

R
Randy Dunlap 已提交
1590 1591 1592 1593 1594 1595 1596
config COMPAT_BRK
	bool "Disable heap randomization"
	default y
	help
	  Randomizing heap placement makes heap exploits harder, but it
	  also breaks ancient binaries (including anything libc5 based).
	  This option changes the bootup default to heap randomization
1597
	  disabled, and can be overridden at runtime by setting
R
Randy Dunlap 已提交
1598 1599 1600 1601
	  /proc/sys/kernel/randomize_va_space to 2.

	  On non-ancient distros (post-2000 ones) N is usually a safe choice.

C
Christoph Lameter 已提交
1602 1603
choice
	prompt "Choose SLAB allocator"
1604
	default SLUB
C
Christoph Lameter 已提交
1605 1606 1607 1608 1609 1610 1611
	help
	   This option allows to select a slab allocator.

config SLAB
	bool "SLAB"
	help
	  The regular slab allocator that is established and known to work
1612
	  well in all environments. It organizes cache hot objects in
1613
	  per cpu and per node queues.
C
Christoph Lameter 已提交
1614 1615 1616 1617 1618 1619 1620 1621

config SLUB
	bool "SLUB (Unqueued Allocator)"
	help
	   SLUB is a slab allocator that minimizes cache line usage
	   instead of managing queues of cached objects (SLAB approach).
	   Per cpu caching is realized using slabs of objects instead
	   of queues of objects. SLUB can use memory efficiently
1622 1623
	   and has enhanced diagnostics. SLUB is the default choice for
	   a slab allocator.
C
Christoph Lameter 已提交
1624 1625

config SLOB
1626
	depends on EXPERT
C
Christoph Lameter 已提交
1627 1628
	bool "SLOB (Simple Allocator)"
	help
M
Matt Mackall 已提交
1629 1630 1631
	   SLOB replaces the stock allocator with a drastically simpler
	   allocator. SLOB is generally more space efficient but
	   does not perform as well on large systems.
C
Christoph Lameter 已提交
1632 1633 1634

endchoice

1635 1636
config SLUB_CPU_PARTIAL
	default y
1637
	depends on SLUB && SMP
1638 1639 1640 1641 1642 1643 1644 1645
	bool "SLUB per cpu partial cache"
	help
	  Per cpu partial caches accellerate objects allocation and freeing
	  that is local to a processor at the price of more indeterminism
	  in the latency of the free. On overflow these caches will be cleared
	  which requires the taking of locks that may cause latency spikes.
	  Typically one would choose no for a realtime system.

1646 1647
config MMAP_ALLOW_UNINITIALIZED
	bool "Allow mmapped anonymous memory to be uninitialized"
1648
	depends on EXPERT && !MMU
1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667
	default n
	help
	  Normally, and according to the Linux spec, anonymous memory obtained
	  from mmap() has it's contents cleared before it is passed to
	  userspace.  Enabling this config option allows you to request that
	  mmap() skip that if it is given an MAP_UNINITIALIZED flag, thus
	  providing a huge performance boost.  If this option is not enabled,
	  then the flag will be ignored.

	  This is taken advantage of by uClibc's malloc(), and also by
	  ELF-FDPIC binfmt's brk and stack allocator.

	  Because of the obvious security issues, this option should only be
	  enabled on embedded devices where you control what is run in
	  userspace.  Since that isn't generally a problem on no-MMU systems,
	  it is normally safe to say Y here.

	  See Documentation/nommu-mmap.txt for more information.

1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679
config SYSTEM_TRUSTED_KEYRING
	bool "Provide system-wide ring of trusted keys"
	depends on KEYS
	help
	  Provide a system keyring to which trusted keys can be added.  Keys in
	  the keyring are considered to be trusted.  Keys may be added at will
	  by the kernel from compiled-in data and from hardware key stores, but
	  userspace may only add extra keys if those keys can be verified by
	  keys already in the keyring.

	  Keys in this keyring are used by module signature checking.

1680
config PROFILING
1681
	bool "Profiling support"
1682 1683 1684 1685
	help
	  Say Y here to enable the extended profiling support mechanisms used
	  by profilers such as OProfile.

1686 1687 1688 1689
#
# Place an empty function call at each tracepoint site. Can be
# dynamically changed for a probe function.
#
M
Mathieu Desnoyers 已提交
1690
config TRACEPOINTS
1691
	bool
M
Mathieu Desnoyers 已提交
1692

M
Mathieu Desnoyers 已提交
1693 1694
source "arch/Kconfig"

L
Linus Torvalds 已提交
1695 1696
endmenu		# General setup

1697 1698 1699 1700
config HAVE_GENERIC_DMA_COHERENT
	bool
	default n

1701 1702 1703
config SLABINFO
	bool
	depends on PROC_FS
1704
	depends on SLAB || SLUB_DEBUG
1705 1706
	default y

1707 1708 1709
config RT_MUTEXES
	boolean

L
Linus Torvalds 已提交
1710 1711 1712 1713 1714
config BASE_SMALL
	int
	default 0 if BASE_FULL
	default 1 if !BASE_FULL

1715
menuconfig MODULES
L
Linus Torvalds 已提交
1716
	bool "Enable loadable module support"
1717
	option modules
L
Linus Torvalds 已提交
1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735
	help
	  Kernel modules are small pieces of compiled code which can
	  be inserted in the running kernel, rather than being
	  permanently built into the kernel.  You use the "modprobe"
	  tool to add (and sometimes remove) them.  If you say Y here,
	  many parts of the kernel can be built as modules (by
	  answering M instead of Y where indicated): this is most
	  useful for infrequently used options which are not required
	  for booting.  For more information, see the man pages for
	  modprobe, lsmod, modinfo, insmod and rmmod.

	  If you say Y here, you will need to run "make
	  modules_install" to put the modules under /lib/modules/
	  where modprobe can find them (you may need to be root to do
	  this).

	  If unsure, say Y.

1736 1737
if MODULES

1738 1739 1740 1741
config MODULE_FORCE_LOAD
	bool "Forced module loading"
	default n
	help
1742 1743 1744
	  Allow loading of modules without version information (ie. modprobe
	  --force).  Forced module loading sets the 'F' (forced) taint flag and
	  is usually a really bad idea.
1745

L
Linus Torvalds 已提交
1746 1747 1748 1749 1750
config MODULE_UNLOAD
	bool "Module unloading"
	help
	  Without this option you will not be able to unload any
	  modules (note that some modules may not be unloadable
1751 1752
	  anyway), which makes your kernel smaller, faster
	  and simpler.  If unsure, say Y.
L
Linus Torvalds 已提交
1753 1754 1755

config MODULE_FORCE_UNLOAD
	bool "Forced module unloading"
1756
	depends on MODULE_UNLOAD
L
Linus Torvalds 已提交
1757 1758 1759 1760 1761 1762 1763 1764
	help
	  This option allows you to force a module to unload, even if the
	  kernel believes it is unsafe: the kernel will remove the module
	  without waiting for anyone to stop using it (using the -f option to
	  rmmod).  This is mainly for kernel developers and desperate users.
	  If unsure, say N.

config MODVERSIONS
1765
	bool "Module versioning support"
L
Linus Torvalds 已提交
1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784
	help
	  Usually, you have to use modules compiled with your kernel.
	  Saying Y here makes it sometimes possible to use modules
	  compiled for different kernels, by adding enough information
	  to the modules to (hopefully) spot any changes which would
	  make them incompatible with the kernel you are running.  If
	  unsure, say N.

config MODULE_SRCVERSION_ALL
	bool "Source checksum for all modules"
	help
	  Modules which contain a MODULE_VERSION get an extra "srcversion"
	  field inserted into their modinfo section, which contains a
    	  sum of the source files which made it.  This helps maintainers
	  see exactly which source was used to build a module (since
	  others sometimes change the module source without updating
	  the version).  With this option, such a "srcversion" field
	  will be created for all modules.  If unsure, say N.

R
Rusty Russell 已提交
1785 1786 1787
config MODULE_SIG
	bool "Module signature verification"
	depends on MODULES
1788
	select SYSTEM_TRUSTED_KEYRING
1789 1790 1791 1792 1793 1794 1795 1796
	select KEYS
	select CRYPTO
	select ASYMMETRIC_KEY_TYPE
	select ASYMMETRIC_PUBLIC_KEY_SUBTYPE
	select PUBLIC_KEY_ALGO_RSA
	select ASN1
	select OID_REGISTRY
	select X509_CERTIFICATE_PARSER
R
Rusty Russell 已提交
1797 1798 1799 1800 1801
	help
	  Check modules for valid signatures upon load: the signature
	  is simply appended to the module. For more information see
	  Documentation/module-signing.txt.

D
David Howells 已提交
1802 1803 1804 1805 1806
	  !!!WARNING!!!  If you enable this option, you MUST make sure that the
	  module DOES NOT get stripped after being signed.  This includes the
	  debuginfo strip done by some packagers (such as rpmbuild) and
	  inclusion into an initramfs that wants the module size reduced.

R
Rusty Russell 已提交
1807 1808 1809 1810 1811 1812
config MODULE_SIG_FORCE
	bool "Require modules to be validly signed"
	depends on MODULE_SIG
	help
	  Reject unsigned modules or signed modules for which we don't have a
	  key.  Without this, such modules will simply taint the kernel.
D
David Howells 已提交
1813

1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824
config MODULE_SIG_ALL
	bool "Automatically sign all modules"
	default y
	depends on MODULE_SIG
	help
	  Sign all modules during make modules_install. Without this option,
	  modules must be signed manually, using the scripts/sign-file tool.

comment "Do not forget to sign required modules with scripts/sign-file"
	depends on MODULE_SIG_FORCE && !MODULE_SIG_ALL

D
David Howells 已提交
1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856
choice
	prompt "Which hash algorithm should modules be signed with?"
	depends on MODULE_SIG
	help
	  This determines which sort of hashing algorithm will be used during
	  signature generation.  This algorithm _must_ be built into the kernel
	  directly so that signature verification can take place.  It is not
	  possible to load a signed module containing the algorithm to check
	  the signature on that module.

config MODULE_SIG_SHA1
	bool "Sign modules with SHA-1"
	select CRYPTO_SHA1

config MODULE_SIG_SHA224
	bool "Sign modules with SHA-224"
	select CRYPTO_SHA256

config MODULE_SIG_SHA256
	bool "Sign modules with SHA-256"
	select CRYPTO_SHA256

config MODULE_SIG_SHA384
	bool "Sign modules with SHA-384"
	select CRYPTO_SHA512

config MODULE_SIG_SHA512
	bool "Sign modules with SHA-512"
	select CRYPTO_SHA512

endchoice

1857 1858 1859 1860 1861 1862 1863 1864 1865
config MODULE_SIG_HASH
	string
	depends on MODULE_SIG
	default "sha1" if MODULE_SIG_SHA1
	default "sha224" if MODULE_SIG_SHA224
	default "sha256" if MODULE_SIG_SHA256
	default "sha384" if MODULE_SIG_SHA384
	default "sha512" if MODULE_SIG_SHA512

1866 1867
endif # MODULES

1868 1869 1870
config INIT_ALL_POSSIBLE
	bool
	help
1871 1872
	  Back when each arch used to define their own cpu_online_mask and
	  cpu_possible_mask, some of them chose to initialize cpu_possible_mask
1873 1874
	  with all 1s, and others with all 0s.  When they were centralised,
	  it was better to provide this option than to break all the archs
1875
	  and have several arch maintainers pursuing me down dark alleys.
1876

L
Linus Torvalds 已提交
1877 1878 1879 1880 1881 1882
config STOP_MACHINE
	bool
	default y
	depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
	help
	  Need stop_machine() primitive.
1883 1884

source "block/Kconfig"
1885 1886 1887

config PREEMPT_NOTIFIERS
	bool
P
Paul E. McKenney 已提交
1888

1889 1890 1891 1892
config PADATA
	depends on SMP
	bool

1893 1894 1895 1896 1897 1898
# Can be selected by architectures with broken toolchains
# that get confused by correct const<->read_only section
# mappings
config BROKEN_RODATA
	bool

1899 1900 1901 1902 1903 1904 1905 1906
config ASN1
	tristate
	help
	  Build a simple ASN.1 grammar compiler that produces a bytecode output
	  that can be interpreted by the ASN.1 stream decoder and used to
	  inform it as to what tags are to be expected in a stream and what
	  functions to call on what tags.

1907
source "kernel/Kconfig.locks"