Kconfig 66.7 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
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
config FHANDLE
A
Andi Kleen 已提交
275
	bool "open by fhandle syscalls" if EXPERT
276
	select EXPORTFS
A
Andi Kleen 已提交
277
	default y
278 279 280 281 282 283 284 285 286
	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.

287 288
config USELIB
	bool "uselib syscall"
289
	def_bool ALPHA || M68K || SPARC || X86_32 || IA32_EMULATION
290 291 292 293 294 295 296
	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.

297 298 299 300 301 302
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
303 304
	  logging of avc messages output).  System call auditing is included
	  on architectures which support it.
305

306 307 308
config HAVE_ARCH_AUDITSYSCALL
	bool

309
config AUDITSYSCALL
310
	def_bool y
311
	depends on AUDIT && HAVE_ARCH_AUDITSYSCALL
312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327

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"

328 329 330
config VIRT_CPU_ACCOUNTING
	bool

331 332 333
choice
	prompt "Cputime accounting"
	default TICK_CPU_ACCOUNTING if !PPC64
334
	default VIRT_CPU_ACCOUNTING_NATIVE if PPC64
335 336 337 338

# Kind of a stub config for the pure tick based cputime accounting
config TICK_CPU_ACCOUNTING
	bool "Simple tick based cputime accounting"
339
	depends on !S390 && !NO_HZ_FULL
340 341 342 343 344 345 346
	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.

347
config VIRT_CPU_ACCOUNTING_NATIVE
348
	bool "Deterministic task and CPU time accounting"
349
	depends on HAVE_VIRT_CPU_ACCOUNTING && !NO_HZ_FULL
350
	select VIRT_CPU_ACCOUNTING
351 352 353 354 355 356 357 358 359
	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.

360 361
config VIRT_CPU_ACCOUNTING_GEN
	bool "Full dynticks CPU time accounting"
362
	depends on HAVE_CONTEXT_TRACKING
363
	depends on HAVE_VIRT_CPU_ACCOUNTING_GEN
364 365 366 367 368 369 370 371 372 373 374 375 376 377
	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.

378 379
config IRQ_TIME_ACCOUNTING
	bool "Fine granularity task level IRQ time accounting"
380
	depends on HAVE_IRQ_TIME_ACCOUNTING && !NO_HZ_FULL
381 382 383 384 385 386 387 388 389 390
	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 已提交
391 392
config BSD_PROCESS_ACCT
	bool "BSD Process Accounting"
393
	depends on MULTIUSER
L
Linus Torvalds 已提交
394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414
	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
415
	  at <http://www.gnu.org/software/acct/>.
L
Linus Torvalds 已提交
416

417
config TASKSTATS
418
	bool "Export task/process statistics through netlink"
419
	depends on NET
420
	depends on MULTIUSER
421 422 423 424 425 426 427 428 429 430
	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.

431
config TASK_DELAY_ACCT
432
	bool "Enable per-task delay accounting"
433
	depends on TASKSTATS
434
	select SCHED_INFO
435 436 437 438 439 440 441 442
	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.

443
config TASK_XACCT
444
	bool "Enable extended accounting over taskstats"
445 446 447 448 449 450 451 452
	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
453
	bool "Enable per-task storage I/O accounting"
454 455 456 457 458 459 460
	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.

461
endmenu # "CPU/Task time and stats accounting"
T
Thomas Gleixner 已提交
462

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

config TREE_RCU
466 467
	bool
	default y if !PREEMPT && SMP
M
Mike Travis 已提交
468 469 470
	help
	  This option selects the RCU implementation that is
	  designed for very large SMP system with hundreds or
P
Paul E. McKenney 已提交
471 472
	  thousands of CPUs.  It also scales down nicely to
	  smaller systems.
M
Mike Travis 已提交
473

474
config PREEMPT_RCU
475 476
	bool
	default y if PREEMPT
477 478 479 480
	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
481 482
	  is also required.  It also scales down nicely to
	  smaller systems.
483

484 485
	  Select this option if you are unsure.

486
config TINY_RCU
487 488
	bool
	default y if !PREEMPT && !SMP
489 490 491 492 493 494
	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.

495 496 497 498 499 500 501 502 503 504 505 506 507 508 509
config RCU_EXPERT
	bool "Make expert-level adjustments to RCU configuration"
	default n
	help
	  This option needs to be enabled if you wish to make
	  expert-level adjustments to RCU configuration.  By default,
	  no such adjustments can be made, which has the often-beneficial
	  side-effect of preventing "make oldconfig" from asking you all
	  sorts of detailed questions about how you would like numerous
	  obscure RCU options to be set up.

	  Say Y if you need to make expert-level adjustments to RCU.

	  Say N if you are unsure.

510 511 512 513 514 515 516
config SRCU
	bool
	help
	  This option selects the sleepable version of RCU. This version
	  permits arbitrary sleeping or blocking within RCU read-side critical
	  sections.

P
Paul E. McKenney 已提交
517
config TASKS_RCU
518
	bool
P
Paul E. McKenney 已提交
519
	default n
520
	select SRCU
P
Paul E. McKenney 已提交
521 522 523 524 525
	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.

