9 option env="KERNELVERSION"
15 default "/lib/modules/$UNAME_RELEASE/.config"
16 default "/etc/kernel-config"
17 default "/boot/config-$UNAME_RELEASE"
18 default "$ARCH_DEFCONFIG"
19 default "arch/$ARCH/defconfig"
24 bool "Prompt for development and/or incomplete code/drivers"
26 Some of the various things that Linux supports (such as network
27 drivers, file systems, network protocols, etc.) can be in a state
28 of development where the functionality, stability, or the level of
29 testing is not yet high enough for general use. This is usually
30 known as the "alpha-test" phase among developers. If a feature is
31 currently in alpha-test, then the developers usually discourage
32 uninformed widespread use of this feature by the general public to
33 avoid "Why doesn't this work?" type mail messages. However, active
34 testing and use of these systems is welcomed. Just be aware that it
35 may not meet the normal level of reliability or it may fail to work
36 in some special cases. Detailed bug reports from people familiar
37 with the kernel internals are usually welcomed by the developers
38 (before submitting bug reports, please read the documents
39 <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
40 <file:Documentation/BUG-HUNTING>, and
41 <file:Documentation/oops-tracing.txt> in the kernel source).
43 This option will also make obsoleted drivers available. These are
44 drivers that have been replaced by something else, and/or are
45 scheduled to be removed in a future kernel release.
47 Unless you intend to help test and develop a feature or driver that
48 falls into this category, or you have a situation that requires
49 using these features, you should probably say N here, which will
50 cause the configurator to present you with fewer choices. If
51 you say Y here, you will be offered the choice of using features or
52 drivers that are currently considered to be in the alpha-test phase.
59 depends on BROKEN || !SMP
64 depends on SMP || PREEMPT
67 config INIT_ENV_ARG_LIMIT
72 Maximum of each of the number of arguments and environment
73 variables passed to init from the kernel command line.
77 string "Local version - append to kernel release"
79 Append an extra string to the end of your kernel version.
80 This will show up when you type uname, for example.
81 The string you set here will be appended after the contents of
82 any files with a filename matching localversion* in your
83 object and source tree, in that order. Your total string can
84 be a maximum of 64 characters.
86 config LOCALVERSION_AUTO
87 bool "Automatically append version information to the version string"
90 This will try to automatically determine if the current tree is a
91 release tree by looking for git tags that belong to the current
94 A string of the format -gxxxxxxxx will be added to the localversion
95 if a git-based tree is found. The string generated by this will be
96 appended after any matching localversion* files, and after the value
97 set in CONFIG_LOCALVERSION.
99 (The actual string used here is the first eight characters produced
100 by running the command:
102 $ git rev-parse --verify HEAD
104 which is done within the script "scripts/setlocalversion".)
107 bool "Support for paging of anonymous memory (swap)"
108 depends on MMU && BLOCK
111 This option allows you to choose whether you want to have support
112 for so called swap devices or swap files in your kernel that are
113 used to provide more virtual memory than the actual RAM present
114 in your computer. If unsure say Y.
119 Inter Process Communication is a suite of library functions and
120 system calls which let processes (running programs) synchronize and
121 exchange information. It is generally considered to be a good thing,
122 and some programs won't run unless you say Y here. In particular, if
123 you want to run the DOS emulator dosemu under Linux (read the
124 DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>),
125 you'll need to say Y here.
127 You can find documentation about IPC with "info ipc" and also in
128 section 6.4 of the Linux Programmer's Guide, available from
129 <http://www.tldp.org/guides.html>.
131 config SYSVIPC_SYSCTL
138 bool "POSIX Message Queues"
139 depends on NET && EXPERIMENTAL
141 POSIX variant of message queues is a part of IPC. In POSIX message
142 queues every message has a priority which decides about succession
143 of receiving it by a process. If you want to compile and run
144 programs written e.g. for Solaris with use of its POSIX message
145 queues (functions mq_*) say Y here.
147 POSIX message queues are visible as a filesystem called 'mqueue'
148 and can be mounted somewhere if you want to do filesystem
149 operations on message queues.
153 config BSD_PROCESS_ACCT
154 bool "BSD Process Accounting"
156 If you say Y here, a user level program will be able to instruct the
157 kernel (via a special system call) to write process accounting
158 information to a file: whenever a process exits, information about
159 that process will be appended to the file by the kernel. The
160 information includes things such as creation time, owning user,
161 command name, memory usage, controlling terminal etc. (the complete
162 list is in the struct acct in <file:include/linux/acct.h>). It is
163 up to the user level program to do useful things with this
164 information. This is generally a good idea, so say Y.
166 config BSD_PROCESS_ACCT_V3
167 bool "BSD Process Accounting version 3 file format"
168 depends on BSD_PROCESS_ACCT
171 If you say Y here, the process accounting information is written
172 in a new file format that also logs the process IDs of each
173 process and it's parent. Note that this file format is incompatible
174 with previous v0/v1/v2 file formats, so you will need updated tools
175 for processing it. A preliminary version of these tools is available
176 at <http://www.gnu.org/software/acct/>.
179 bool "Export task/process statistics through netlink (EXPERIMENTAL)"
183 Export selected statistics for tasks/processes through the
184 generic netlink interface. Unlike BSD process accounting, the
185 statistics are available during the lifetime of tasks/processes as
186 responses to commands. Like BSD accounting, they are sent to user
191 config TASK_DELAY_ACCT
192 bool "Enable per-task delay accounting (EXPERIMENTAL)"
195 Collect information on time spent by a task waiting for system
196 resources like cpu, synchronous block I/O completion and swapping
197 in pages. Such statistics can help in setting a task's priorities
198 relative to other tasks for cpu, io, rss limits etc.
203 bool "Enable extended accounting over taskstats (EXPERIMENTAL)"
206 Collect extended task accounting data and send the data
207 to userland for processing over the taskstats interface.
211 config TASK_IO_ACCOUNTING
212 bool "Enable per-task storage I/O accounting (EXPERIMENTAL)"
213 depends on TASK_XACCT
215 Collect information on the number of bytes of storage I/O which this
221 bool "Auditing support"
224 Enable auditing infrastructure that can be used with another
225 kernel subsystem, such as SELinux (which requires this for
226 logging of avc messages output). Does not do system-call
227 auditing without CONFIG_AUDITSYSCALL.
230 bool "Enable system-call auditing support"
231 depends on AUDIT && (X86 || PPC || PPC64 || S390 || IA64 || UML || SPARC64|| SUPERH)
232 default y if SECURITY_SELINUX
234 Enable low-overhead system-call auditing infrastructure that
235 can be used independently or with another kernel subsystem,
236 such as SELinux. To use audit's filesystem watch feature, please
237 ensure that INOTIFY is configured.
241 depends on AUDITSYSCALL && INOTIFY
244 tristate "Kernel .config support"
246 This option enables the complete Linux kernel ".config" file
247 contents to be saved in the kernel. It provides documentation
248 of which kernel options are used in a running kernel or in an
249 on-disk kernel. This information can be extracted from the kernel
250 image file with the script scripts/extract-ikconfig and used as
251 input to rebuild the current kernel or to build another kernel.
252 It can also be extracted from a running kernel by reading
253 /proc/config.gz if enabled (below).
256 bool "Enable access to .config through /proc/config.gz"
257 depends on IKCONFIG && PROC_FS
259 This option enables access to the kernel configuration file
260 through /proc/config.gz.
263 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
267 Select kernel log buffer size as a power of 2.
277 bool "Control Group support"
279 This option will let you use process cgroup subsystems
285 bool "Example debug cgroup subsystem"
289 This option enables a simple cgroup subsystem that
290 exports useful debugging information about the cgroups
296 bool "Namespace cgroup subsystem"
299 Provides a simple namespace cgroup subsystem to
300 provide hierarchical naming of sets of namespaces,
301 for instance virtual servers and checkpoint/restart
304 config CGROUP_FREEZER
305 bool "control group freezer subsystem"
308 Provides a way to freeze and unfreeze all tasks in a
312 bool "Device controller for cgroups"
313 depends on CGROUPS && EXPERIMENTAL
315 Provides a cgroup implementing whitelists for devices which
316 a process in the cgroup can mknod or open.
319 bool "Cpuset support"
320 depends on SMP && CGROUPS
322 This option will let you create and manage CPUSETs which
323 allow dynamically partitioning a system into sets of CPUs and
324 Memory Nodes and assigning tasks to run only within those sets.
325 This is primarily useful on large SMP or NUMA systems.
330 # Architectures with an unreliable sched_clock() should select this:
332 config HAVE_UNSTABLE_SCHED_CLOCK
336 bool "Group CPU scheduler"
337 depends on EXPERIMENTAL
340 This feature lets CPU scheduler recognize task groups and control CPU
341 bandwidth allocation to such task groups.
343 config FAIR_GROUP_SCHED
344 bool "Group scheduling for SCHED_OTHER"
345 depends on GROUP_SCHED
348 config RT_GROUP_SCHED
349 bool "Group scheduling for SCHED_RR/FIFO"
350 depends on EXPERIMENTAL
351 depends on GROUP_SCHED
354 This feature lets you explicitly allocate real CPU bandwidth
355 to users or control groups (depending on the "Basis for grouping tasks"
356 setting below. If enabled, it will also make it impossible to
357 schedule realtime tasks for non-root users until you allocate
358 realtime bandwidth for them.
359 See Documentation/scheduler/sched-rt-group.txt for more information.
362 depends on GROUP_SCHED
363 prompt "Basis for grouping tasks"
369 This option will choose userid as the basis for grouping
370 tasks, thus providing equal CPU bandwidth to each user.
373 bool "Control groups"
376 This option allows you to create arbitrary task groups
377 using the "cgroup" pseudo filesystem and control
378 the cpu bandwidth allocated to each such task group.
379 Refer to Documentation/cgroups.txt for more information
380 on "cgroup" pseudo filesystem.
384 config CGROUP_CPUACCT
385 bool "Simple CPU accounting cgroup subsystem"
388 Provides a simple Resource Controller for monitoring the
389 total CPU consumed by the tasks in a cgroup
391 config RESOURCE_COUNTERS
392 bool "Resource counters"
394 This option enables controller independent resource accounting
395 infrastructure that works with cgroups
401 config CGROUP_MEM_RES_CTLR
402 bool "Memory Resource Controller for Control Groups"
403 depends on CGROUPS && RESOURCE_COUNTERS
406 Provides a memory resource controller that manages both anonymous
407 memory and page cache. (See Documentation/controllers/memory.txt)
409 Note that setting this option increases fixed memory overhead
410 associated with each page of memory in the system. By this,
411 20(40)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
412 usage tracking struct at boot. Total amount of this is printed out
415 Only enable when you're ok with these trade offs and really
416 sure you need the memory resource controller. Even when you enable
417 this, you can set "cgroup_disable=memory" at your boot option to
418 disable memory resource controller and you can avoid overheads.
419 (and lose benefits of memory resource contoller)
421 This config option also selects MM_OWNER config option, which
422 could in turn add some fork/exit overhead.
424 config SYSFS_DEPRECATED
427 config SYSFS_DEPRECATED_V2
428 bool "Create deprecated sysfs files"
431 select SYSFS_DEPRECATED
433 This option creates deprecated symlinks such as the
434 "device"-link, the <subsystem>:<name>-link, and the
435 "bus"-link. It may also add deprecated key in the
437 None of these features or values should be used today, as
438 they export driver core implementation details to userspace
439 or export properties which can't be kept stable across kernel
442 If enabled, this option will also move any device structures
443 that belong to a class, back into the /sys/class hierarchy, in
444 order to support older versions of udev and some userspace
447 If you are using a distro with the most recent userspace
448 packages, it should be safe to say N here.
450 config PROC_PID_CPUSET
451 bool "Include legacy /proc/<pid>/cpuset file"
456 bool "Kernel->user space relay support (formerly relayfs)"
458 This option enables support for relay interface support in
459 certain file systems (such as debugfs).
460 It is designed to provide an efficient mechanism for tools and
461 facilities to relay large amounts of data from kernel space to
467 bool "Namespaces support" if EMBEDDED
470 Provides the way to make tasks work with different objects using
471 the same id. For example same IPC id may refer to different objects
472 or same user id or pid may refer to different tasks when used in
473 different namespaces.
477 depends on NAMESPACES
479 In this namespace tasks see different info provided with the
484 depends on NAMESPACES && SYSVIPC
486 In this namespace tasks work with IPC ids which correspond to
487 different IPC objects in different namespaces
490 bool "User namespace (EXPERIMENTAL)"
491 depends on NAMESPACES && EXPERIMENTAL
493 This allows containers, i.e. vservers, to use user namespaces
494 to provide different user info for different servers.
498 bool "PID Namespaces (EXPERIMENTAL)"
500 depends on NAMESPACES && EXPERIMENTAL
502 Support process id namespaces. This allows having multiple
503 process with the same pid as long as they are in different
504 pid namespaces. This is a building block of containers.
506 Unless you want to work with an experimental feature
509 config BLK_DEV_INITRD
510 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
511 depends on BROKEN || !FRV
513 The initial RAM filesystem is a ramfs which is loaded by the
514 boot loader (loadlin or lilo) and that is mounted as root
515 before the normal boot procedure. It is typically used to
516 load modules needed to mount the "real" root file system,
517 etc. See <file:Documentation/initrd.txt> for details.
519 If RAM disk support (BLK_DEV_RAM) is also included, this
520 also enables initial RAM disk (initrd) support and adds
521 15 Kbytes (more on some other architectures) to the kernel size.
531 config CC_OPTIMIZE_FOR_SIZE
532 bool "Optimize for size"
535 Enabling this option will pass "-Os" instead of "-O2" to gcc
536 resulting in a smaller kernel.
540 menu "Custom Build Flags"
543 string "Custom CFLAGS for kernel"
546 You can use this to easily set custom gcc CFLAGS to be used for the
547 entire kernel (including modules).
549 No warning for you, i can't fix stupidity.
551 If unsure, leave blank.
553 config CUSTOM_MAKEFLAGS
554 string "Custom MAKEFLAGS for kernel"
557 You can use this to easily set custom MAKEFLAGS to be used for building
560 (Or just use the options when you run make?)
562 If unsure, leave blank.
567 bool "Fast boot support"
569 The fastboot option will cause the kernel to try to optimize
572 This includes doing some of the device initialization asynchronously
573 as well as opportunistically trying to mount the root fs early.
581 bool "Configure standard kernel features (for small systems)"
583 This option allows certain base kernel options and settings
584 to be disabled or tweaked. This is for specialized
585 environments which can tolerate a "non-standard" kernel.
586 Only use this if you really know what you are doing.
589 bool "Enable 16-bit UID system calls" if EMBEDDED
590 depends on ARM || BLACKFIN || CRIS || FRV || H8300 || X86_32 || M68K || (S390 && !64BIT) || SUPERH || SPARC32 || (SPARC64 && COMPAT) || UML || (X86_64 && IA32_EMULATION)
593 This enables the legacy 16-bit UID syscall wrappers.
595 config SYSCTL_SYSCALL
596 bool "Sysctl syscall support" if EMBEDDED
600 sys_sysctl uses binary paths that have been found challenging
601 to properly maintain and use. The interface in /proc/sys
602 using paths with ascii names is now the primary path to this
605 Almost nothing using the binary sysctl interface so if you are
606 trying to save some space it is probably safe to disable this,
607 making your kernel marginally smaller.
609 If unsure say Y here.
612 bool "Load all symbols for debugging/ksymoops" if EMBEDDED
615 Say Y here to let the kernel print out symbolic crash information and
616 symbolic stack backtraces. This increases the size of the kernel
617 somewhat, as all symbols have to be loaded into the kernel image.
620 bool "Include all symbols in kallsyms"
621 depends on DEBUG_KERNEL && KALLSYMS
623 Normally kallsyms only contains the symbols of functions, for nicer
624 OOPS messages. Some debuggers can use kallsyms for other
625 symbols too: say Y here to include all symbols, if you need them
626 and you don't care about adding 300k to the size of your kernel.
630 config KALLSYMS_EXTRA_PASS
631 bool "Do an extra kallsyms pass"
634 If kallsyms is not working correctly, the build will fail with
635 inconsistent kallsyms data. If that occurs, log a bug report and
636 turn on KALLSYMS_EXTRA_PASS which should result in a stable build.
637 Always say N here unless you find a bug in kallsyms, which must be
638 reported. KALLSYMS_EXTRA_PASS is only a temporary workaround while
639 you wait for kallsyms to be fixed.
643 bool "Support for hot-pluggable devices" if EMBEDDED
646 This option is provided for the case where no hotplug or uevent
647 capabilities is wanted by the kernel. You should only consider
648 disabling this option for embedded systems that do not use modules, a
649 dynamic /dev tree, or dynamic device discovery. Just say Y.
653 bool "Enable support for printk" if EMBEDDED
655 This option enables normal printk support. Removing it
656 eliminates most of the message strings from the kernel image
657 and makes the kernel more or less silent. As this makes it
658 very difficult to diagnose system problems, saying N here is
659 strongly discouraged.
662 bool "BUG() support" if EMBEDDED
665 Disabling this option eliminates support for BUG and WARN, reducing
666 the size of your kernel image and potentially quietly ignoring
667 numerous fatal conditions. You should only consider disabling this
668 option for embedded systems with no facilities for reporting errors.
673 bool "Enable ELF core dumps" if EMBEDDED
675 Enable support for generating core dumps. Disabling saves about 4k.
677 config PCSPKR_PLATFORM
678 bool "Enable PC-Speaker support" if EMBEDDED
679 depends on ALPHA || X86 || MIPS || PPC_PREP || PPC_CHRP || PPC_PSERIES
682 This option allows to disable the internal PC-Speaker
683 support, saving some memory.
686 bool "Disable heap randomization"
689 Randomizing heap placement makes heap exploits harder, but it
690 also breaks ancient binaries (including anything libc5 based).
691 This option changes the bootup default to heap randomization
692 disabled, and can be overriden runtime by setting
693 /proc/sys/kernel/randomize_va_space to 2.
695 On non-ancient distros (post-2000 ones) N is usually a safe choice.
699 bool "Enable full-sized data structures for core" if EMBEDDED
701 Disabling this option reduces the size of miscellaneous core
702 kernel data structures. This saves memory on small machines,
703 but may reduce performance.
706 bool "Enable futex support" if EMBEDDED
710 Disabling this option will cause the kernel to be built without
711 support for "fast userspace mutexes". The resulting kernel may not
712 run glibc-based applications correctly.
718 bool "Enable eventpoll support" if EMBEDDED
722 Disabling this option will cause the kernel to be built without
723 support for epoll family of system calls.
726 bool "Enable signalfd() system call" if EMBEDDED
730 Enable the signalfd() system call that allows to receive signals
731 on a file descriptor.
736 bool "Enable timerfd() system call" if EMBEDDED
740 Enable the timerfd() system call that allows to receive timer
741 events on a file descriptor.
746 bool "Enable eventfd() system call" if EMBEDDED
750 Enable the eventfd() system call that allows to receive both
751 kernel notification (ie. KAIO) or userspace notifications.
756 bool "Use full shmem filesystem" if EMBEDDED
760 The shmem is an internal filesystem used to manage shared memory.
761 It is backed by swap and manages resource limits. It is also exported
762 to userspace as tmpfs if TMPFS is enabled. Disabling this
763 option replaces shmem and tmpfs with the much simpler ramfs code,
764 which may be appropriate on small systems without swap.
767 bool "Enable AIO support" if EMBEDDED
770 This option enables POSIX asynchronous I/O which may by used
771 by some high performance threaded applications. Disabling
772 this option saves about 7k.
774 config VM_EVENT_COUNTERS
776 bool "Enable VM event counters for /proc/vmstat" if EMBEDDED
778 VM event counters are needed for event counts to be shown.
779 This option allows the disabling of the VM event counters
780 on EMBEDDED systems. /proc/vmstat will only show page counts
781 if VM event counters are disabled.
785 bool "Enable PCI quirk workarounds" if EMBEDDED
788 This enables workarounds for various PCI chipset
789 bugs/quirks. Disable this only if your target machine is
790 unaffected by PCI quirks.
794 bool "Enable SLUB debugging support" if EMBEDDED
795 depends on SLUB && SYSFS
797 SLUB has extensive debug support features. Disabling these can
798 result in significant savings in code size. This also disables
799 SLUB sysfs support. /sys/slab will not exist and there will be
800 no support for cache validation etc.
803 prompt "Choose SLAB allocator"
806 This option allows to select a slab allocator.
811 The regular slab allocator that is established and known to work
812 well in all environments. It organizes cache hot objects in
813 per cpu and per node queues.
816 bool "SLUB (Unqueued Allocator)"
818 SLUB is a slab allocator that minimizes cache line usage
819 instead of managing queues of cached objects (SLAB approach).
820 Per cpu caching is realized using slabs of objects instead
821 of queues of objects. SLUB can use memory efficiently
822 and has enhanced diagnostics. SLUB is the default choice for
827 bool "SLOB (Simple Allocator)"
829 SLOB replaces the stock allocator with a drastically simpler
830 allocator. SLOB is generally more space efficient but
831 does not perform as well on large systems.
837 tristate "TLSF Allocator"
839 Two Level Segregate Fit Allocator. Its fast and gives low
841 http://rtportal.upv.es/rtmalloc/
842 http://code.google.com/p/compcache/wiki/TLSFAllocator
843 for more information.
848 bool "Enable TLSF debugging" if EMBEDDED || BLK_DEV_COMPCACHE
850 Enable TLSF debugging.
851 This causes negligible performance loss and size increase.
857 bool "Collect TLSF statistics" if EMBEDDED || BLK_DEV_COMPCACHE
859 Creates /proc/tlsfinfo to export various tlsf statistics.
860 This adds about 30K to size with significant performance loss.
864 bool "Profiling support (EXPERIMENTAL)"
866 Say Y here to enable the extended profiling support mechanisms used
867 by profilers such as OProfile.
870 # Place an empty function call at each tracepoint site. Can be
871 # dynamically changed for a probe function.
877 bool "Activate markers"
879 Place an empty function call at each marker site. Can be
880 dynamically changed for a probe function.
882 source "arch/Kconfig"
884 endmenu # General setup
886 config HAVE_GENERIC_DMA_COHERENT
893 depends on SLAB || SLUB_DEBUG
906 default 0 if BASE_FULL
907 default 1 if !BASE_FULL
910 bool "Enable loadable module support"
912 Kernel modules are small pieces of compiled code which can
913 be inserted in the running kernel, rather than being
914 permanently built into the kernel. You use the "modprobe"
915 tool to add (and sometimes remove) them. If you say Y here,
916 many parts of the kernel can be built as modules (by
917 answering M instead of Y where indicated): this is most
918 useful for infrequently used options which are not required
919 for booting. For more information, see the man pages for
920 modprobe, lsmod, modinfo, insmod and rmmod.
922 If you say Y here, you will need to run "make
923 modules_install" to put the modules under /lib/modules/
924 where modprobe can find them (you may need to be root to do
931 config MODULE_FORCE_LOAD
932 bool "Forced module loading"
935 Allow loading of modules without version information (ie. modprobe
936 --force). Forced module loading sets the 'F' (forced) taint flag and
937 is usually a really bad idea.
940 bool "Module unloading"
942 Without this option you will not be able to unload any
943 modules (note that some modules may not be unloadable
944 anyway), which makes your kernel smaller, faster
945 and simpler. If unsure, say Y.
947 config MODULE_FORCE_UNLOAD
948 bool "Forced module unloading"
949 depends on MODULE_UNLOAD && EXPERIMENTAL
951 This option allows you to force a module to unload, even if the
952 kernel believes it is unsafe: the kernel will remove the module
953 without waiting for anyone to stop using it (using the -f option to
954 rmmod). This is mainly for kernel developers and desperate users.
958 bool "Module versioning support"
960 Usually, you have to use modules compiled with your kernel.
961 Saying Y here makes it sometimes possible to use modules
962 compiled for different kernels, by adding enough information
963 to the modules to (hopefully) spot any changes which would
964 make them incompatible with the kernel you are running. If
967 config MODULE_SRCVERSION_ALL
968 bool "Source checksum for all modules"
970 Modules which contain a MODULE_VERSION get an extra "srcversion"
971 field inserted into their modinfo section, which contains a
972 sum of the source files which made it. This helps maintainers
973 see exactly which source was used to build a module (since
974 others sometimes change the module source without updating
975 the version). With this option, such a "srcversion" field
976 will be created for all modules. If unsure, say N.
981 This is being removed soon. These days, CONFIG_MODULES
982 implies CONFIG_KMOD, so use that instead.
989 depends on (SMP && MODULE_UNLOAD) || HOTPLUG_CPU
991 Need stop_machine() primitive.
993 source "block/Kconfig"
995 config PREEMPT_NOTIFIERS
999 def_bool !PREEMPT_RCU
1001 This option selects the classic RCU implementation that is
1002 designed for best read-side performance on non-realtime
1003 systems. Classic RCU is the default. Note that the
1004 PREEMPT_RCU symbol is used to select/deselect this option.