init/Kconfig

   1 config ARCH
   2         string
   3         option env="ARCH"
   4
   5 config KERNELVERSION
   6         string
   7         option env="KERNELVERSION"
   8
   9 config DEFCONFIG_LIST
  10         string
  11         depends on !UML
  12         option defconfig_list
  13         default "/lib/modules/$UNAME_RELEASE/.config"
  14         default "/etc/kernel-config"
  15         default "/boot/config-$UNAME_RELEASE"
  16         default "$ARCH_DEFCONFIG"
  17         default "arch/$ARCH/defconfig"
  18
  19 config CONSTRUCTORS
  20         bool
  21         depends on !UML
  22
  23 config HAVE_IRQ_WORK
  24         bool
  25
  26 config IRQ_WORK
  27         bool
  28         depends on HAVE_IRQ_WORK
  29
  30 config BUILDTIME_EXTABLE_SORT
  31         bool
  32
  33 menu "General setup"
  34
  35 config EXPERIMENTAL
  36         bool "Prompt for development and/or incomplete code/drivers"
  37         ---help---
  38           Some of the various things that Linux supports (such as network
  39           drivers, file systems, network protocols, etc.) can be in a state
  40           of development where the functionality, stability, or the level of
  41           testing is not yet high enough for general use. This is usually
  42           known as the "alpha-test" phase among developers. If a feature is
  43           currently in alpha-test, then the developers usually discourage
  44           uninformed widespread use of this feature by the general public to
  45           avoid "Why doesn't this work?" type mail messages. However, active
  46           testing and use of these systems is welcomed. Just be aware that it
  47           may not meet the normal level of reliability or it may fail to work
  48           in some special cases. Detailed bug reports from people familiar
  49           with the kernel internals are usually welcomed by the developers
  50           (before submitting bug reports, please read the documents
  51           <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
  52           <file:Documentation/BUG-HUNTING>, and
  53           <file:Documentation/oops-tracing.txt> in the kernel source).
  54
  55           This option will also make obsoleted drivers available. These are
  56           drivers that have been replaced by something else, and/or are
  57           scheduled to be removed in a future kernel release.
  58
  59           Unless you intend to help test and develop a feature or driver that
  60           falls into this category, or you have a situation that requires
  61           using these features, you should probably say N here, which will
  62           cause the configurator to present you with fewer choices. If
  63           you say Y here, you will be offered the choice of using features or
  64           drivers that are currently considered to be in the alpha-test phase.
  65
  66 config BROKEN
  67         bool
  68
  69 config BROKEN_ON_SMP
  70         bool
  71         depends on BROKEN || !SMP
  72         default y
  73
  74 config INIT_ENV_ARG_LIMIT
  75         int
  76         default 32 if !UML
  77         default 128 if UML
  78         help
  79           Maximum of each of the number of arguments and environment
  80           variables passed to init from the kernel command line.
  81
  82
  83 config CROSS_COMPILE
  84         string "Cross-compiler tool prefix"
  85         help
  86           Same as running 'make CROSS_COMPILE=prefix-' but stored for
  87           default make runs in this kernel build directory.  You don't
  88           need to set this unless you want the configured kernel build
  89           directory to select the cross-compiler automatically.
  90
  91 config LOCALVERSION
  92         string "Local version - append to kernel release"
  93         help
  94           Append an extra string to the end of your kernel version.
  95           This will show up when you type uname, for example.
  96           The string you set here will be appended after the contents of
  97           any files with a filename matching localversion* in your
  98           object and source tree, in that order.  Your total string can
  99           be a maximum of 64 characters.
 100
 101 config LOCALVERSION_AUTO
 102         bool "Automatically append version information to the version string"
 103         default y
 104         help
 105           This will try to automatically determine if the current tree is a
 106           release tree by looking for git tags that belong to the current
 107           top of tree revision.
 108
 109           A string of the format -gxxxxxxxx will be added to the localversion
 110           if a git-based tree is found.  The string generated by this will be
 111           appended after any matching localversion* files, and after the value
 112           set in CONFIG_LOCALVERSION.
 113
 114           (The actual string used here is the first eight characters produced
 115           by running the command:
 116
 117             $ git rev-parse --verify HEAD
 118
 119           which is done within the script "scripts/setlocalversion".)
 120
 121 config HAVE_KERNEL_GZIP
 122         bool
 123
 124 config HAVE_KERNEL_BZIP2
 125         bool
 126
 127 config HAVE_KERNEL_LZMA
 128         bool
 129
 130 config HAVE_KERNEL_XZ
 131         bool
 132
 133 config HAVE_KERNEL_LZO
 134         bool
 135
 136 choice
 137         prompt "Kernel compression mode"
 138         default KERNEL_GZIP
 139         depends on HAVE_KERNEL_GZIP || HAVE_KERNEL_BZIP2 || HAVE_KERNEL_LZMA || HAVE_KERNEL_XZ || HAVE_KERNEL_LZO
 140         help
 141           The linux kernel is a kind of self-extracting executable.
 142           Several compression algorithms are available, which differ
 143           in efficiency, compression and decompression speed.
 144           Compression speed is only relevant when building a kernel.
 145           Decompression speed is relevant at each boot.
 146
 147           If you have any problems with bzip2 or lzma compressed
 148           kernels, mail me (Alain Knaff) <alain@knaff.lu>. (An older
 149           version of this functionality (bzip2 only), for 2.4, was
 150           supplied by Christian Ludwig)
 151
 152           High compression options are mostly useful for users, who
 153           are low on disk space (embedded systems), but for whom ram
 154           size matters less.
 155
 156           If in doubt, select 'gzip'
 157
 158 config KERNEL_GZIP
 159         bool "Gzip"
 160         depends on HAVE_KERNEL_GZIP
 161         help
 162           The old and tried gzip compression. It provides a good balance
 163           between compression ratio and decompression speed.
 164
 165 config KERNEL_BZIP2
 166         bool "Bzip2"
 167         depends on HAVE_KERNEL_BZIP2
 168         help
 169           Its compression ratio and speed is intermediate.
 170           Decompression speed is slowest among the choices.  The kernel
 171           size is about 10% smaller with bzip2, in comparison to gzip.
 172           Bzip2 uses a large amount of memory. For modern kernels you
 173           will need at least 8MB RAM or more for booting.
 174
 175 config KERNEL_LZMA
 176         bool "LZMA"
 177         depends on HAVE_KERNEL_LZMA
 178         help
 179           This compression algorithm's ratio is best.  Decompression speed
 180           is between gzip and bzip2.  Compression is slowest.
 181           The kernel size is about 33% smaller with LZMA in comparison to gzip.
 182
 183 config KERNEL_XZ
 184         bool "XZ"
 185         depends on HAVE_KERNEL_XZ
 186         help
 187           XZ uses the LZMA2 algorithm and instruction set specific
 188           BCJ filters which can improve compression ratio of executable
 189           code. The size of the kernel is about 30% smaller with XZ in
 190           comparison to gzip. On architectures for which there is a BCJ
 191           filter (i386, x86_64, ARM, IA-64, PowerPC, and SPARC), XZ
 192           will create a few percent smaller kernel than plain LZMA.
 193
 194           The speed is about the same as with LZMA: The decompression
 195           speed of XZ is better than that of bzip2 but worse than gzip
 196           and LZO. Compression is slow.
 197
 198 config KERNEL_LZO
 199         bool "LZO"
 200         depends on HAVE_KERNEL_LZO
 201         help
 202           Its compression ratio is the poorest among the choices. The kernel
 203           size is about 10% bigger than gzip; however its speed
 204           (both compression and decompression) is the fastest.
 205
 206 endchoice
 207
 208 config DEFAULT_HOSTNAME
 209         string "Default hostname"
 210         default "(none)"
 211         help
 212           This option determines the default system hostname before userspace
 213           calls sethostname(2). The kernel traditionally uses "(none)" here,
 214           but you may wish to use a different default here to make a minimal
 215           system more usable with less configuration.
 216
 217 config SWAP
 218         bool "Support for paging of anonymous memory (swap)"
 219         depends on MMU && BLOCK
 220         default y
 221         help
 222           This option allows you to choose whether you want to have support
 223           for so called swap devices or swap files in your kernel that are
 224           used to provide more virtual memory than the actual RAM present
 225           in your computer.  If unsure say Y.
 226
 227 config SYSVIPC
 228         bool "System V IPC"
 229         ---help---
 230           Inter Process Communication is a suite of library functions and
 231           system calls which let processes (running programs) synchronize and
 232           exchange information. It is generally considered to be a good thing,
 233           and some programs won't run unless you say Y here. In particular, if
 234           you want to run the DOS emulator dosemu under Linux (read the
 235           DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
 236           you'll need to say Y here.
 237
 238           You can find documentation about IPC with "info ipc" and also in
 239           section 6.4 of the Linux Programmer's Guide, available from
 240           <http://www.tldp.org/guides.html>.
 241
 242 config SYSVIPC_SYSCTL
 243         bool
 244         depends on SYSVIPC
 245         depends on SYSCTL
 246         default y
 247
 248 config POSIX_MQUEUE
 249         bool "POSIX Message Queues"
 250         depends on NET && EXPERIMENTAL
 251         ---help---
 252           POSIX variant of message queues is a part of IPC. In POSIX message
 253           queues every message has a priority which decides about succession
 254           of receiving it by a process. If you want to compile and run
 255           programs written e.g. for Solaris with use of its POSIX message
 256           queues (functions mq_*) say Y here.
 257
 258           POSIX message queues are visible as a filesystem called 'mqueue'
 259           and can be mounted somewhere if you want to do filesystem
 260           operations on message queues.
 261
 262           If unsure, say Y.
 263
 264 config POSIX_MQUEUE_SYSCTL
 265         bool
 266         depends on POSIX_MQUEUE
 267         depends on SYSCTL
 268         default y
 269
 270 config BSD_PROCESS_ACCT
 271         bool "BSD Process Accounting"
 272         help
 273           If you say Y here, a user level program will be able to instruct the
 274           kernel (via a special system call) to write process accounting
 275           information to a file: whenever a process exits, information about
 276           that process will be appended to the file by the kernel.  The
 277           information includes things such as creation time, owning user,
 278           command name, memory usage, controlling terminal etc. (the complete
 279           list is in the struct acct in <file:include/linux/acct.h>).  It is
 280           up to the user level program to do useful things with this
 281           information.  This is generally a good idea, so say Y.
 282
 283 config BSD_PROCESS_ACCT_V3
 284         bool "BSD Process Accounting version 3 file format"
 285         depends on BSD_PROCESS_ACCT
 286         default n
 287         help
 288           If you say Y here, the process accounting information is written
 289           in a new file format that also logs the process IDs of each
 290           process and it's parent. Note that this file format is incompatible
 291           with previous v0/v1/v2 file formats, so you will need updated tools
 292           for processing it. A preliminary version of these tools is available
 293           at <http://www.gnu.org/software/acct/>.
 294
 295 config FHANDLE
 296         bool "open by fhandle syscalls"
 297         select EXPORTFS
 298         help
 299           If you say Y here, a user level program will be able to map
 300           file names to handle and then later use the handle for
 301           different file system operations. This is useful in implementing
 302           userspace file servers, which now track files using handles instead
 303           of names. The handle would remain the same even if file names
 304           get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2)
 305           syscalls.
 306
 307 config TASKSTATS
 308         bool "Export task/process statistics through netlink (EXPERIMENTAL)"
 309         depends on NET
 310         default n
 311         help
 312           Export selected statistics for tasks/processes through the
 313           generic netlink interface. Unlike BSD process accounting, the
 314           statistics are available during the lifetime of tasks/processes as
 315           responses to commands. Like BSD accounting, they are sent to user
 316           space on task exit.
 317
 318           Say N if unsure.
 319
 320 config TASK_DELAY_ACCT
 321         bool "Enable per-task delay accounting (EXPERIMENTAL)"
 322         depends on TASKSTATS
 323         help
 324           Collect information on time spent by a task waiting for system
 325           resources like cpu, synchronous block I/O completion and swapping
 326           in pages. Such statistics can help in setting a task's priorities
 327           relative to other tasks for cpu, io, rss limits etc.
 328
 329           Say N if unsure.
 330
 331 config TASK_XACCT
 332         bool "Enable extended accounting over taskstats (EXPERIMENTAL)"
 333         depends on TASKSTATS
 334         help
 335           Collect extended task accounting data and send the data
 336           to userland for processing over the taskstats interface.
 337
 338           Say N if unsure.
 339
 340 config TASK_IO_ACCOUNTING
 341         bool "Enable per-task storage I/O accounting (EXPERIMENTAL)"
 342         depends on TASK_XACCT
 343         help
 344           Collect information on the number of bytes of storage I/O which this
 345           task has caused.
 346
 347           Say N if unsure.
 348
 349 config AUDIT
 350         bool "Auditing support"
 351         depends on NET
 352         help
 353           Enable auditing infrastructure that can be used with another
 354           kernel subsystem, such as SELinux (which requires this for
 355           logging of avc messages output).  Does not do system-call
 356           auditing without CONFIG_AUDITSYSCALL.
 357
 358 config AUDITSYSCALL
 359         bool "Enable system-call auditing support"
 360         depends on AUDIT && (X86 || PPC || S390 || IA64 || UML || SPARC64 || SUPERH || (ARM && AEABI && !OABI_COMPAT))
 361         default y if SECURITY_SELINUX
 362         help
 363           Enable low-overhead system-call auditing infrastructure that
 364           can be used independently or with another kernel subsystem,
 365           such as SELinux.
 366
 367 config AUDIT_WATCH
 368         def_bool y
 369         depends on AUDITSYSCALL
 370         select FSNOTIFY
 371
 372 config AUDIT_TREE
 373         def_bool y
 374         depends on AUDITSYSCALL
 375         select FSNOTIFY
 376
 377 config AUDIT_LOGINUID_IMMUTABLE
 378         bool "Make audit loginuid immutable"
 379         depends on AUDIT
 380         help
 381           The config option toggles if a task setting its loginuid requires
 382           CAP_SYS_AUDITCONTROL or if that task should require no special permissions
 383           but should instead only allow setting its loginuid if it was never
 384           previously set.  On systems which use systemd or a similar central
 385           process to restart login services this should be set to true.  On older
 386           systems in which an admin would typically have to directly stop and
 387           start processes this should be set to false.  Setting this to true allows
 388           one to drop potentially dangerous capabilites from the login tasks,
 389           but may not be backwards compatible with older init systems.
 390
 391 source "kernel/irq/Kconfig"
 392 source "kernel/time/Kconfig"
 393
 394 menu "RCU Subsystem"
 395
 396 choice
 397         prompt "RCU Implementation"
 398         default TREE_RCU
 399
 400 config TREE_RCU
 401         bool "Tree-based hierarchical RCU"
 402         depends on !PREEMPT && SMP
 403         help
 404           This option selects the RCU implementation that is
 405           designed for very large SMP system with hundreds or
 406           thousands of CPUs.  It also scales down nicely to
 407           smaller systems.
 408
 409 config TREE_PREEMPT_RCU
 410         bool "Preemptible tree-based hierarchical RCU"
 411         depends on PREEMPT && SMP
 412         help
 413           This option selects the RCU implementation that is
 414           designed for very large SMP systems with hundreds or
 415           thousands of CPUs, but for which real-time response
 416           is also required.  It also scales down nicely to
 417           smaller systems.
 418
 419 config TINY_RCU
 420         bool "UP-only small-memory-footprint RCU"
 421         depends on !PREEMPT && !SMP
 422         help
 423           This option selects the RCU implementation that is
 424           designed for UP systems from which real-time response
 425           is not required.  This option greatly reduces the
 426           memory footprint of RCU.
 427
 428 config TINY_PREEMPT_RCU
 429         bool "Preemptible UP-only small-memory-footprint RCU"
 430         depends on PREEMPT && !SMP
 431         help
 432           This option selects the RCU implementation that is designed
 433           for real-time UP systems.  This option greatly reduces the
 434           memory footprint of RCU.
 435
 436 endchoice
 437
 438 config PREEMPT_RCU
 439         def_bool ( TREE_PREEMPT_RCU || TINY_PREEMPT_RCU )
 440         help
 441           This option enables preemptible-RCU code that is common between
 442           the TREE_PREEMPT_RCU and TINY_PREEMPT_RCU implementations.
 443
 444 config RCU_FANOUT
 445         int "Tree-based hierarchical RCU fanout value"
 446         range 2 64 if 64BIT
 447         range 2 32 if !64BIT
 448         depends on TREE_RCU || TREE_PREEMPT_RCU
 449         default 64 if 64BIT
 450         default 32 if !64BIT
 451         help
 452           This option controls the fanout of hierarchical implementations
 453           of RCU, allowing RCU to work efficiently on machines with
 454           large numbers of CPUs.  This value must be at least the fourth
 455           root of NR_CPUS, which allows NR_CPUS to be insanely large.
 456           The default value of RCU_FANOUT should be used for production
 457           systems, but if you are stress-testing the RCU implementation
 458           itself, small RCU_FANOUT values allow you to test large-system
 459           code paths on small(er) systems.
 460
 461           Select a specific number if testing RCU itself.
 462           Take the default if unsure.
 463
 464 config RCU_FANOUT_LEAF
 465         int "Tree-based hierarchical RCU leaf-level fanout value"
 466         range 2 RCU_FANOUT if 64BIT
 467         range 2 RCU_FANOUT if !64BIT
 468         depends on TREE_RCU || TREE_PREEMPT_RCU
 469         default 16
 470         help
 471           This option controls the leaf-level fanout of hierarchical
 472           implementations of RCU, and allows trading off cache misses
 473           against lock contention.  Systems that synchronize their
 474           scheduling-clock interrupts for energy-efficiency reasons will
 475           want the default because the smaller leaf-level fanout keeps
 476           lock contention levels acceptably low.  Very large systems
 477           (hundreds or thousands of CPUs) will instead want to set this
 478           value to the maximum value possible in order to reduce the
 479           number of cache misses incurred during RCU's grace-period
 480           initialization.  These systems tend to run CPU-bound, and thus
 481           are not helped by synchronized interrupts, and thus tend to
 482           skew them, which reduces lock contention enough that large
 483           leaf-level fanouts work well.
 484
 485           Select a specific number if testing RCU itself.
 486
 487           Select the maximum permissible value for large systems.
 488
 489           Take the default if unsure.
 490
 491 config RCU_FANOUT_EXACT
 492         bool "Disable tree-based hierarchical RCU auto-balancing"
 493         depends on TREE_RCU || TREE_PREEMPT_RCU
 494         default n
 495         help
 496           This option forces use of the exact RCU_FANOUT value specified,
 497           regardless of imbalances in the hierarchy.  This is useful for
 498           testing RCU itself, and might one day be useful on systems with
 499           strong NUMA behavior.
 500
 501           Without RCU_FANOUT_EXACT, the code will balance the hierarchy.
 502
 503           Say N if unsure.
 504
 505 config RCU_FAST_NO_HZ
 506         bool "Accelerate last non-dyntick-idle CPU's grace periods"
 507         depends on NO_HZ && SMP
 508         default n
 509         help
 510           This option causes RCU to attempt to accelerate grace periods
 511           in order to allow CPUs to enter dynticks-idle state more
 512           quickly.  On the other hand, this option increases the overhead
 513           of the dynticks-idle checking, particularly on systems with
 514           large numbers of CPUs.
 515
 516           Say Y if energy efficiency is critically important, particularly
 517                 if you have relatively few CPUs.
 518
 519           Say N if you are unsure.
 520
 521 config TREE_RCU_TRACE
 522         def_bool RCU_TRACE && ( TREE_RCU || TREE_PREEMPT_RCU )
 523         select DEBUG_FS
 524         help
 525           This option provides tracing for the TREE_RCU and
 526           TREE_PREEMPT_RCU implementations, permitting Makefile to
 527           trivially select kernel/rcutree_trace.c.
 528
 529 config RCU_BOOST
 530         bool "Enable RCU priority boosting"
 531         depends on RT_MUTEXES && PREEMPT_RCU
 532         default n
 533         help
 534           This option boosts the priority of preempted RCU readers that
 535           block the current preemptible RCU grace period for too long.
 536           This option also prevents heavy loads from blocking RCU
 537           callback invocation for all flavors of RCU.
 538
 539           Say Y here if you are working with real-time apps or heavy loads
 540           Say N here if you are unsure.
 541
 542 config RCU_BOOST_PRIO
 543         int "Real-time priority to boost RCU readers to"
 544         range 1 99
 545         depends on RCU_BOOST
 546         default 1
 547         help
 548           This option specifies the real-time priority to which long-term
 549           preempted RCU readers are to be boosted.  If you are working
 550           with a real-time application that has one or more CPU-bound
 551           threads running at a real-time priority level, you should set
 552           RCU_BOOST_PRIO to a priority higher then the highest-priority
 553           real-time CPU-bound thread.  The default RCU_BOOST_PRIO value
 554           of 1 is appropriate in the common case, which is real-time
 555           applications that do not have any CPU-bound threads.
 556
 557           Some real-time applications might not have a single real-time
 558           thread that saturates a given CPU, but instead might have
 559           multiple real-time threads that, taken together, fully utilize
 560           that CPU.  In this case, you should set RCU_BOOST_PRIO to
 561           a priority higher than the lowest-priority thread that is
 562           conspiring to prevent the CPU from running any non-real-time
 563           tasks.  For example, if one thread at priority 10 and another
 564           thread at priority 5 are between themselves fully consuming
 565           the CPU time on a given CPU, then RCU_BOOST_PRIO should be
 566           set to priority 6 or higher.
 567
 568           Specify the real-time priority, or take the default if unsure.
 569
 570 config RCU_BOOST_DELAY
 571         int "Milliseconds to delay boosting after RCU grace-period start"
 572         range 0 3000
 573         depends on RCU_BOOST
 574         default 500
 575         help
 576           This option specifies the time to wait after the beginning of
 577           a given grace period before priority-boosting preempted RCU
 578           readers blocking that grace period.  Note that any RCU reader
 579           blocking an expedited RCU grace period is boosted immediately.
 580
 581           Accept the default if unsure.
 582
 583 endmenu # "RCU Subsystem"
 584
 585 config IKCONFIG
 586         tristate "Kernel .config support"
 587         ---help---
 588           This option enables the complete Linux kernel ".config" file
 589           contents to be saved in the kernel. It provides documentation
 590           of which kernel options are used in a running kernel or in an
 591           on-disk kernel.  This information can be extracted from the kernel
 592           image file with the script scripts/extract-ikconfig and used as
 593           input to rebuild the current kernel or to build another kernel.
 594           It can also be extracted from a running kernel by reading
 595           /proc/config.gz if enabled (below).
 596
 597 config IKCONFIG_PROC
 598         bool "Enable access to .config through /proc/config.gz"
 599         depends on IKCONFIG && PROC_FS
 600         ---help---
 601           This option enables access to the kernel configuration file
 602           through /proc/config.gz.
 603
 604 config LOG_BUF_SHIFT
 605         int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
 606         range 12 21
 607         default 17
 608         help
 609           Select kernel log buffer size as a power of 2.
 610           Examples:
 611                      17 => 128 KB
 612                      16 => 64 KB
 613                      15 => 32 KB
 614                      14 => 16 KB
 615                      13 =>  8 KB
 616                      12 =>  4 KB
 617
 618 #
 619 # Architectures with an unreliable sched_clock() should select this:
 620 #
 621 config HAVE_UNSTABLE_SCHED_CLOCK
 622         bool
 623
 624 menuconfig CGROUPS
 625         boolean "Control Group support"
 626         depends on EVENTFD
 627         help
 628           This option adds support for grouping sets of processes together, for
 629           use with process control subsystems such as Cpusets, CFS, memory
 630           controls or device isolation.
 631           See
 632                 - Documentation/scheduler/sched-design-CFS.txt  (CFS)
 633                 - Documentation/cgroups/ (features for grouping, isolation
 634                                           and resource control)
 635
 636           Say N if unsure.
 637
 638 if CGROUPS
 639
 640 config CGROUP_DEBUG
 641         bool "Example debug cgroup subsystem"
 642         default n
 643         help
 644           This option enables a simple cgroup subsystem that
 645           exports useful debugging information about the cgroups
 646           framework.
 647
 648           Say N if unsure.
 649
 650 config CGROUP_FREEZER
 651         bool "Freezer cgroup subsystem"
 652         help
 653           Provides a way to freeze and unfreeze all tasks in a
 654           cgroup.
 655
 656 config CGROUP_DEVICE
 657         bool "Device controller for cgroups"
 658         help
 659           Provides a cgroup implementing whitelists for devices which
 660           a process in the cgroup can mknod or open.
 661
 662 config CPUSETS
 663         bool "Cpuset support"
 664         help
 665           This option will let you create and manage CPUSETs which
 666           allow dynamically partitioning a system into sets of CPUs and
 667           Memory Nodes and assigning tasks to run only within those sets.
 668           This is primarily useful on large SMP or NUMA systems.
 669
 670           Say N if unsure.
 671
 672 config PROC_PID_CPUSET
 673         bool "Include legacy /proc/<pid>/cpuset file"
 674         depends on CPUSETS
 675         default y
 676
 677 config CGROUP_CPUACCT
 678         bool "Simple CPU accounting cgroup subsystem"
 679         help
 680           Provides a simple Resource Controller for monitoring the
 681           total CPU consumed by the tasks in a cgroup.
 682
 683 config RESOURCE_COUNTERS
 684         bool "Resource counters"
 685         help
 686           This option enables controller independent resource accounting
 687           infrastructure that works with cgroups.
 688
 689 config MEMCG
 690         bool "Memory Resource Controller for Control Groups"
 691         depends on RESOURCE_COUNTERS
 692         select MM_OWNER
 693         help
 694           Provides a memory resource controller that manages both anonymous
 695           memory and page cache. (See Documentation/cgroups/memory.txt)
 696
 697           Note that setting this option increases fixed memory overhead
 698           associated with each page of memory in the system. By this,
 699           20(40)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
 700           usage tracking struct at boot. Total amount of this is printed out
 701           at boot.
 702
 703           Only enable when you're ok with these trade offs and really
 704           sure you need the memory resource controller. Even when you enable
 705           this, you can set "cgroup_disable=memory" at your boot option to
 706           disable memory resource controller and you can avoid overheads.
 707           (and lose benefits of memory resource controller)
 708
 709           This config option also selects MM_OWNER config option, which
 710           could in turn add some fork/exit overhead.
 711
 712 config MEMCG_SWAP
 713         bool "Memory Resource Controller Swap Extension"
 714         depends on MEMCG && SWAP
 715         help
 716           Add swap management feature to memory resource controller. When you
 717           enable this, you can limit mem+swap usage per cgroup. In other words,
 718           when you disable this, memory resource controller has no cares to
 719           usage of swap...a process can exhaust all of the swap. This extension
 720           is useful when you want to avoid exhaustion swap but this itself
 721           adds more overheads and consumes memory for remembering information.
 722           Especially if you use 32bit system or small memory system, please
 723           be careful about enabling this. When memory resource controller
 724           is disabled by boot option, this will be automatically disabled and
 725           there will be no overhead from this. Even when you set this config=y,
 726           if boot option "swapaccount=0" is set, swap will not be accounted.
 727           Now, memory usage of swap_cgroup is 2 bytes per entry. If swap page
 728           size is 4096bytes, 512k per 1Gbytes of swap.
 729 config MEMCG_SWAP_ENABLED
 730         bool "Memory Resource Controller Swap Extension enabled by default"
 731         depends on MEMCG_SWAP
 732         default y
 733         help
 734           Memory Resource Controller Swap Extension comes with its price in
 735           a bigger memory consumption. General purpose distribution kernels
 736           which want to enable the feature but keep it disabled by default
 737           and let the user enable it by swapaccount boot command line
 738           parameter should have this option unselected.
 739           For those who want to have the feature enabled by default should
 740           select this option (if, for some reason, they need to disable it
 741           then swapaccount=0 does the trick).
 742 config MEMCG_KMEM
 743         bool "Memory Resource Controller Kernel Memory accounting (EXPERIMENTAL)"
 744         depends on MEMCG && EXPERIMENTAL
 745         default n
 746         help
 747           The Kernel Memory extension for Memory Resource Controller can limit
 748           the amount of memory used by kernel objects in the system. Those are
 749           fundamentally different from the entities handled by the standard
 750           Memory Controller, which are page-based, and can be swapped. Users of
 751           the kmem extension can use it to guarantee that no group of processes
 752           will ever exhaust kernel resources alone.
 753
 754 config CGROUP_HUGETLB
 755         bool "HugeTLB Resource Controller for Control Groups"
 756         depends on RESOURCE_COUNTERS && HUGETLB_PAGE && EXPERIMENTAL
 757         default n
 758         help
 759           Provides a cgroup Resource Controller for HugeTLB pages.
 760           When you enable this, you can put a per cgroup limit on HugeTLB usage.
 761           The limit is enforced during page fault. Since HugeTLB doesn't
 762           support page reclaim, enforcing the limit at page fault time implies
 763           that, the application will get SIGBUS signal if it tries to access
 764           HugeTLB pages beyond its limit. This requires the application to know
 765           beforehand how much HugeTLB pages it would require for its use. The
 766           control group is tracked in the third page lru pointer. This means
 767           that we cannot use the controller with huge page less than 3 pages.
 768
 769 config CGROUP_PERF
 770         bool "Enable perf_event per-cpu per-container group (cgroup) monitoring"
 771         depends on PERF_EVENTS && CGROUPS
 772         help
 773           This option extends the per-cpu mode to restrict monitoring to
 774           threads which belong to the cgroup specified and run on the
 775           designated cpu.
 776
 777           Say N if unsure.
 778
 779 menuconfig CGROUP_SCHED
 780         bool "Group CPU scheduler"
 781         default n
 782         help
 783           This feature lets CPU scheduler recognize task groups and control CPU
 784           bandwidth allocation to such task groups. It uses cgroups to group
 785           tasks.
 786
 787 if CGROUP_SCHED
 788 config FAIR_GROUP_SCHED
 789         bool "Group scheduling for SCHED_OTHER"
 790         depends on CGROUP_SCHED
 791         default CGROUP_SCHED
 792
 793 config CFS_BANDWIDTH
 794         bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED"
 795         depends on EXPERIMENTAL
 796         depends on FAIR_GROUP_SCHED
 797         default n
 798         help
 799           This option allows users to define CPU bandwidth rates (limits) for
 800           tasks running within the fair group scheduler.  Groups with no limit
 801           set are considered to be unconstrained and will run with no
 802           restriction.
 803           See tip/Documentation/scheduler/sched-bwc.txt for more information.
 804
 805 config RT_GROUP_SCHED
 806         bool "Group scheduling for SCHED_RR/FIFO"
 807         depends on EXPERIMENTAL
 808         depends on CGROUP_SCHED
 809         default n
 810         help
 811           This feature lets you explicitly allocate real CPU bandwidth
 812           to task groups. If enabled, it will also make it impossible to
 813           schedule realtime tasks for non-root users until you allocate
 814           realtime bandwidth for them.
 815           See Documentation/scheduler/sched-rt-group.txt for more information.
 816
 817 endif #CGROUP_SCHED
 818
 819 config BLK_CGROUP
 820         bool "Block IO controller"
 821         depends on BLOCK
 822         default n
 823         ---help---
 824         Generic block IO controller cgroup interface. This is the common
 825         cgroup interface which should be used by various IO controlling
 826         policies.
 827
 828         Currently, CFQ IO scheduler uses it to recognize task groups and
 829         control disk bandwidth allocation (proportional time slice allocation)
 830         to such task groups. It is also used by bio throttling logic in
 831         block layer to implement upper limit in IO rates on a device.
 832
 833         This option only enables generic Block IO controller infrastructure.
 834         One needs to also enable actual IO controlling logic/policy. For
 835         enabling proportional weight division of disk bandwidth in CFQ, set
 836         CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set
 837         CONFIG_BLK_DEV_THROTTLING=y.
 838
 839         See Documentation/cgroups/blkio-controller.txt for more information.
 840
 841 config DEBUG_BLK_CGROUP
 842         bool "Enable Block IO controller debugging"
 843         depends on BLK_CGROUP
 844         default n
 845         ---help---
 846         Enable some debugging help. Currently it exports additional stat
 847         files in a cgroup which can be useful for debugging.
 848
 849 endif # CGROUPS
 850
 851 config CHECKPOINT_RESTORE
 852         bool "Checkpoint/restore support" if EXPERT
 853         default n
 854         help
 855           Enables additional kernel features in a sake of checkpoint/restore.
 856           In particular it adds auxiliary prctl codes to setup process text,
 857           data and heap segment sizes, and a few additional /proc filesystem
 858           entries.
 859
 860           If unsure, say N here.
 861
 862 menuconfig NAMESPACES
 863         bool "Namespaces support" if EXPERT
 864         default !EXPERT
 865         help
 866           Provides the way to make tasks work with different objects using
 867           the same id. For example same IPC id may refer to different objects
 868           or same user id or pid may refer to different tasks when used in
 869           different namespaces.
 870
 871 if NAMESPACES
 872
 873 config UTS_NS
 874         bool "UTS namespace"
 875         default y
 876         help
 877           In this namespace tasks see different info provided with the
 878           uname() system call
 879
 880 config IPC_NS
 881         bool "IPC namespace"
 882         depends on (SYSVIPC || POSIX_MQUEUE)
 883         default y
 884         help
 885           In this namespace tasks work with IPC ids which correspond to
 886           different IPC objects in different namespaces.
 887
 888 config USER_NS
 889         bool "User namespace (EXPERIMENTAL)"
 890         depends on EXPERIMENTAL
 891         depends on UIDGID_CONVERTED
 892         select UIDGID_STRICT_TYPE_CHECKS
 893
 894         default n
 895         help
 896           This allows containers, i.e. vservers, to use user namespaces
 897           to provide different user info for different servers.
 898           If unsure, say N.
 899
 900 config PID_NS
 901         bool "PID Namespaces"
 902         default y
 903         help
 904           Support process id namespaces.  This allows having multiple
 905           processes with the same pid as long as they are in different
 906           pid namespaces.  This is a building block of containers.
 907
 908 config NET_NS
 909         bool "Network namespace"
 910         depends on NET
 911         default y
 912         help
 913           Allow user space to create what appear to be multiple instances
 914           of the network stack.
 915
 916 endif # NAMESPACES
 917
 918 config UIDGID_CONVERTED
 919         # True if all of the selected software conmponents are known
 920         # to have uid_t and gid_t converted to kuid_t and kgid_t
 921         # where appropriate and are otherwise safe to use with
 922         # the user namespace.
 923         bool
 924         default y
 925
 926         # List of kernel pieces that need user namespace work
 927         # Features
 928         depends on IMA = n
 929         depends on EVM = n
 930         depends on KEYS = n
 931         depends on AUDIT = n
 932         depends on AUDITSYSCALL = n
 933         depends on TASKSTATS = n
 934         depends on TRACING = n
 935         depends on FS_POSIX_ACL = n
 936         depends on QUOTA = n
 937         depends on QUOTACTL = n
 938         depends on BSD_PROCESS_ACCT = n
 939         depends on DRM = n
 940
 941         # Networking
 942         depends on NET_9P = n
 943         depends on AF_RXRPC = n
 944         depends on DNS_RESOLVER = n
 945
 946         # Filesystems
 947         depends on USB_GADGETFS = n
 948         depends on USB_FUNCTIONFS = n
 949         depends on DEVTMPFS = n
 950         depends on XENFS = n
 951
 952         depends on 9P_FS = n
 953         depends on ADFS_FS = n
 954         depends on AFFS_FS = n
 955         depends on AFS_FS = n
 956         depends on AUTOFS4_FS = n
 957         depends on BEFS_FS = n
 958         depends on BFS_FS = n
 959         depends on BTRFS_FS = n
 960         depends on CEPH_FS = n
 961         depends on CIFS = n
 962         depends on CODA_FS = n
 963         depends on CONFIGFS_FS = n
 964         depends on CRAMFS = n
 965         depends on ECRYPT_FS = n
 966         depends on EFS_FS = n
 967         depends on EXOFS_FS = n
 968         depends on FAT_FS = n
 969         depends on FUSE_FS = n
 970         depends on GFS2_FS = n
 971         depends on HFS_FS = n
 972         depends on HFSPLUS_FS = n
 973         depends on HPFS_FS = n
 974         depends on HUGETLBFS = n
 975         depends on ISO9660_FS = n
 976         depends on JFFS2_FS = n
 977         depends on JFS_FS = n
 978         depends on LOGFS = n
 979         depends on MINIX_FS = n
 980         depends on NCP_FS = n
 981         depends on NFSD = n
 982         depends on NFS_FS = n
 983         depends on NILFS2_FS = n
 984         depends on NTFS_FS = n
 985         depends on OCFS2_FS = n
 986         depends on OMFS_FS = n
 987         depends on QNX4FS_FS = n
 988         depends on QNX6FS_FS = n
 989         depends on REISERFS_FS = n
 990         depends on SQUASHFS = n
 991         depends on SYSV_FS = n
 992         depends on UBIFS_FS = n
 993         depends on UDF_FS = n
 994         depends on UFS_FS = n
 995         depends on VXFS_FS = n
 996         depends on XFS_FS = n
 997
 998         depends on !UML || HOSTFS = n
 999