526
config RCU_STALL_COMMON
527
	def_bool ( TREE_RCU || PREEMPT_RCU || RCU_TRACE )
528 529 530 531 532 533
	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.

534 535 536 537 538 539
config CONTEXT_TRACKING
       bool

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

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

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

563

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

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

584 585
config RCU_FANOUT_LEAF
	int "Tree-based hierarchical RCU leaf-level fanout value"
586 587
	range 2 64 if 64BIT
	range 2 32 if !64BIT
588
	depends on (TREE_RCU || PREEMPT_RCU) && RCU_EXPERT
589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610
	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.

611 612
config RCU_FAST_NO_HZ
	bool "Accelerate last non-dyntick-idle CPU's grace periods"
613
	depends on NO_HZ_COMMON && SMP && RCU_EXPERT
614 615
	default n
	help
616 617 618 619 620 621 622
	  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().
623

624 625
	  Say Y if energy efficiency is critically important, and you
	  	don't care about increased grace-period durations.
626 627 628

	  Say N if you are unsure.

M
Mike Travis 已提交
629
config TREE_RCU_TRACE
630
	def_bool RCU_TRACE && ( TREE_RCU || PREEMPT_RCU )
M
Mike Travis 已提交
631 632
	select DEBUG_FS
	help
633
	  This option provides tracing for the TREE_RCU and
634
	  PREEMPT_RCU implementations, permitting Makefile to
635
	  trivially select kernel/rcutree_trace.c.
M
Mike Travis 已提交
636

637 638
config RCU_BOOST
	bool "Enable RCU priority boosting"
639
	depends on RT_MUTEXES && PREEMPT_RCU && RCU_EXPERT
640 641 642 643 644 645 646 647 648 649
	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.

650 651
config RCU_KTHREAD_PRIO
	int "Real-time priority to use for RCU worker threads"
652 653 654 655
	range 1 99 if RCU_BOOST
	range 0 99 if !RCU_BOOST
	default 1 if RCU_BOOST
	default 0 if !RCU_BOOST
656
	depends on RCU_EXPERT
657
	help
658 659 660 661 662 663 664 665
	  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
666 667 668 669 670
	  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
671
	  that CPU.  In this case, you should set RCU_KTHREAD_PRIO to
672 673 674 675
	  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
676
	  the CPU time on a given CPU, then RCU_KTHREAD_PRIO should be
677
	  set to priority 6 or higher.
678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693

	  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 已提交
694
config RCU_NOCB_CPU
695
	bool "Offload RCU callback processing from boot-selected CPUs"
696
	depends on TREE_RCU || PREEMPT_RCU
697
	depends on RCU_EXPERT || NO_HZ_FULL
P
Paul E. McKenney 已提交
698 699 700 701 702 703 704 705 706
	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.
707 708 709 710 711 712 713
	  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 已提交
714

715
	  Say Y here if you want to help to debug reduced OS jitter.
P
Paul E. McKenney 已提交
716 717
	  Say N here if you are unsure.

718 719 720
choice
	prompt "Build-forced no-CBs CPUs"
	default RCU_NOCB_CPU_NONE
721
	depends on RCU_NOCB_CPU
722
	help
723 724 725 726
	  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.
727 728 729 730 731 732

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
733 734 735 736 737 738 739
	  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.
740 741 742 743

config RCU_NOCB_CPU_ZERO
	bool "CPU 0 is a build_forced no-CBs CPU"
	help
744 745 746 747 748 749
	  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.
750 751

	  Select this if CPU 0 needs to be a no-CBs CPU for real-time
752 753
	  or energy-efficiency reasons, but the real reason it exists
	  is to ensure that randconfig testing covers mixed systems.
754 755 756 757 758

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=
759 760 761 762 763 764
	  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.
765 766 767 768 769 770

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

endchoice

771 772 773 774 775 776 777 778 779 780 781 782 783
config RCU_EXPEDITE_BOOT
	bool
	default n
	help
	  This option enables expedited grace periods at boot time,
	  as if rcu_expedite_gp() had been invoked early in boot.
	  The corresponding rcu_unexpedite_gp() is invoked from
	  rcu_end_inkernel_boot(), which is intended to be invoked
	  at the end of the kernel-only boot sequence, just before
	  init is exec'ed.

	  Accept the default if unsure.

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

786 787 788 789
config BUILD_BIN2C
	bool
	default n

L
Linus Torvalds 已提交
790
config IKCONFIG
791
	tristate "Kernel .config support"
792
	select BUILD_BIN2C
L
Linus Torvalds 已提交
793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809
	---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.

810 811
config LOG_BUF_SHIFT
	int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
812
	range 12 25
A
Adrian Bunk 已提交
813
	default 17
814
	depends on PRINTK
815
	help
816 817 818 819 820
	  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.

A
Adrian Bunk 已提交
821
	  Examples:
822
		     17 => 128 KB
A
Adrian Bunk 已提交
823
		     16 => 64 KB
824 825
		     15 => 32 KB
		     14 => 16 KB
826 827 828
		     13 =>  8 KB
		     12 =>  4 KB

829 830
config LOG_CPU_MAX_BUF_SHIFT
	int "CPU kernel log buffer size contribution (13 => 8 KB, 17 => 128KB)"
831
	depends on SMP
832 833 834
	range 0 21
	default 12 if !BASE_SMALL
	default 0 if BASE_SMALL
835
	depends on PRINTK
836 837 838 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
	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

865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886
config NMI_LOG_BUF_SHIFT
	int "Temporary per-CPU NMI log buffer size (12 => 4KB, 13 => 8KB)"
	range 10 21
	default 13
	depends on PRINTK_NMI
	help
	  Select the size of a per-CPU buffer where NMI messages are temporary
	  stored. They are copied to the main log buffer in a safe context
	  to avoid a deadlock. The value defines the size as a power of 2.

	  NMI messages are rare and limited. The largest one is when
	  a backtrace is printed. It usually fits into 4KB. Select
	  8KB if you want to be on the safe side.

	  Examples:
		     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

887 888 889 890 891 892
#
# Architectures with an unreliable sched_clock() should select this:
#
config HAVE_UNSTABLE_SCHED_CLOCK
	bool

893 894 895
config GENERIC_SCHED_CLOCK
	bool

896 897 898 899 900 901 902
#
# For architectures that want to enable the support for NUMA-affine scheduler
# balancing logic:
#
config ARCH_SUPPORTS_NUMA_BALANCING
	bool

903 904 905 906 907 908 909 910 911 912
#
# For architectures that prefer to flush all TLBs after a number of pages
# are unmapped instead of sending one IPI per page to flush. The architecture
# must provide guarantees on what happens if a clean TLB cache entry is
# written after the unmap. Details are in mm/rmap.c near the check for
# should_defer_flush. The architecture should also consider if the full flush
# and the refill costs are offset by the savings of sending fewer IPIs.
config ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH
	bool

P
Peter Zijlstra 已提交
913 914 915 916 917 918
#
# For architectures that know their GCC __int128 support is sound
#
config ARCH_SUPPORTS_INT128
	bool

919 920 921 922 923 924 925 926 927 928 929 930 931 932
# 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

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
933
	  it has references to the node the task is running on.
934 935 936

	  This system will be inactive on UMA systems.

937 938 939 940 941 942 943 944
config NUMA_BALANCING_DEFAULT_ENABLED
	bool "Automatically enable NUMA aware memory/task placement"
	default y
	depends on NUMA_BALANCING
	help
	  If set, automatic NUMA balancing will be enabled if running on a NUMA
	  machine.

L
Li Zefan 已提交
945
menuconfig CGROUPS
946
	bool "Control Group support"
T
Tejun Heo 已提交
947
	select KERNFS
948
	help
L
Li Zefan 已提交
949
	  This option adds support for grouping sets of processes together, for
950 951 952 953
	  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 已提交
954 955
		- Documentation/cgroups/ (features for grouping, isolation
					  and resource control)
956 957 958

	  Say N if unsure.

L
Li Zefan 已提交
959 960
if CGROUPS

961 962 963
config PAGE_COUNTER
       bool

A
Andrew Morton 已提交
964
config MEMCG
965
	bool "Memory controller"
966
	select PAGE_COUNTER
967
	select EVENTFD
968
	help
969
	  Provides control over the memory footprint of tasks in a cgroup.
970

A
Andrew Morton 已提交
971
config MEMCG_SWAP
972
	bool "Swap controller"
A
Andrew Morton 已提交
973
	depends on MEMCG && SWAP
974
	help
975 976
	  Provides control over the swap space consumed by tasks in a cgroup.

A
Andrew Morton 已提交
977
config MEMCG_SWAP_ENABLED
978
	bool "Swap controller enabled by default"
A
Andrew Morton 已提交
979
	depends on MEMCG_SWAP
980 981 982 983
	default y
	help
	  Memory Resource Controller Swap Extension comes with its price in
	  a bigger memory consumption. General purpose distribution kernels
J
Jim Cromie 已提交
984
	  which want to enable the feature but keep it disabled by default
985
	  and let the user enable it by swapaccount=1 boot command line
986 987 988
	  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
989
	  then swapaccount=0 does the trick).
990

991 992 993
config BLK_CGROUP
	bool "IO controller"
	depends on BLOCK
994
	default n
995 996 997 998
	---help---
	Generic block IO controller cgroup interface. This is the common
	cgroup interface which should be used by various IO controlling
	policies.
999

1000 1001 1002 1003
	Currently, CFQ IO scheduler uses it to recognize task groups and
	control disk bandwidth allocation (proportional time slice allocation)
	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.
S
Stephane Eranian 已提交
1004

1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024
	This option only enables generic Block IO controller infrastructure.
	One needs to also enable actual IO controlling logic/policy. For
	enabling proportional weight division of disk bandwidth in CFQ, set
	CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
	CONFIG_BLK_DEV_THROTTLING=y.

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

config DEBUG_BLK_CGROUP
	bool "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.

config CGROUP_WRITEBACK
	bool
	depends on MEMCG && BLK_CGROUP
	default y
S
Stephane Eranian 已提交
1025