1000         # The rare drivers that won't build
1001         depends on INFINIBAND_QIB = n
1002         depends on BLK_DEV_LOOP = n
1003         depends on ANDROID_BINDER_IPC = n
1004
1005         # Security modules
1006         depends on SECURITY_TOMOYO = n
1007         depends on SECURITY_APPARMOR = n
1008
1009 config UIDGID_STRICT_TYPE_CHECKS
1010         bool "Require conversions between uid/gids and their internal representation"
1011         depends on UIDGID_CONVERTED
1012         default n
1013         help
1014          While the nececessary conversions are being added to all subsystems this option allows
1015          the code to continue to build for unconverted subsystems.
1016
1017          Say Y here if you want the strict type checking enabled
1018
1019 config SCHED_AUTOGROUP
1020         bool "Automatic process group scheduling"
1021         select EVENTFD
1022         select CGROUPS
1023         select CGROUP_SCHED
1024         select FAIR_GROUP_SCHED
1025         help
1026           This option optimizes the scheduler for common desktop workloads by
1027           automatically creating and populating task groups.  This separation
1028           of workloads isolates aggressive CPU burners (like build jobs) from
1029           desktop applications.  Task group autogeneration is currently based
1030           upon task session.
1031
1032 config MM_OWNER
1033         bool
1034
1035 config SYSFS_DEPRECATED
1036         bool "Enable deprecated sysfs features to support old userspace tools"
1037         depends on SYSFS
1038         default n
1039         help
1040           This option adds code that switches the layout of the "block" class
1041           devices, to not show up in /sys/class/block/, but only in
1042           /sys/block/.
1043
1044           This switch is only active when the sysfs.deprecated=1 boot option is
1045           passed or the SYSFS_DEPRECATED_V2 option is set.
1046
1047           This option allows new kernels to run on old distributions and tools,
1048           which might get confused by /sys/class/block/. Since 2007/2008 all
1049           major distributions and tools handle this just fine.
1050
1051           Recent distributions and userspace tools after 2009/2010 depend on
1052           the existence of /sys/class/block/, and will not work with this
1053           option enabled.
1054
1055           Only if you are using a new kernel on an old distribution, you might
1056           need to say Y here.
1057
1058 config SYSFS_DEPRECATED_V2
1059         bool "Enable deprecated sysfs features by default"
1060         default n
1061         depends on SYSFS
1062         depends on SYSFS_DEPRECATED
1063         help
1064           Enable deprecated sysfs by default.
1065
1066           See the CONFIG_SYSFS_DEPRECATED option for more details about this
1067           option.
1068
1069           Only if you are using a new kernel on an old distribution, you might
1070           need to say Y here. Even then, odds are you would not need it
1071           enabled, you can always pass the boot option if absolutely necessary.
1072
1073 config RELAY
1074         bool "Kernel->user space relay support (formerly relayfs)"
1075         help
1076           This option enables support for relay interface support in
1077           certain file systems (such as debugfs).
1078           It is designed to provide an efficient mechanism for tools and
1079           facilities to relay large amounts of data from kernel space to
1080           user space.
1081
1082           If unsure, say N.
1083
1084 config BLK_DEV_INITRD
1085         bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
1086         depends on BROKEN || !FRV
1087         help
1088           The initial RAM filesystem is a ramfs which is loaded by the
1089           boot loader (loadlin or lilo) and that is mounted as root
1090           before the normal boot procedure. It is typically used to
1091           load modules needed to mount the "real" root file system,
1092           etc. See <file:Documentation/initrd.txt> for details.
1093
1094           If RAM disk support (BLK_DEV_RAM) is also included, this
1095           also enables initial RAM disk (initrd) support and adds
1096           15 Kbytes (more on some other architectures) to the kernel size.
1097
1098           If unsure say Y.
1099
1100 if BLK_DEV_INITRD
1101
1102 source "usr/Kconfig"
1103
1104 endif
1105
1106 config CC_OPTIMIZE_FOR_SIZE
1107         bool "Optimize for size"
1108         help
1109           Enabling this option will pass "-Os" instead of "-O2" to gcc
1110           resulting in a smaller kernel.
1111
1112           If unsure, say Y.
1113
1114 config SYSCTL
1115         bool
1116
1117 config ANON_INODES
1118         bool
1119
1120 menuconfig EXPERT
1121         bool "Configure standard kernel features (expert users)"
1122         # Unhide debug options, to make the on-by-default options visible
1123         select DEBUG_KERNEL
1124         help
1125           This option allows certain base kernel options and settings
1126           to be disabled or tweaked. This is for specialized
1127           environments which can tolerate a "non-standard" kernel.
1128           Only use this if you really know what you are doing.
1129
1130 config UID16
1131         bool "Enable 16-bit UID system calls" if EXPERT
1132         depends on ARM || BLACKFIN || CRIS || FRV || H8300 || X86_32 || M68K || (S390 && !64BIT) || SUPERH || SPARC32 || (SPARC64 && COMPAT) || UML || (X86_64 && IA32_EMULATION)
1133         default y
1134         help
1135           This enables the legacy 16-bit UID syscall wrappers.
1136
1137 config SYSCTL_SYSCALL
1138         bool "Sysctl syscall support" if EXPERT
1139         depends on PROC_SYSCTL
1140         default n
1141         select SYSCTL
1142         ---help---
1143           sys_sysctl uses binary paths that have been found challenging
1144           to properly maintain and use.  The interface in /proc/sys
1145           using paths with ascii names is now the primary path to this
1146           information.
1147
1148           Almost nothing using the binary sysctl interface so if you are
1149           trying to save some space it is probably safe to disable this,
1150           making your kernel marginally smaller.
1151
1152           If unsure say N here.
1153
1154 config KALLSYMS
1155          bool "Load all symbols for debugging/ksymoops" if EXPERT
1156          default y
1157          help
1158            Say Y here to let the kernel print out symbolic crash information and
1159            symbolic stack backtraces. This increases the size of the kernel
1160            somewhat, as all symbols have to be loaded into the kernel image.
1161
1162 config KALLSYMS_ALL
1163         bool "Include all symbols in kallsyms"
1164         depends on DEBUG_KERNEL && KALLSYMS
1165         help
1166            Normally kallsyms only contains the symbols of functions for nicer
1167            OOPS messages and backtraces (i.e., symbols from the text and inittext
1168            sections). This is sufficient for most cases. And only in very rare
1169            cases (e.g., when a debugger is used) all symbols are required (e.g.,
1170            names of variables from the data sections, etc).
1171
1172            This option makes sure that all symbols are loaded into the kernel
1173            image (i.e., symbols from all sections) in cost of increased kernel
1174            size (depending on the kernel configuration, it may be 300KiB or
1175            something like this).
1176
1177            Say N unless you really need all symbols.
1178
1179 config HOTPLUG
1180         bool "Support for hot-pluggable devices" if EXPERT
1181         default y
1182         help
1183           This option is provided for the case where no hotplug or uevent
1184           capabilities is wanted by the kernel.  You should only consider
1185           disabling this option for embedded systems that do not use modules, a
1186           dynamic /dev tree, or dynamic device discovery.  Just say Y.
1187
1188 config PRINTK
1189         default y
1190         bool "Enable support for printk" if EXPERT
1191         help
1192           This option enables normal printk support. Removing it
1193           eliminates most of the message strings from the kernel image
1194           and makes the kernel more or less silent. As this makes it
1195           very difficult to diagnose system problems, saying N here is
1196           strongly discouraged.
1197
1198 config BUG
1199         bool "BUG() support" if EXPERT
1200         default y
1201         help
1202           Disabling this option eliminates support for BUG and WARN, reducing
1203           the size of your kernel image and potentially quietly ignoring
1204           numerous fatal conditions. You should only consider disabling this
1205           option for embedded systems with no facilities for reporting errors.
1206           Just say Y.
1207
1208 config ELF_CORE
1209         default y
1210         bool "Enable ELF core dumps" if EXPERT
1211         help
1212           Enable support for generating core dumps. Disabling saves about 4k.
1213
1214
1215 config PCSPKR_PLATFORM
1216         bool "Enable PC-Speaker support" if EXPERT
1217         depends on HAVE_PCSPKR_PLATFORM
1218         select I8253_LOCK
1219         default y
1220         help
1221           This option allows to disable the internal PC-Speaker
1222           support, saving some memory.
1223
1224 config HAVE_PCSPKR_PLATFORM
1225         bool
1226
1227 config BASE_FULL
1228         default y
1229         bool "Enable full-sized data structures for core" if EXPERT
1230         help
1231           Disabling this option reduces the size of miscellaneous core
1232           kernel data structures. This saves memory on small machines,
1233           but may reduce performance.
1234
1235 config FUTEX
1236         bool "Enable futex support" if EXPERT
1237         default y
1238         select RT_MUTEXES
1239         help
1240           Disabling this option will cause the kernel to be built without
1241           support for "fast userspace mutexes".  The resulting kernel may not
1242           run glibc-based applications correctly.
1243
1244 config EPOLL
1245         bool "Enable eventpoll support" if EXPERT
1246         default y
1247         select ANON_INODES
1248         help
1249           Disabling this option will cause the kernel to be built without
1250           support for epoll family of system calls.
1251
1252 config SIGNALFD
1253         bool "Enable signalfd() system call" if EXPERT
1254         select ANON_INODES
1255         default y
1256         help
1257           Enable the signalfd() system call that allows to receive signals
1258           on a file descriptor.
1259
1260           If unsure, say Y.
1261
1262 config TIMERFD
1263         bool "Enable timerfd() system call" if EXPERT
1264         select ANON_INODES
1265         default y
1266         help
1267           Enable the timerfd() system call that allows to receive timer
1268           events on a file descriptor.
1269
1270           If unsure, say Y.
1271
1272 config EVENTFD
1273         bool "Enable eventfd() system call" if EXPERT
1274         select ANON_INODES
1275         default y
1276         help
1277           Enable the eventfd() system call that allows to receive both
1278           kernel notification (ie. KAIO) or userspace notifications.
1279
1280           If unsure, say Y.
1281
1282 config SHMEM
1283         bool "Use full shmem filesystem" if EXPERT
1284         default y
1285         depends on MMU
1286         help
1287           The shmem is an internal filesystem used to manage shared memory.
1288           It is backed by swap and manages resource limits. It is also exported
1289           to userspace as tmpfs if TMPFS is enabled. Disabling this
1290           option replaces shmem and tmpfs with the much simpler ramfs code,
1291           which may be appropriate on small systems without swap.
1292
1293 config AIO
1294         bool "Enable AIO support" if EXPERT
1295         default y
1296         help
1297           This option enables POSIX asynchronous I/O which may by used
1298           by some high performance threaded applications. Disabling
1299           this option saves about 7k.
1300
1301 config EMBEDDED
1302         bool "Embedded system"
1303         select EXPERT
1304         help
1305           This option should be enabled if compiling the kernel for
1306           an embedded system so certain expert options are available
1307           for configuration.
1308
1309 config HAVE_PERF_EVENTS
1310         bool
1311         help
1312           See tools/perf/design.txt for details.
1313
1314 config PERF_USE_VMALLOC
1315         bool
1316         help
1317           See tools/perf/design.txt for details
1318
1319 menu "Kernel Performance Events And Counters"
1320
1321 config PERF_EVENTS
1322         bool "Kernel performance events and counters"
1323         default y if PROFILING
1324         depends on HAVE_PERF_EVENTS
1325         select ANON_INODES
1326         select IRQ_WORK
1327         help
1328           Enable kernel support for various performance events provided
1329           by software and hardware.
1330
1331           Software events are supported either built-in or via the
1332           use of generic tracepoints.
1333
1334           Most modern CPUs support performance events via performance
1335           counter registers. These registers count the number of certain
1336           types of hw events: such as instructions executed, cachemisses
1337           suffered, or branches mis-predicted - without slowing down the
1338           kernel or applications. These registers can also trigger interrupts
1339           when a threshold number of events have passed - and can thus be
1340           used to profile the code that runs on that CPU.
1341
1342           The Linux Performance Event subsystem provides an abstraction of
1343           these software and hardware event capabilities, available via a
1344           system call and used by the "perf" utility in tools/perf/. It
1345           provides per task and per CPU counters, and it provides event
1346           capabilities on top of those.
1347
1348           Say Y if unsure.
1349
1350 config DEBUG_PERF_USE_VMALLOC
1351         default n
1352         bool "Debug: use vmalloc to back perf mmap() buffers"
1353         depends on PERF_EVENTS && DEBUG_KERNEL
1354         select PERF_USE_VMALLOC
1355         help
1356          Use vmalloc memory to back perf mmap() buffers.
1357
1358          Mostly useful for debugging the vmalloc code on platforms
1359          that don't require it.
1360
1361          Say N if unsure.
1362
1363 endmenu
1364
1365 config VM_EVENT_COUNTERS
1366         default y
1367         bool "Enable VM event counters for /proc/vmstat" if EXPERT
1368         help
1369           VM event counters are needed for event counts to be shown.
1370           This option allows the disabling of the VM event counters
1371           on EXPERT systems.  /proc/vmstat will only show page counts
1372           if VM event counters are disabled.
1373
1374 config PCI_QUIRKS
1375         default y
1376         bool "Enable PCI quirk workarounds" if EXPERT
1377         depends on PCI
1378         help
1379           This enables workarounds for various PCI chipset
1380           bugs/quirks. Disable this only if your target machine is
1381           unaffected by PCI quirks.
1382
1383 config SLUB_DEBUG
1384         default y
1385         bool "Enable SLUB debugging support" if EXPERT
1386         depends on SLUB && SYSFS
1387         help
1388           SLUB has extensive debug support features. Disabling these can
1389           result in significant savings in code size. This also disables
1390           SLUB sysfs support. /sys/slab will not exist and there will be
1391           no support for cache validation etc.
1392
1393 config COMPAT_BRK
1394         bool "Disable heap randomization"
1395         default y
1396         help
1397           Randomizing heap placement makes heap exploits harder, but it
1398           also breaks ancient binaries (including anything libc5 based).
1399           This option changes the bootup default to heap randomization
1400           disabled, and can be overridden at runtime by setting
1401           /proc/sys/kernel/randomize_va_space to 2.
1402
1403           On non-ancient distros (post-2000 ones) N is usually a safe choice.
1404
1405 choice
1406         prompt "Choose SLAB allocator"
1407         default SLUB
1408         help
1409            This option allows to select a slab allocator.
1410
1411 config SLAB
1412         bool "SLAB"
1413         help
1414           The regular slab allocator that is established and known to work
1415           well in all environments. It organizes cache hot objects in
1416           per cpu and per node queues.
1417
1418 config SLUB
1419         bool "SLUB (Unqueued Allocator)"
1420         help
1421            SLUB is a slab allocator that minimizes cache line usage
1422            instead of managing queues of cached objects (SLAB approach).
1423            Per cpu caching is realized using slabs of objects instead
1424            of queues of objects. SLUB can use memory efficiently
1425            and has enhanced diagnostics. SLUB is the default choice for
1426            a slab allocator.
1427
1428 config SLOB
1429         depends on EXPERT
1430         bool "SLOB (Simple Allocator)"
1431         help
1432            SLOB replaces the stock allocator with a drastically simpler
1433            allocator. SLOB is generally more space efficient but
1434            does not perform as well on large systems.
1435
1436 endchoice
1437
1438 config MMAP_ALLOW_UNINITIALIZED
1439         bool "Allow mmapped anonymous memory to be uninitialized"
1440         depends on EXPERT && !MMU
1441         default n
1442         help
1443           Normally, and according to the Linux spec, anonymous memory obtained
1444           from mmap() has it's contents cleared before it is passed to
1445           userspace.  Enabling this config option allows you to request that
1446           mmap() skip that if it is given an MAP_UNINITIALIZED flag, thus
1447           providing a huge performance boost.  If this option is not enabled,
1448           then the flag will be ignored.
1449
1450           This is taken advantage of by uClibc's malloc(), and also by
1451           ELF-FDPIC binfmt's brk and stack allocator.
1452
1453           Because of the obvious security issues, this option should only be
1454           enabled on embedded devices where you control what is run in
1455           userspace.  Since that isn't generally a problem on no-MMU systems,
1456           it is normally safe to say Y here.
1457
1458           See Documentation/nommu-mmap.txt for more information.
1459
1460 config PROFILING
1461         bool "Profiling support"
1462         help
1463           Say Y here to enable the extended profiling support mechanisms used
1464           by profilers such as OProfile.
1465
1466 #
1467 # Place an empty function call at each tracepoint site. Can be
1468 # dynamically changed for a probe function.
1469 #
1470 config TRACEPOINTS
1471         bool
1472
1473 source "arch/Kconfig"
1474
1475 endmenu         # General setup
1476
1477 config HAVE_GENERIC_DMA_COHERENT
1478         bool
1479         default n
1480
1481 config SLABINFO
1482         bool
1483         depends on PROC_FS
1484         depends on SLAB || SLUB_DEBUG
1485         default y
1486
1487 config RT_MUTEXES
1488         boolean
1489
1490 config BASE_SMALL
1491         int
1492         default 0 if BASE_FULL
1493         default 1 if !BASE_FULL
1494
1495 menuconfig MODULES
1496         bool "Enable loadable module support"
1497         help
1498           Kernel modules are small pieces of compiled code which can
1499           be inserted in the running kernel, rather than being
1500           permanently built into the kernel.  You use the "modprobe"
1501           tool to add (and sometimes remove) them.  If you say Y here,
1502           many parts of the kernel can be built as modules (by
1503           answering M instead of Y where indicated): this is most
1504           useful for infrequently used options which are not required
1505           for booting.  For more information, see the man pages for
1506           modprobe, lsmod, modinfo, insmod and rmmod.
1507
1508           If you say Y here, you will need to run "make
1509           modules_install" to put the modules under /lib/modules/
1510           where modprobe can find them (you may need to be root to do
1511           this).
1512
1513           If unsure, say Y.
1514
1515 if MODULES
1516
1517 config MODULE_FORCE_LOAD
1518         bool "Forced module loading"
1519         default n
1520         help
1521           Allow loading of modules without version information (ie. modprobe
1522           --force).  Forced module loading sets the 'F' (forced) taint flag and
1523           is usually a really bad idea.
1524
1525 config MODULE_UNLOAD
1526         bool "Module unloading"
1527         help
1528           Without this option you will not be able to unload any
1529           modules (note that some modules may not be unloadable
1530           anyway), which makes your kernel smaller, faster
1531           and simpler.  If unsure, say Y.
1532
1533 config MODULE_FORCE_UNLOAD
1534         bool "Forced module unloading"
1535         depends on MODULE_UNLOAD && EXPERIMENTAL
1536         help
1537           This option allows you to force a module to unload, even if the
1538           kernel believes it is unsafe: the kernel will remove the module
1539           without waiting for anyone to stop using it (using the -f option to
1540           rmmod).  This is mainly for kernel developers and desperate users.
1541           If unsure, say N.
1542
1543 config MODVERSIONS
1544         bool "Module versioning support"
1545         help
1546           Usually, you have to use modules compiled with your kernel.
1547           Saying Y here makes it sometimes possible to use modules
1548           compiled for different kernels, by adding enough information
1549           to the modules to (hopefully) spot any changes which would
1550           make them incompatible with the kernel you are running.  If
1551           unsure, say N.
1552
1553 config MODULE_SRCVERSION_ALL
1554         bool "Source checksum for all modules"
1555         help
1556           Modules which contain a MODULE_VERSION get an extra "srcversion"
1557           field inserted into their modinfo section, which contains a
1558           sum of the source files which made it.  This helps maintainers
1559           see exactly which source was used to build a module (since
1560           others sometimes change the module source without updating
1561           the version).  With this option, such a "srcversion" field
1562           will be created for all modules.  If unsure, say N.
1563
1564 endif # MODULES
1565
1566 config INIT_ALL_POSSIBLE
1567         bool
1568         help
1569           Back when each arch used to define their own cpu_online_mask and
1570           cpu_possible_mask, some of them chose to initialize cpu_possible_mask
1571           with all 1s, and others with all 0s.  When they were centralised,
1572           it was better to provide this option than to break all the archs
1573           and have several arch maintainers pursuing me down dark alleys.
1574
1575 config STOP_MACHINE
1576         bool
1577         default y
1578         depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
1579         help
1580           Need stop_machine() primitive.
1581
1582 source "block/Kconfig"
1583
1584 config PREEMPT_NOTIFIERS
1585         bool
1586
1587 config PADATA
1588         depends on SMP
1589         bool
1590
1591 source "kernel/Kconfig.locks"