D
Dhaval Giani 已提交
1026
menuconfig CGROUP_SCHED
1027
	bool "CPU controller"
D
Dhaval Giani 已提交
1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039
	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

1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050
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 已提交
1051 1052 1053 1054 1055 1056
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
1057
	  to task groups. If enabled, it will also make it impossible to
D
Dhaval Giani 已提交
1058 1059 1060 1061 1062 1063
	  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

1064 1065 1066 1067 1068 1069 1070 1071 1072
config CGROUP_PIDS
	bool "PIDs controller"
	help
	  Provides enforcement of process number limits in the scope of a
	  cgroup. Any attempt to fork more processes than is allowed in the
	  cgroup will fail. PIDs are fundamentally a global resource because it
	  is fairly trivial to reach PID exhaustion before you reach even a
	  conservative kmemcg limit. As a result, it is possible to grind a
	  system to halt without being limited by other cgroup policies. The
1073
	  PIDs controller is designed to stop this from happening.
1074 1075

	  It should be noted that organisational operations (such as attaching
1076
	  to a cgroup hierarchy will *not* be blocked by the PIDs controller),
1077 1078 1079 1080 1081 1082 1083 1084 1085
	  since the PIDs limit only affects a process's ability to fork, not to
	  attach to a cgroup.

config CGROUP_FREEZER
	bool "Freezer controller"
	help
	  Provides a way to freeze and unfreeze all tasks in a
	  cgroup.

1086 1087 1088 1089 1090
	  This option affects the ORIGINAL cgroup interface. The cgroup2 memory
	  controller includes important in-kernel memory consumers per default.

	  If you're using cgroup2, say N.

1091 1092 1093 1094
config CGROUP_HUGETLB
	bool "HugeTLB controller"
	depends on HUGETLB_PAGE
	select PAGE_COUNTER
1095
	default n
1096 1097 1098 1099 1100 1101 1102 1103 1104 1105
	help
	  Provides a cgroup 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.
1106

1107 1108 1109 1110 1111 1112 1113
config CPUSETS
	bool "Cpuset controller"
	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.
1114

1115
	  Say N if unsure.
1116

1117 1118 1119 1120
config PROC_PID_CPUSET
	bool "Include legacy /proc/<pid>/cpuset file"
	depends on CPUSETS
	default y
1121

1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145
config CGROUP_DEVICE
	bool "Device controller"
	help
	  Provides a cgroup controller implementing whitelists for
	  devices which a process in the cgroup can mknod or open.

config CGROUP_CPUACCT
	bool "Simple CPU accounting controller"
	help
	  Provides a simple controller for monitoring the
	  total CPU consumed by the tasks in a cgroup.

config CGROUP_PERF
	bool "Perf controller"
	depends on PERF_EVENTS
	help
	  This option extends the perf per-cpu mode to restrict monitoring
	  to threads which belong to the cgroup specified and run on the
	  designated cpu.

	  Say N if unsure.

config CGROUP_DEBUG
	bool "Example controller"
1146
	default n
1147 1148 1149
	help
	  This option enables a simple controller that exports
	  debugging information about the cgroups framework.
1150

1151
	  Say N.
1152

L
Li Zefan 已提交
1153
endif # CGROUPS
1154

1155 1156
config CHECKPOINT_RESTORE
	bool "Checkpoint/restore support" if EXPERT
1157
	select PROC_CHILDREN
1158 1159 1160 1161 1162 1163 1164 1165 1166
	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.

1167
menuconfig NAMESPACES
1168
	bool "Namespaces support" if EXPERT
1169
	depends on MULTIUSER
1170
	default !EXPERT
1171 1172 1173 1174 1175 1176
	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.

1177 1178
if NAMESPACES

1179 1180
config UTS_NS
	bool "UTS namespace"
1181
	default y
1182 1183 1184 1185
	help
	  In this namespace tasks see different info provided with the
	  uname() system call

1186 1187
config IPC_NS
	bool "IPC namespace"
1188
	depends on (SYSVIPC || POSIX_MQUEUE)
1189
	default y
1190 1191
	help
	  In this namespace tasks work with IPC ids which correspond to
1192
	  different IPC objects in different namespaces.
1193

1194
config USER_NS
1195
	bool "User namespace"
1196
	default n
1197 1198 1199
	help
	  This allows containers, i.e. vservers, to use user namespaces
	  to provide different user info for different servers.
1200 1201

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

1206 1207
	  If unsure, say N.

1208
config PID_NS
1209
	bool "PID Namespaces"
1210
	default y
1211
	help
1212
	  Support process id namespaces.  This allows having multiple
1213
	  processes with the same pid as long as they are in different
1214 1215
	  pid namespaces.  This is a building block of containers.

1216 1217
config NET_NS
	bool "Network namespace"
1218
	depends on NET
1219
	default y
1220 1221 1222 1223
	help
	  Allow user space to create what appear to be multiple instances
	  of the network stack.

1224 1225
endif # NAMESPACES

1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237
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.

1238
config SYSFS_DEPRECATED
1239
	bool "Enable deprecated sysfs features to support old userspace tools"
1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261
	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
1262
	bool "Enable deprecated sysfs features by default"
1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286
	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.

1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302
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.

1303 1304
if BLK_DEV_INITRD

1305 1306
source "usr/Kconfig"

1307 1308
endif

1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319
choice
	prompt "Compiler optimization level"
	default CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE

config CC_OPTIMIZE_FOR_PERFORMANCE
	bool "Optimize for performance"
	help
	  This is the default optimization level for the kernel, building
	  with the "-O2" compiler flag for best performance and most
	  helpful compile-time warnings.

1320
config CC_OPTIMIZE_FOR_SIZE
1321
	bool "Optimize for size"
1322
	help
1323 1324
	  Enabling this option will pass "-Os" instead of "-O2" to
	  your compiler resulting in a smaller kernel.
1325

1326
	  If unsure, say N.
1327

1328 1329
endchoice

R
Randy Dunlap 已提交
1330 1331 1332
config SYSCTL
	bool

R
Randy Dunlap 已提交
1333 1334 1335
config ANON_INODES
	bool

1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361
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

A
Alexei Starovoitov 已提交
1362 1363 1364 1365
# interpreter that classic socket filters depend on
config BPF
	bool

1366 1367
menuconfig EXPERT
	bool "Configure standard kernel features (expert users)"
1368 1369
	# Unhide debug options, to make the on-by-default options visible
	select DEBUG_KERNEL
L
Linus Torvalds 已提交
1370 1371 1372 1373 1374 1375
	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.

1376
config UID16
1377
	bool "Enable 16-bit UID system calls" if EXPERT
1378
	depends on HAVE_UID16 && MULTIUSER
1379 1380 1381 1382
	default y
	help
	  This enables the legacy 16-bit UID syscall wrappers.

1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396
config MULTIUSER
	bool "Multiple users, groups and capabilities support" if EXPERT
	default y
	help
	  This option enables support for non-root users, groups and
	  capabilities.

	  If you say N here, all processes will run with UID 0, GID 0, and all
	  possible capabilities.  Saying N here also compiles out support for
	  system calls related to UIDs, GIDs, and capabilities, such as setuid,
	  setgid, and capset.

	  If unsure, say Y here.

1397 1398 1399 1400 1401 1402 1403 1404 1405 1406
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.

1407 1408 1409 1410 1411 1412 1413 1414 1415 1416
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.

1417
config SYSCTL_SYSCALL
1418
	bool "Sysctl syscall support" if EXPERT
1419
	depends on PROC_SYSCTL
1420
	default n
1421
	select SYSCTL
1422
	---help---
1423 1424 1425 1426
	  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.
1427

1428 1429 1430
	  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.
1431

1432
	  If unsure say N here.
1433

L
Linus Torvalds 已提交
1434
config KALLSYMS
1435
	 bool "Load all symbols for debugging/ksymoops" if EXPERT
L
Linus Torvalds 已提交
1436 1437 1438 1439 1440 1441 1442 1443 1444 1445
	 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
1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457
	   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 已提交
1458

1459 1460
config KALLSYMS_ABSOLUTE_PERCPU
	bool
1461
	depends on KALLSYMS
1462 1463
	default X86_64 && SMP

1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481
config KALLSYMS_BASE_RELATIVE
	bool
	depends on KALLSYMS
	default !IA64 && !(TILE && 64BIT)
	help
	  Instead of emitting them as absolute values in the native word size,
	  emit the symbol references in the kallsyms table as 32-bit entries,
	  each containing a relative value in the range [base, base + U32_MAX]
	  or, when KALLSYMS_ABSOLUTE_PERCPU is in effect, each containing either
	  an absolute value in the range [0, S32_MAX] or a relative value in the
	  range [base, base + S32_MAX], where base is the lowest relative symbol
	  address encountered in the image.

	  On 64-bit builds, this reduces the size of the address table by 50%,
	  but more importantly, it results in entries whose values are build
	  time constants, and no relocation pass is required at runtime to fix
	  up the entries based on the runtime load address of the kernel.

M
Matt Mackall 已提交
1482 1483
config PRINTK
	default y
1484
	bool "Enable support for printk" if EXPERT
1485
	select IRQ_WORK
M
Matt Mackall 已提交
1486 1487 1488 1489 1490 1491 1492
	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.

1493 1494 1495 1496 1497
config PRINTK_NMI
	def_bool y
	depends on PRINTK
	depends on HAVE_NMI

M
Matt Mackall 已提交
1498
config BUG
1499
	bool "BUG() support" if EXPERT
M
Matt Mackall 已提交
1500 1501 1502 1503 1504 1505 1506 1507
	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.

1508
config ELF_CORE
1509
	depends on COREDUMP
1510
	default y
1511
	bool "Enable ELF core dumps" if EXPERT
1512 1513 1514
	help
	  Enable support for generating core dumps. Disabling saves about 4k.

1515

S
Stas Sergeev 已提交
1516
config PCSPKR_PLATFORM
1517
	bool "Enable PC-Speaker support" if EXPERT
1518
	depends on HAVE_PCSPKR_PLATFORM
1519
	select I8253_LOCK
S
Stas Sergeev 已提交
1520 1521 1522 1523 1524
	default y
	help
          This option allows to disable the internal PC-Speaker
          support, saving some memory.

L
Linus Torvalds 已提交
1525 1526
config BASE_FULL
	default y
1527
	bool "Enable full-sized data structures for core" if EXPERT
L
Linus Torvalds 已提交
1528 1529 1530 1531 1532 1533
	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
1534
	bool "Enable futex support" if EXPERT
L
Linus Torvalds 已提交
1535
	default y
I
Ingo Molnar 已提交
1536
	select RT_MUTEXES
L
Linus Torvalds 已提交
1537 1538 1539 1540 1541
	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.

1542 1543
config HAVE_FUTEX_CMPXCHG
	bool
1544
	depends on FUTEX
1545 1546 1547 1548 1549
	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 已提交
1550
config EPOLL
1551
	bool "Enable eventpoll support" if EXPERT
L
Linus Torvalds 已提交
1552
	default y
1553
	select ANON_INODES
L
Linus Torvalds 已提交
1554 1555 1556 1557
	help
	  Disabling this option will cause the kernel to be built without
	  support for epoll family of system calls.

1558
config SIGNALFD
1559
	bool "Enable signalfd() system call" if EXPERT
1560
	select ANON_INODES
1561 1562 1563 1564 1565 1566 1567
	default y
	help
	  Enable the signalfd() system call that allows to receive signals
	  on a file descriptor.

	  If unsure, say Y.

1568
config TIMERFD
1569
	bool "Enable timerfd() system call" if EXPERT
1570
	select ANON_INODES
1571 1572 1573 1574 1575 1576 1577
	default y
	help
	  Enable the timerfd() system call that allows to receive timer
	  events on a file descriptor.

	  If unsure, say Y.

1578
config EVENTFD
1579
	bool "Enable eventfd() system call" if EXPERT
1580
	select ANON_INODES
1581 1582 1583 1584 1585 1586 1587
	default y
	help
	  Enable the eventfd() system call that allows to receive both
	  kernel notification (ie. KAIO) or userspace notifications.

	  If unsure, say Y.

A
Alexei Starovoitov 已提交
1588 1589
# syscall, maps, verifier
config BPF_SYSCALL
1590
	bool "Enable bpf() system call"
A
Alexei Starovoitov 已提交
1591 1592 1593 1594 1595 1596 1597
	select ANON_INODES
	select BPF
	default n
	help
	  Enable the bpf() system call that allows to manipulate eBPF
	  programs and maps via file descriptors.

L
Linus Torvalds 已提交
1598
config SHMEM
1599
	bool "Use full shmem filesystem" if EXPERT
L
Linus Torvalds 已提交
1600 1601 1602 1603 1604 1605 1606 1607 1608
	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 已提交
1609
config AIO
1610
	bool "Enable AIO support" if EXPERT
T
Thomas Petazzoni 已提交
1611 1612 1613
	default y
	help
	  This option enables POSIX asynchronous I/O which may by used
1614 1615 1616
	  by some high performance threaded applications. Disabling
	  this option saves about 7k.

1617 1618 1619 1620 1621 1622 1623 1624 1625 1626
config ADVISE_SYSCALLS
	bool "Enable madvise/fadvise syscalls" if EXPERT
	default y
	help
	  This option enables the madvise and fadvise syscalls, used by
	  applications to advise the kernel about their future memory or file
	  usage, improving performance. If building an embedded system where no
	  applications use these syscalls, you can disable this option to save
	  space.

1627 1628 1629 1630 1631 1632 1633 1634
config USERFAULTFD
	bool "Enable userfaultfd() system call"
	select ANON_INODES
	depends on MMU
	help
	  Enable the userfaultfd() system call that allows to intercept and
	  handle page faults in userland.

1635 1636 1637 1638 1639 1640 1641 1642
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 已提交
1643

1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655
config MEMBARRIER
	bool "Enable membarrier() system call" if EXPERT
	default y
	help
	  Enable the membarrier() system call that allows issuing memory
	  barriers across all running threads, which can be used to distribute
	  the cost of user-space memory barriers asymmetrically by transforming
	  pairs of memory barriers into pairs consisting of membarrier() and a
	  compiler barrier.

	  If unsure, say Y.

1656 1657
config EMBEDDED
	bool "Embedded system"
1658
	option allnoconfig_y
1659 1660 1661 1662 1663 1664
	select EXPERT
	help
	  This option should be enabled if compiling the kernel for
	  an embedded system so certain expert options are available
	  for configuration.

1665
config HAVE_PERF_EVENTS
T
Thomas Gleixner 已提交
1666
	bool
1667 1668
	help
	  See tools/perf/design.txt for details.
T
Thomas Gleixner 已提交
1669

1670 1671 1672 1673 1674
config PERF_USE_VMALLOC
	bool
	help
	  See tools/perf/design.txt for details

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

1677
config PERF_EVENTS
I
Ingo Molnar 已提交
1678
	bool "Kernel performance events and counters"
1679
	default y if PROFILING
1680
	depends on HAVE_PERF_EVENTS
I
Ingo Molnar 已提交
1681
	select ANON_INODES
1682
	select IRQ_WORK
1683
	select SRCU
T
Thomas Gleixner 已提交
1684
	help
I
Ingo Molnar 已提交
1685 1686
	  Enable kernel support for various performance events provided
	  by software and hardware.
T
Thomas Gleixner 已提交
1687

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

I
Ingo Molnar 已提交
1691 1692
	  Most modern CPUs support performance events via performance
	  counter registers. These registers count the number of certain
T
Thomas Gleixner 已提交
1693 1694 1695 1696 1697 1698
	  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 已提交
1699
	  The Linux Performance Event subsystem provides an abstraction of
1700
	  these software and hardware event capabilities, available via a
I
Ingo Molnar 已提交
1701
	  system call and used by the "perf" utility in tools/perf/. It
T
Thomas Gleixner 已提交
1702 1703 1704 1705 1706
	  provides per task and per CPU counters, and it provides event
	  capabilities on top of those.

	  Say Y if unsure.

1707 1708 1709
config DEBUG_PERF_USE_VMALLOC
	default n
	bool "Debug: use vmalloc to back perf mmap() buffers"
1710
	depends on PERF_EVENTS && DEBUG_KERNEL && !PPC
1711 1712 1713 1714 1715 1716 1717 1718 1719
	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 已提交
1720 1721
endmenu

1722 1723
config VM_EVENT_COUNTERS
	default y
1724
	bool "Enable VM event counters for /proc/vmstat" if EXPERT
1725
	help
1726 1727
	  VM event counters are needed for event counts to be shown.
	  This option allows the disabling of the VM event counters
1728
	  on EXPERT systems.  /proc/vmstat will only show page counts
1729
	  if VM event counters are disabled.
1730

C
Christoph Lameter 已提交
1731 1732
config SLUB_DEBUG
	default y
1733
	bool "Enable SLUB debugging support" if EXPERT
C
Christoph Lameter 已提交
1734
	depends on SLUB && SYSFS
C
Christoph Lameter 已提交
1735 1736 1737 1738 1739 1740
	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 已提交
1741 1742 1743 1744 1745 1746 1747
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
1748
	  disabled, and can be overridden at runtime by setting
R
Randy Dunlap 已提交
1749 1750 1751 1752
	  /proc/sys/kernel/randomize_va_space to 2.

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

C
Christoph Lameter 已提交
1753 1754
choice
	prompt "Choose SLAB allocator"
1755
	default SLUB
C
Christoph Lameter 已提交
1756 1757 1758 1759 1760 1761 1762
	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
1763
	  well in all environments. It organizes cache hot objects in
1764
	  per cpu and per node queues.
C
Christoph Lameter 已提交
1765 1766 1767 1768 1769 1770 1771 1772

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
1773 1774
	   and has enhanced diagnostics. SLUB is the default choice for
	   a slab allocator.
C
Christoph Lameter 已提交
1775 1776

config SLOB
1777
	depends on EXPERT
C
Christoph Lameter 已提交
1778 1779
	bool "SLOB (Simple Allocator)"
	help
M
Matt Mackall 已提交
1780 1781 1782
	   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 已提交
1783 1784 1785

endchoice

T
Thomas Garnier 已提交
1786 1787 1788 1789 1790 1791 1792 1793 1794
config SLAB_FREELIST_RANDOM
	default n
	depends on SLAB
	bool "SLAB freelist randomization"
	help
	  Randomizes the freelist order used on creating new SLABs. This
	  security feature reduces the predictability of the kernel slab
	  allocator against heap overflows.

1795 1796
config SLUB_CPU_PARTIAL
	default y
1797
	depends on SLUB && SMP
1798 1799 1800 1801 1802 1803 1804 1805
	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.

1806 1807
config MMAP_ALLOW_UNINITIALIZED
	bool "Allow mmapped anonymous memory to be uninitialized"
1808
	depends on EXPERT && !MMU
1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827
	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.

1828 1829 1830 1831 1832
config SYSTEM_DATA_VERIFICATION
	def_bool n
	select SYSTEM_TRUSTED_KEYRING
	select KEYS
	select CRYPTO
1833
	select CRYPTO_RSA
1834 1835 1836 1837 1838 1839
	select ASYMMETRIC_KEY_TYPE
	select ASYMMETRIC_PUBLIC_KEY_SUBTYPE
	select ASN1
	select OID_REGISTRY
	select X509_CERTIFICATE_PARSER
	select PKCS7_MESSAGE_PARSER
1840
	help
1841 1842 1843 1844
	  Provide PKCS#7 message verification using the contents of the system
	  trusted keyring to provide public keys.  This then can be used for
	  module verification, kexec image verification and firmware blob
	  verification.
1845

1846
config PROFILING
1847
	bool "Profiling support"
1848 1849 1850 1851
	help
	  Say Y here to enable the extended profiling support mechanisms used
	  by profilers such as OProfile.

1852 1853 1854 1855
#
# Place an empty function call at each tracepoint site. Can be
# dynamically changed for a probe function.
#
M
Mathieu Desnoyers 已提交
1856
config TRACEPOINTS
1857
	bool
M
Mathieu Desnoyers 已提交
1858

M
Mathieu Desnoyers 已提交
1859 1860
source "arch/Kconfig"

L
Linus Torvalds 已提交
1861 1862
endmenu		# General setup

1863 1864 1865 1866
config HAVE_GENERIC_DMA_COHERENT
	bool
	default n

1867 1868 1869
config SLABINFO
	bool
	depends on PROC_FS
1870
	depends on SLAB || SLUB_DEBUG
1871 1872
	default y

1873
config RT_MUTEXES
1874
	bool
1875

L
Linus Torvalds 已提交
1876 1877 1878 1879 1880
config BASE_SMALL
	int
	default 0 if BASE_FULL
	default 1 if !BASE_FULL

1881
menuconfig MODULES
L
Linus Torvalds 已提交
1882
	bool "Enable loadable module support"
1883
	option modules
L
Linus Torvalds 已提交
1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901
	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.

1902 1903
if MODULES

1904 1905 1906 1907
config MODULE_FORCE_LOAD
	bool "Forced module loading"
	default n
	help
1908 1909 1910
	  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.
1911

L
Linus Torvalds 已提交
1912 1913 1914 1915 1916
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
1917 1918
	  anyway), which makes your kernel smaller, faster
	  and simpler.  If unsure, say Y.
L
Linus Torvalds 已提交
1919 1920 1921

config MODULE_FORCE_UNLOAD
	bool "Forced module unloading"
1922
	depends on MODULE_UNLOAD
L
Linus Torvalds 已提交
1923 1924 1925 1926 1927 1928 1929 1930
	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
1931
	bool "Module versioning support"
L
Linus Torvalds 已提交
1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950
	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 已提交
1951 1952 1953
config MODULE_SIG
	bool "Module signature verification"
	depends on MODULES
1954
	select SYSTEM_DATA_VERIFICATION
R
Rusty Russell 已提交
1955 1956 1957 1958 1959
	help
	  Check modules for valid signatures upon load: the signature
	  is simply appended to the module. For more information see
	  Documentation/module-signing.txt.

1960 1961 1962 1963
	  Note that this option adds the OpenSSL development packages as a
	  kernel build dependency so that the signing tool can use its crypto
	  library.

D
David Howells 已提交
1964 1965 1966 1967 1968
	  !!!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 已提交
1969 1970 1971 1972 1973 1974
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 已提交
1975

1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986
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 已提交
1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018
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

2019 2020 2021 2022 2023 2024 2025 2026 2027
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

2028 2029 2030 2031 2032
config MODULE_COMPRESS
	bool "Compress modules on installation"
	depends on MODULES
	help

2033 2034
	  Compresses kernel modules when 'make modules_install' is run; gzip or
	  xz depending on "Compression algorithm" below.
2035

2036
	  module-init-tools MAY support gzip, and kmod MAY support gzip and xz.
2037

2038 2039
	  Out-of-tree kernel modules installed using Kbuild will also be
	  compressed upon installation.
2040

2041 2042
	  Note: for modules inside an initrd or initramfs, it's more efficient
	  to compress the whole initrd or initramfs instead.
2043

2044 2045 2046
	  Note: This is fully compatible with signed modules.

	  If in doubt, say N.
2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065

choice
	prompt "Compression algorithm"
	depends on MODULE_COMPRESS
	default MODULE_COMPRESS_GZIP
	help
	  This determines which sort of compression will be used during
	  'make modules_install'.

	  GZIP (default) and XZ are supported.

config MODULE_COMPRESS_GZIP
	bool "GZIP"

config MODULE_COMPRESS_XZ
	bool "XZ"

endchoice

2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081
config TRIM_UNUSED_KSYMS
	bool "Trim unused exported kernel symbols"
	depends on MODULES && !UNUSED_SYMBOLS
	help
	  The kernel and some modules make many symbols available for
	  other modules to use via EXPORT_SYMBOL() and variants. Depending
	  on the set of modules being selected in your kernel configuration,
	  many of those exported symbols might never be used.

	  This option allows for unused exported symbols to be dropped from
	  the build. In turn, this provides the compiler more opportunities
	  (especially when using LTO) for optimizing the code and reducing
	  binary size.  This might have some security advantages as well.

	  If unsure say N.

2082 2083
endif # MODULES

2084 2085 2086 2087
config MODULES_TREE_LOOKUP
	def_bool y
	depends on PERF_EVENTS || TRACING

2088 2089 2090
config INIT_ALL_POSSIBLE
	bool
	help
2091 2092
	  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
2093 2094
	  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
2095
	  and have several arch maintainers pursuing me down dark alleys.
2096

2097
source "block/Kconfig"
2098 2099 2100

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

2102 2103 2104 2105
config PADATA
	depends on SMP
	bool

2106 2107 2108 2109 2110 2111
# Can be selected by architectures with broken toolchains
# that get confused by correct const<->read_only section
# mappings
config BROKEN_RODATA
	bool

2112 2113 2114 2115 2116 2117 2118 2119
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.

2120
source "kernel/Kconfig.locks"