Blame view
init/Kconfig
73.2 KB
ec8f24b7f
|
1 |
# SPDX-License-Identifier: GPL-2.0-only |
face4374e
|
2 3 |
config DEFCONFIG_LIST string |
b2670eacf
|
4 |
depends on !UML |
face4374e
|
5 |
option defconfig_list |
47f38ae08
|
6 |
default "/lib/modules/$(shell,uname -r)/.config" |
face4374e
|
7 |
default "/etc/kernel-config" |
47f38ae08
|
8 |
default "/boot/config-$(shell,uname -r)" |
2a86f6612
|
9 |
default "arch/$(SRCARCH)/configs/$(KBUILD_DEFCONFIG)" |
face4374e
|
10 |
|
a43538989
|
11 12 13 14 15 |
config CC_IS_GCC def_bool $(success,$(CC) --version | head -n 1 | grep -q gcc) config GCC_VERSION int |
fa7295ab6
|
16 |
default $(shell,$(srctree)/scripts/gcc-version.sh $(CC)) if CC_IS_GCC |
a43538989
|
17 |
default 0 |
469cb7376
|
18 19 20 21 22 23 |
config CC_IS_CLANG def_bool $(success,$(CC) --version | head -n 1 | grep -q clang) config CLANG_VERSION int default $(shell,$(srctree)/scripts/clang-version.sh $(CC)) |
1a927fd34
|
24 25 |
config CC_CAN_LINK def_bool $(success,$(srctree)/scripts/cc-can-link.sh $(CC)) |
e9666d10a
|
26 27 |
config CC_HAS_ASM_GOTO def_bool $(success,$(srctree)/scripts/gcc-goto.sh $(CC)) |
5cf896fb6
|
28 |
config TOOLS_SUPPORT_RELR |
2d1229424
|
29 |
def_bool $(success,env "CC=$(CC)" "LD=$(LD)" "NM=$(NM)" "OBJCOPY=$(OBJCOPY)" $(srctree)/scripts/tools-support-relr.sh) |
5cf896fb6
|
30 |
|
eb1118693
|
31 32 |
config CC_HAS_ASM_INLINE def_bool $(success,echo 'void foo(void) { asm inline (""); }' | $(CC) -x c - -c -o /dev/null) |
b303c6df8
|
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 |
config CC_HAS_WARN_MAYBE_UNINITIALIZED def_bool $(cc-option,-Wmaybe-uninitialized) help GCC >= 4.7 supports this option. config CC_DISABLE_WARN_MAYBE_UNINITIALIZED bool depends on CC_HAS_WARN_MAYBE_UNINITIALIZED default CC_IS_GCC && GCC_VERSION < 40900 # unreliable for GCC < 4.9 help GCC's -Wmaybe-uninitialized is not reliable by definition. Lots of false positive warnings are produced in some cases. If this option is enabled, -Wno-maybe-uninitialzed is passed to the compiler to suppress maybe-uninitialized warnings. |
b99b87f70
|
48 49 |
config CONSTRUCTORS bool |
87c9366e1
|
50 |
depends on !UML |
b99b87f70
|
51 |
|
e360adbe2
|
52 53 |
config IRQ_WORK bool |
e360adbe2
|
54 |
|
109167063
|
55 |
config BUILDTIME_TABLE_SORT |
1dbdc6f17
|
56 |
bool |
c65eacbe2
|
57 58 59 60 61 62 |
config THREAD_INFO_IN_TASK bool help Select this to move thread_info off the stack into task_struct. To make this work, an arch will need to remove all thread_info fields except flags and fix any runtime bugs. |
c6c314a61
|
63 64 |
One subtle change that will be needed is to use try_get_task_stack() and put_task_stack() in save_thread_stack_tsk() and get_wchan(). |
ff0cfc66c
|
65 |
menu "General setup" |
1da177e4c
|
66 |
|
1da177e4c
|
67 68 |
config BROKEN bool |
1da177e4c
|
69 70 71 72 73 |
config BROKEN_ON_SMP bool depends on BROKEN || !SMP default y |
1da177e4c
|
74 75 |
config INIT_ENV_ARG_LIMIT int |
dd673bca4
|
76 77 |
default 32 if !UML default 128 if UML |
1da177e4c
|
78 |
help |
34ad92c23
|
79 80 |
Maximum of each of the number of arguments and environment variables passed to init from the kernel command line. |
1da177e4c
|
81 |
|
4bb166725
|
82 83 |
config COMPILE_TEST bool "Compile also drivers which will not load" |
bc083a64b
|
84 |
depends on !UML |
4bb166725
|
85 86 87 88 89 90 91 92 93 94 95 |
default n help Some drivers can be compiled on a different platform than they are intended to be run on. Despite they cannot be loaded there (or even when they load they cannot be used due to missing HW support), developers still, opposing to distributors, might want to build such drivers to compile-test them. If you are a developer and want to build everything available, say Y here. If you are a user/distributor, say N here to exclude useless drivers to be distributed. |
d6fc9fcba
|
96 97 |
config UAPI_HEADER_TEST bool "Compile test UAPI headers" |
fcbb8461f
|
98 |
depends on HEADERS_INSTALL && CC_CAN_LINK |
d6fc9fcba
|
99 100 101 102 103 104 |
help Compile test headers exported to user-space to ensure they are self-contained, i.e. compilable as standalone units. If you are a developer or tester and want to ensure the exported headers are self-contained, say Y here. Otherwise, choose N. |
1da177e4c
|
105 106 107 108 109 110 111 112 113 |
config LOCALVERSION string "Local version - append to kernel release" help Append an extra string to the end of your kernel version. This will show up when you type uname, for example. The string you set here will be appended after the contents of any files with a filename matching localversion* in your object and source tree, in that order. Your total string can be a maximum of 64 characters. |
aaebf4332
|
114 115 116 |
config LOCALVERSION_AUTO bool "Automatically append version information to the version string" default y |
ac3339baf
|
117 |
depends on !COMPILE_TEST |
aaebf4332
|
118 119 |
help This will try to automatically determine if the current tree is a |
6e5a5420b
|
120 121 |
release tree by looking for git tags that belong to the current top of tree revision. |
aaebf4332
|
122 123 |
A string of the format -gxxxxxxxx will be added to the localversion |
6e5a5420b
|
124 |
if a git-based tree is found. The string generated by this will be |
aaebf4332
|
125 |
appended after any matching localversion* files, and after the value |
6e5a5420b
|
126 |
set in CONFIG_LOCALVERSION. |
aaebf4332
|
127 |
|
6e5a5420b
|
128 129 130 131 132 133 |
(The actual string used here is the first eight characters produced by running the command: $ git rev-parse --verify HEAD which is done within the script "scripts/setlocalversion".) |
aaebf4332
|
134 |
|
9afb719e7
|
135 |
config BUILD_SALT |
e8cf4e9ca
|
136 137 138 139 140 141 142 |
string "Build ID Salt" default "" help The build ID is used to link binaries and their debug info. Setting this option will use the value in the calculation of the build id. This is mostly useful for distributions which want to ensure the build is unique between builds. It's safe to leave the default. |
9afb719e7
|
143 |
|
2e9f3bddc
|
144 145 146 147 148 149 150 151 |
config HAVE_KERNEL_GZIP bool config HAVE_KERNEL_BZIP2 bool config HAVE_KERNEL_LZMA bool |
3ebe12439
|
152 153 |
config HAVE_KERNEL_XZ bool |
7dd65feb6
|
154 155 |
config HAVE_KERNEL_LZO bool |
e76e1fdfa
|
156 157 |
config HAVE_KERNEL_LZ4 bool |
f16466af3
|
158 159 |
config HAVE_KERNEL_UNCOMPRESSED bool |
30d65dbfe
|
160 |
choice |
2e9f3bddc
|
161 162 |
prompt "Kernel compression mode" default KERNEL_GZIP |
f16466af3
|
163 |
depends on HAVE_KERNEL_GZIP || HAVE_KERNEL_BZIP2 || HAVE_KERNEL_LZMA || HAVE_KERNEL_XZ || HAVE_KERNEL_LZO || HAVE_KERNEL_LZ4 || HAVE_KERNEL_UNCOMPRESSED |
2e9f3bddc
|
164 |
help |
30d65dbfe
|
165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 |
The linux kernel is a kind of self-extracting executable. Several compression algorithms are available, which differ in efficiency, compression and decompression speed. Compression speed is only relevant when building a kernel. Decompression speed is relevant at each boot. If you have any problems with bzip2 or lzma compressed kernels, mail me (Alain Knaff) <alain@knaff.lu>. (An older version of this functionality (bzip2 only), for 2.4, was supplied by Christian Ludwig) High compression options are mostly useful for users, who are low on disk space (embedded systems), but for whom ram size matters less. If in doubt, select 'gzip' config KERNEL_GZIP |
2e9f3bddc
|
183 184 185 |
bool "Gzip" depends on HAVE_KERNEL_GZIP help |
7dd65feb6
|
186 187 |
The old and tried gzip compression. It provides a good balance between compression ratio and decompression speed. |
30d65dbfe
|
188 189 190 |
config KERNEL_BZIP2 bool "Bzip2" |
2e9f3bddc
|
191 |
depends on HAVE_KERNEL_BZIP2 |
30d65dbfe
|
192 193 |
help Its compression ratio and speed is intermediate. |
0a4dd35c6
|
194 |
Decompression speed is slowest among the choices. The kernel |
2e9f3bddc
|
195 196 197 |
size is about 10% smaller with bzip2, in comparison to gzip. Bzip2 uses a large amount of memory. For modern kernels you will need at least 8MB RAM or more for booting. |
30d65dbfe
|
198 199 |
config KERNEL_LZMA |
2e9f3bddc
|
200 201 202 |
bool "LZMA" depends on HAVE_KERNEL_LZMA help |
0a4dd35c6
|
203 204 205 |
This compression algorithm's ratio is best. Decompression speed is between gzip and bzip2. Compression is slowest. The kernel size is about 33% smaller with LZMA in comparison to gzip. |
30d65dbfe
|
206 |
|
3ebe12439
|
207 208 209 210 211 212 213 214 215 216 217 218 219 220 |
config KERNEL_XZ bool "XZ" depends on HAVE_KERNEL_XZ help XZ uses the LZMA2 algorithm and instruction set specific BCJ filters which can improve compression ratio of executable code. The size of the kernel is about 30% smaller with XZ in comparison to gzip. On architectures for which there is a BCJ filter (i386, x86_64, ARM, IA-64, PowerPC, and SPARC), XZ will create a few percent smaller kernel than plain LZMA. The speed is about the same as with LZMA: The decompression speed of XZ is better than that of bzip2 but worse than gzip and LZO. Compression is slow. |
7dd65feb6
|
221 222 223 224 |
config KERNEL_LZO bool "LZO" depends on HAVE_KERNEL_LZO help |
0a4dd35c6
|
225 |
Its compression ratio is the poorest among the choices. The kernel |
681b3049d
|
226 |
size is about 10% bigger than gzip; however its speed |
7dd65feb6
|
227 |
(both compression and decompression) is the fastest. |
e76e1fdfa
|
228 229 230 231 232 233 234 235 236 237 238 |
config KERNEL_LZ4 bool "LZ4" depends on HAVE_KERNEL_LZ4 help LZ4 is an LZ77-type compressor with a fixed, byte-oriented encoding. A preliminary version of LZ4 de/compression tool is available at <https://code.google.com/p/lz4/>. Its compression ratio is worse than LZO. The size of the kernel is about 8% bigger than LZO. But the decompression speed is faster than LZO. |
f16466af3
|
239 240 241 242 243 244 245 246 247 |
config KERNEL_UNCOMPRESSED bool "None" depends on HAVE_KERNEL_UNCOMPRESSED help Produce uncompressed kernel image. This option is usually not what you want. It is useful for debugging the kernel in slow simulation environments, where decompressing and moving the kernel is awfully slow. This option allows early boot code to skip the decompressor and jump right at uncompressed kernel image. |
30d65dbfe
|
248 |
endchoice |
bd5dc17be
|
249 250 251 252 253 254 255 256 |
config DEFAULT_HOSTNAME string "Default hostname" default "(none)" help This option determines the default system hostname before userspace calls sethostname(2). The kernel traditionally uses "(none)" here, but you may wish to use a different default here to make a minimal system more usable with less configuration. |
17c46a6af
|
257 258 259 260 261 262 |
# # For some reason microblaze and nios2 hard code SWAP=n. Hopefully we can # add proper SWAP support to them, in which case this can be remove. # config ARCH_NO_SWAP bool |
1da177e4c
|
263 264 |
config SWAP bool "Support for paging of anonymous memory (swap)" |
17c46a6af
|
265 |
depends on MMU && BLOCK && !ARCH_NO_SWAP |
1da177e4c
|
266 267 268 |
default y help This option allows you to choose whether you want to have support |
92c3504e6
|
269 |
for so called swap devices or swap files in your kernel that are |
1da177e4c
|
270 271 272 273 274 |
used to provide more virtual memory than the actual RAM present in your computer. If unsure say Y. config SYSVIPC bool "System V IPC" |
1da177e4c
|
275 276 277 278 279 280 281 282 283 284 285 286 |
---help--- Inter Process Communication is a suite of library functions and system calls which let processes (running programs) synchronize and exchange information. It is generally considered to be a good thing, and some programs won't run unless you say Y here. In particular, if you want to run the DOS emulator dosemu under Linux (read the DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>), you'll need to say Y here. You can find documentation about IPC with "info ipc" and also in section 6.4 of the Linux Programmer's Guide, available from <http://www.tldp.org/guides.html>. |
a5494dcd8
|
287 288 289 290 291 |
config SYSVIPC_SYSCTL bool depends on SYSVIPC depends on SYSCTL default y |
1da177e4c
|
292 293 |
config POSIX_MQUEUE bool "POSIX Message Queues" |
19c923998
|
294 |
depends on NET |
1da177e4c
|
295 296 297 298 299 |
---help--- POSIX variant of message queues is a part of IPC. In POSIX message queues every message has a priority which decides about succession of receiving it by a process. If you want to compile and run programs written e.g. for Solaris with use of its POSIX message |
b0e376504
|
300 |
queues (functions mq_*) say Y here. |
1da177e4c
|
301 302 303 304 305 306 |
POSIX message queues are visible as a filesystem called 'mqueue' and can be mounted somewhere if you want to do filesystem operations on message queues. If unsure, say Y. |
bdc8e5f85
|
307 308 309 310 311 |
config POSIX_MQUEUE_SYSCTL bool depends on POSIX_MQUEUE depends on SYSCTL default y |
226b4ccdc
|
312 313 314 315 316 317 318 |
config CROSS_MEMORY_ATTACH bool "Enable process_vm_readv/writev syscalls" depends on MMU default y help Enabling this option adds the system calls process_vm_readv and process_vm_writev which allow a process with the correct privileges |
a2a368d90
|
319 |
to directly read from or write to another process' address space. |
226b4ccdc
|
320 |
See the man page for more details. |
69369a700
|
321 322 |
config USELIB bool "uselib syscall" |
b2113a417
|
323 |
def_bool ALPHA || M68K || SPARC || X86_32 || IA32_EMULATION |
69369a700
|
324 325 326 327 328 329 |
help This option enables the uselib syscall, a system call used in the dynamic linker from libc5 and earlier. glibc does not use this system call. If you intend to run programs built on libc5 or earlier, you may need to enable this syscall. Current systems running glibc can safely disable this. |
391dc69c6
|
330 331 332 333 334 335 |
config AUDIT bool "Auditing support" depends on NET help Enable auditing infrastructure that can be used with another kernel subsystem, such as SELinux (which requires this for |
cb74ed278
|
336 337 |
logging of avc messages output). System call auditing is included on architectures which support it. |
391dc69c6
|
338 |
|
7a0177212
|
339 340 |
config HAVE_ARCH_AUDITSYSCALL bool |
391dc69c6
|
341 |
config AUDITSYSCALL |
cb74ed278
|
342 |
def_bool y |
7a0177212
|
343 |
depends on AUDIT && HAVE_ARCH_AUDITSYSCALL |
391dc69c6
|
344 |
select FSNOTIFY |
391dc69c6
|
345 346 |
source "kernel/irq/Kconfig" source "kernel/time/Kconfig" |
87a4c3759
|
347 |
source "kernel/Kconfig.preempt" |
391dc69c6
|
348 349 |
menu "CPU/Task time and stats accounting" |
abf917cd9
|
350 351 |
config VIRT_CPU_ACCOUNTING bool |
fdf9c3565
|
352 353 354 |
choice prompt "Cputime accounting" default TICK_CPU_ACCOUNTING if !PPC64 |
02fc8d372
|
355 |
default VIRT_CPU_ACCOUNTING_NATIVE if PPC64 |
fdf9c3565
|
356 357 358 359 |
# Kind of a stub config for the pure tick based cputime accounting config TICK_CPU_ACCOUNTING bool "Simple tick based cputime accounting" |
c58b0df12
|
360 |
depends on !S390 && !NO_HZ_FULL |
fdf9c3565
|
361 362 363 364 365 366 |
help This is the basic tick based cputime accounting that maintains statistics about user, system and idle time spent on per jiffies granularity. If unsure, say Y. |
abf917cd9
|
367 |
config VIRT_CPU_ACCOUNTING_NATIVE |
b952741c8
|
368 |
bool "Deterministic task and CPU time accounting" |
c58b0df12
|
369 |
depends on HAVE_VIRT_CPU_ACCOUNTING && !NO_HZ_FULL |
abf917cd9
|
370 |
select VIRT_CPU_ACCOUNTING |
b952741c8
|
371 372 373 374 375 376 377 378 |
help Select this option to enable more accurate task and CPU time accounting. This is done by reading a CPU counter on each kernel entry and exit and on transitions within the kernel between system, softirq and hardirq state, so there is a small performance impact. In the case of s390 or IBM POWER > 5, this also enables accounting of stolen time on logically-partitioned systems. |
abf917cd9
|
379 380 |
config VIRT_CPU_ACCOUNTING_GEN bool "Full dynticks CPU time accounting" |
ff3fb2541
|
381 |
depends on HAVE_CONTEXT_TRACKING |
554b0004d
|
382 |
depends on HAVE_VIRT_CPU_ACCOUNTING_GEN |
041a15744
|
383 |
depends on GENERIC_CLOCKEVENTS |
abf917cd9
|
384 385 386 387 388 389 390 391 392 393 394 395 396 |
select VIRT_CPU_ACCOUNTING select CONTEXT_TRACKING help Select this option to enable task and CPU time accounting on full dynticks systems. This accounting is implemented by watching every kernel-user boundaries using the context tracking subsystem. The accounting is thus performed at the expense of some significant overhead. For now this is only useful if you are working on the full dynticks subsystem development. If unsure, say N. |
b58c35840
|
397 |
endchoice |
fdf9c3565
|
398 399 |
config IRQ_TIME_ACCOUNTING bool "Fine granularity task level IRQ time accounting" |
b58c35840
|
400 |
depends on HAVE_IRQ_TIME_ACCOUNTING && !VIRT_CPU_ACCOUNTING_NATIVE |
fdf9c3565
|
401 402 403 404 405 406 407 |
help Select this option to enable fine granularity task irq time accounting. This is done by reading a timestamp on each transitions between softirq and hardirq state, so there can be a small performance impact. If in doubt, say N here. |
11d4afd4f
|
408 409 410 411 |
config HAVE_SCHED_AVG_IRQ def_bool y depends on IRQ_TIME_ACCOUNTING || PARAVIRT_TIME_ACCOUNTING depends on SMP |
765047932
|
412 413 414 |
config SCHED_THERMAL_PRESSURE bool "Enable periodic averaging of thermal pressure" depends on SMP |
1da177e4c
|
415 416 |
config BSD_PROCESS_ACCT bool "BSD Process Accounting" |
2813893f8
|
417 |
depends on MULTIUSER |
1da177e4c
|
418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 |
help If you say Y here, a user level program will be able to instruct the kernel (via a special system call) to write process accounting information to a file: whenever a process exits, information about that process will be appended to the file by the kernel. The information includes things such as creation time, owning user, command name, memory usage, controlling terminal etc. (the complete list is in the struct acct in <file:include/linux/acct.h>). It is up to the user level program to do useful things with this information. This is generally a good idea, so say Y. config BSD_PROCESS_ACCT_V3 bool "BSD Process Accounting version 3 file format" depends on BSD_PROCESS_ACCT default n help If you say Y here, the process accounting information is written in a new file format that also logs the process IDs of each |
3903bf940
|
436 |
process and its parent. Note that this file format is incompatible |
1da177e4c
|
437 438 |
with previous v0/v1/v2 file formats, so you will need updated tools for processing it. A preliminary version of these tools is available |
37a4c9407
|
439 |
at <http://www.gnu.org/software/acct/>. |
1da177e4c
|
440 |
|
c757249af
|
441 |
config TASKSTATS |
19c923998
|
442 |
bool "Export task/process statistics through netlink" |
c757249af
|
443 |
depends on NET |
2813893f8
|
444 |
depends on MULTIUSER |
c757249af
|
445 446 447 448 449 450 451 452 453 |
default n help Export selected statistics for tasks/processes through the generic netlink interface. Unlike BSD process accounting, the statistics are available during the lifetime of tasks/processes as responses to commands. Like BSD accounting, they are sent to user space on task exit. Say N if unsure. |
ca74e92b4
|
454 |
config TASK_DELAY_ACCT |
19c923998
|
455 |
bool "Enable per-task delay accounting" |
6f44993fe
|
456 |
depends on TASKSTATS |
f6db83479
|
457 |
select SCHED_INFO |
ca74e92b4
|
458 459 460 461 462 463 464 |
help Collect information on time spent by a task waiting for system resources like cpu, synchronous block I/O completion and swapping in pages. Such statistics can help in setting a task's priorities relative to other tasks for cpu, io, rss limits etc. Say N if unsure. |
18f705f49
|
465 |
config TASK_XACCT |
19c923998
|
466 |
bool "Enable extended accounting over taskstats" |
18f705f49
|
467 468 469 470 471 472 473 474 |
depends on TASKSTATS help Collect extended task accounting data and send the data to userland for processing over the taskstats interface. Say N if unsure. config TASK_IO_ACCOUNTING |
19c923998
|
475 |
bool "Enable per-task storage I/O accounting" |
18f705f49
|
476 477 478 479 480 481 |
depends on TASK_XACCT help Collect information on the number of bytes of storage I/O which this task has caused. Say N if unsure. |
eb414681d
|
482 483 484 485 486 487 488 489 490 491 |
config PSI bool "Pressure stall information tracking" help Collect metrics that indicate how overcommitted the CPU, memory, and IO capacity are in the system. If you say Y here, the kernel will create /proc/pressure/ with the pressure statistics files cpu, memory, and io. These will indicate the share of walltime in which some or all tasks in the system are delayed due to contention of the respective resource. |
2ce7135ad
|
492 493 494 |
In kernels with cgroup support, cgroups (cgroup2 only) will have cpu.pressure, memory.pressure, and io.pressure files, which aggregate pressure stalls for the grouped tasks only. |
c3123552a
|
495 |
For more details see Documentation/accounting/psi.rst. |
eb414681d
|
496 497 |
Say N if unsure. |
e0c274472
|
498 499 500 501 502 503 |
config PSI_DEFAULT_DISABLED bool "Require boot parameter to enable pressure stall information tracking" default n depends on PSI help If set, pressure stall information tracking will be disabled |
428a1cb4b
|
504 505 |
per default but can be enabled through passing psi=1 on the kernel commandline during boot. |
e0c274472
|
506 |
|
7b2489d37
|
507 508 509 510 511 512 513 514 515 516 |
This feature adds some code to the task wakeup and sleep paths of the scheduler. The overhead is too low to affect common scheduling-intense workloads in practice (such as webservers, memcache), but it does show up in artificial scheduler stress tests, such as hackbench. If you are paranoid and not sure what the kernel will be used for, say Y. Say N if unsure. |
391dc69c6
|
517 |
endmenu # "CPU/Task time and stats accounting" |
d9817ebee
|
518 |
|
5c4991e24
|
519 520 |
config CPU_ISOLATION bool "CPU isolation" |
414a2dc13
|
521 |
depends on SMP || COMPILE_TEST |
2c43838c9
|
522 |
default y |
5c4991e24
|
523 524 525 |
help Make sure that CPUs running critical tasks are not disturbed by any source of "noise" such as unbound workqueues, timers, kthreads... |
2c43838c9
|
526 527 528 529 |
Unbound jobs get offloaded to housekeeping CPUs. This is driven by the "isolcpus=" boot parameter. Say Y if unsure. |
5c4991e24
|
530 |
|
0af92d460
|
531 |
source "kernel/rcu/Kconfig" |
c903ff837
|
532 |
|
de5b56ba5
|
533 534 535 |
config BUILD_BIN2C bool default n |
1da177e4c
|
536 |
config IKCONFIG |
f2443ab6c
|
537 |
tristate "Kernel .config support" |
1da177e4c
|
538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 |
---help--- This option enables the complete Linux kernel ".config" file contents to be saved in the kernel. It provides documentation of which kernel options are used in a running kernel or in an on-disk kernel. This information can be extracted from the kernel image file with the script scripts/extract-ikconfig and used as input to rebuild the current kernel or to build another kernel. It can also be extracted from a running kernel by reading /proc/config.gz if enabled (below). config IKCONFIG_PROC bool "Enable access to .config through /proc/config.gz" depends on IKCONFIG && PROC_FS ---help--- This option enables access to the kernel configuration file through /proc/config.gz. |
f7b101d33
|
554 555 556 557 558 559 560 561 |
config IKHEADERS tristate "Enable kernel headers through /sys/kernel/kheaders.tar.xz" depends on SYSFS help This option enables access to the in-kernel headers that are generated during the build process. These can be used to build eBPF tracing programs, or similar programs. If you build the headers as a module, a module called kheaders.ko is built which can be loaded on-demand to get access to headers. |
43d8ce9d6
|
562 |
|
794543a23
|
563 564 |
config LOG_BUF_SHIFT int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" |
fb39f98d1
|
565 |
range 12 25 |
f17a32e97
|
566 |
default 17 |
361e9dfba
|
567 |
depends on PRINTK |
794543a23
|
568 |
help |
23b2899f7
|
569 570 571 572 |
Select the minimal kernel log buffer size as a power of 2. The final size is affected by LOG_CPU_MAX_BUF_SHIFT config parameter, see below. Any higher size also might be forced by "log_buf_len" boot parameter. |
f17a32e97
|
573 |
Examples: |
23b2899f7
|
574 |
17 => 128 KB |
f17a32e97
|
575 |
16 => 64 KB |
23b2899f7
|
576 577 |
15 => 32 KB 14 => 16 KB |
794543a23
|
578 579 |
13 => 8 KB 12 => 4 KB |
23b2899f7
|
580 581 |
config LOG_CPU_MAX_BUF_SHIFT int "CPU kernel log buffer size contribution (13 => 8 KB, 17 => 128KB)" |
2240a31db
|
582 |
depends on SMP |
23b2899f7
|
583 584 585 |
range 0 21 default 12 if !BASE_SMALL default 0 if BASE_SMALL |
361e9dfba
|
586 |
depends on PRINTK |
23b2899f7
|
587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 |
help This option allows to increase the default ring buffer size according to the number of CPUs. The value defines the contribution of each CPU as a power of 2. The used space is typically only few lines however it might be much more when problems are reported, e.g. backtraces. The increased size means that a new buffer has to be allocated and the original static one is unused. It makes sense only on systems with more CPUs. Therefore this value is used only when the sum of contributions is greater than the half of the default kernel ring buffer as defined by LOG_BUF_SHIFT. The default values are set so that more than 64 CPUs are needed to trigger the allocation. Also this option is ignored when "log_buf_len" kernel parameter is used as it forces an exact (power of two) size of the ring buffer. The number of possible CPUs is used for this computation ignoring |
5e0d8d59a
|
605 606 |
hotplugging making the computation optimal for the worst case scenario while allowing a simple algorithm to be used from bootup. |
23b2899f7
|
607 608 609 610 611 612 613 614 |
Examples shift values and their meaning: 17 => 128 KB for each CPU 16 => 64 KB for each CPU 15 => 32 KB for each CPU 14 => 16 KB for each CPU 13 => 8 KB for each CPU 12 => 4 KB for each CPU |
f92bac3b1
|
615 616 |
config PRINTK_SAFE_LOG_BUF_SHIFT int "Temporary per-CPU printk log buffer size (12 => 4KB, 13 => 8KB)" |
427934b87
|
617 618 |
range 10 21 default 13 |
f92bac3b1
|
619 |
depends on PRINTK |
427934b87
|
620 |
help |
f92bac3b1
|
621 622 623 624 625 |
Select the size of an alternate printk per-CPU buffer where messages printed from usafe contexts are temporary stored. One example would be NMI messages, another one - printk recursion. The messages are copied to the main log buffer in a safe context to avoid a deadlock. The value defines the size as a power of 2. |
427934b87
|
626 |
|
f92bac3b1
|
627 |
Those messages are rare and limited. The largest one is when |
427934b87
|
628 629 630 631 632 633 634 635 636 637 |
a backtrace is printed. It usually fits into 4KB. Select 8KB if you want to be on the safe side. Examples: 17 => 128 KB for each CPU 16 => 64 KB for each CPU 15 => 32 KB for each CPU 14 => 16 KB for each CPU 13 => 8 KB for each CPU 12 => 4 KB for each CPU |
a5574cf65
|
638 639 640 641 642 |
# # Architectures with an unreliable sched_clock() should select this: # config HAVE_UNSTABLE_SCHED_CLOCK bool |
38ff87f77
|
643 644 |
config GENERIC_SCHED_CLOCK bool |
69842cba9
|
645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 |
menu "Scheduler features" config UCLAMP_TASK bool "Enable utilization clamping for RT/FAIR tasks" depends on CPU_FREQ_GOV_SCHEDUTIL help This feature enables the scheduler to track the clamped utilization of each CPU based on RUNNABLE tasks scheduled on that CPU. With this option, the user can specify the min and max CPU utilization allowed for RUNNABLE tasks. The max utilization defines the maximum frequency a task should use while the min utilization defines the minimum frequency it should use. Both min and max utilization clamp values are hints to the scheduler, aiming at improving its frequency selection policy, but they do not enforce or grant any specific bandwidth for tasks. If in doubt, say N. config UCLAMP_BUCKETS_COUNT int "Number of supported utilization clamp buckets" range 5 20 default 5 depends on UCLAMP_TASK help Defines the number of clamp buckets to use. The range of each bucket will be SCHED_CAPACITY_SCALE/UCLAMP_BUCKETS_COUNT. The higher the number of clamp buckets the finer their granularity and the higher the precision of clamping aggregation and tracking at run-time. For example, with the minimum configuration value we will have 5 clamp buckets tracking 20% utilization each. A 25% boosted tasks will be refcounted in the [20..39]% bucket and will set the bucket clamp effective value to 25%. If a second 30% boosted task should be co-scheduled on the same CPU, that task will be refcounted in the same bucket of the first task and it will boost the bucket clamp effective value to 30%. The clamp effective value of a bucket is reset to its nominal value (20% in the example above) when there are no more tasks refcounted in that bucket. An additional boost/capping margin can be added to some tasks. In the example above the 25% task will be boosted to 30% until it exits the CPU. If that should be considered not acceptable on certain systems, it's always possible to reduce the margin by increasing the number of clamp buckets to trade off used memory for run-time tracking precision. If in doubt, use the default value. endmenu |
be3a72842
|
697 698 699 700 701 702 |
# # For architectures that want to enable the support for NUMA-affine scheduler # balancing logic: # config ARCH_SUPPORTS_NUMA_BALANCING bool |
be5e610c0
|
703 |
# |
72b252aed
|
704 705 706 707 708 709 710 711 |
# For architectures that prefer to flush all TLBs after a number of pages # are unmapped instead of sending one IPI per page to flush. The architecture # must provide guarantees on what happens if a clean TLB cache entry is # written after the unmap. Details are in mm/rmap.c near the check for # should_defer_flush. The architecture should also consider if the full flush # and the refill costs are offset by the savings of sending fewer IPIs. config ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH bool |
c12d3362a
|
712 |
config CC_HAS_INT128 |
3a7c73316
|
713 |
def_bool !$(cc-option,$(m64-flag) -D__SIZEOF_INT128__=0) && 64BIT |
c12d3362a
|
714 |
|
72b252aed
|
715 |
# |
be5e610c0
|
716 717 718 719 |
# For architectures that know their GCC __int128 support is sound # config ARCH_SUPPORTS_INT128 bool |
be3a72842
|
720 721 722 723 724 |
# For architectures that (ab)use NUMA to represent different memory regions # all cpu-local but of different latencies, such as SuperH. # config ARCH_WANT_NUMA_VARIABLE_LOCALITY bool |
be3a72842
|
725 726 |
config NUMA_BALANCING bool "Memory placement aware NUMA scheduler" |
be3a72842
|
727 728 729 730 731 732 |
depends on ARCH_SUPPORTS_NUMA_BALANCING depends on !ARCH_WANT_NUMA_VARIABLE_LOCALITY depends on SMP && NUMA && MIGRATION help This option adds support for automatic NUMA aware memory/task placement. The mechanism is quite primitive and is based on migrating memory when |
6d56a410a
|
733 |
it has references to the node the task is running on. |
be3a72842
|
734 735 |
This system will be inactive on UMA systems. |
6f7c97e80
|
736 737 738 739 740 741 742 |
config NUMA_BALANCING_DEFAULT_ENABLED bool "Automatically enable NUMA aware memory/task placement" default y depends on NUMA_BALANCING help If set, automatic NUMA balancing will be enabled if running on a NUMA machine. |
23964d2d0
|
743 |
menuconfig CGROUPS |
6341e62b2
|
744 |
bool "Control Group support" |
2bd59d48e
|
745 |
select KERNFS |
5cdc38f98
|
746 |
help |
23964d2d0
|
747 |
This option adds support for grouping sets of processes together, for |
5cdc38f98
|
748 749 750 |
use with process control subsystems such as Cpusets, CFS, memory controls or device isolation. See |
d6a3b2476
|
751 |
- Documentation/scheduler/sched-design-CFS.rst (CFS) |
da82c92f1
|
752 |
- Documentation/admin-guide/cgroup-v1/ (features for grouping, isolation |
45ce80fb6
|
753 |
and resource control) |
5cdc38f98
|
754 755 |
Say N if unsure. |
23964d2d0
|
756 |
if CGROUPS |
3e32cb2e0
|
757 |
config PAGE_COUNTER |
e8cf4e9ca
|
758 |
bool |
3e32cb2e0
|
759 |
|
c255a4580
|
760 |
config MEMCG |
a0166ec4b
|
761 |
bool "Memory controller" |
3e32cb2e0
|
762 |
select PAGE_COUNTER |
79bd9814e
|
763 |
select EVENTFD |
00f0b8259
|
764 |
help |
a0166ec4b
|
765 |
Provides control over the memory footprint of tasks in a cgroup. |
00f0b8259
|
766 |
|
c255a4580
|
767 |
config MEMCG_SWAP |
a0166ec4b
|
768 |
bool "Swap controller" |
c255a4580
|
769 |
depends on MEMCG && SWAP |
c077719be
|
770 |
help |
a0166ec4b
|
771 |
Provides control over the swap space consumed by tasks in a cgroup. |
c255a4580
|
772 |
config MEMCG_SWAP_ENABLED |
a0166ec4b
|
773 |
bool "Swap controller enabled by default" |
c255a4580
|
774 |
depends on MEMCG_SWAP |
a42c390cf
|
775 776 777 778 |
default y help Memory Resource Controller Swap Extension comes with its price in a bigger memory consumption. General purpose distribution kernels |
43d547f9c
|
779 |
which want to enable the feature but keep it disabled by default |
07555ac14
|
780 |
and let the user enable it by swapaccount=1 boot command line |
a42c390cf
|
781 782 783 |
parameter should have this option unselected. For those who want to have the feature enabled by default should select this option (if, for some reason, they need to disable it |
00a66d297
|
784 |
then swapaccount=0 does the trick). |
c077719be
|
785 |
|
84c07d11a
|
786 787 788 789 |
config MEMCG_KMEM bool depends on MEMCG && !SLOB default y |
6bf024e69
|
790 791 792 |
config BLK_CGROUP bool "IO controller" depends on BLOCK |
2bc64a204
|
793 |
default n |
6bf024e69
|
794 795 796 797 |
---help--- Generic block IO controller cgroup interface. This is the common cgroup interface which should be used by various IO controlling policies. |
2bc64a204
|
798 |
|
6bf024e69
|
799 800 801 802 |
Currently, CFQ IO scheduler uses it to recognize task groups and control disk bandwidth allocation (proportional time slice allocation) to such task groups. It is also used by bio throttling logic in block layer to implement upper limit in IO rates on a device. |
e5d1367f1
|
803 |
|
6bf024e69
|
804 805 806 807 808 |
This option only enables generic Block IO controller infrastructure. One needs to also enable actual IO controlling logic/policy. For enabling proportional weight division of disk bandwidth in CFQ, set CONFIG_CFQ_GROUP_IOSCHED=y; for enabling throttling policy, set CONFIG_BLK_DEV_THROTTLING=y. |
da82c92f1
|
809 |
See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information. |
6bf024e69
|
810 |
|
6bf024e69
|
811 812 813 814 |
config CGROUP_WRITEBACK bool depends on MEMCG && BLK_CGROUP default y |
e5d1367f1
|
815 |
|
7c9414385
|
816 |
menuconfig CGROUP_SCHED |
a0166ec4b
|
817 |
bool "CPU controller" |
7c9414385
|
818 819 820 821 822 823 824 825 826 827 828 |
default n help This feature lets CPU scheduler recognize task groups and control CPU bandwidth allocation to such task groups. It uses cgroups to group tasks. if CGROUP_SCHED config FAIR_GROUP_SCHED bool "Group scheduling for SCHED_OTHER" depends on CGROUP_SCHED default CGROUP_SCHED |
ab84d31e1
|
829 830 |
config CFS_BANDWIDTH bool "CPU bandwidth provisioning for FAIR_GROUP_SCHED" |
ab84d31e1
|
831 832 833 834 835 836 837 |
depends on FAIR_GROUP_SCHED default n help This option allows users to define CPU bandwidth rates (limits) for tasks running within the fair group scheduler. Groups with no limit set are considered to be unconstrained and will run with no restriction. |
d6a3b2476
|
838 |
See Documentation/scheduler/sched-bwc.rst for more information. |
ab84d31e1
|
839 |
|
7c9414385
|
840 841 |
config RT_GROUP_SCHED bool "Group scheduling for SCHED_RR/FIFO" |
7c9414385
|
842 843 844 845 |
depends on CGROUP_SCHED default n help This feature lets you explicitly allocate real CPU bandwidth |
32bd7eb5a
|
846 |
to task groups. If enabled, it will also make it impossible to |
7c9414385
|
847 848 |
schedule realtime tasks for non-root users until you allocate realtime bandwidth for them. |
d6a3b2476
|
849 |
See Documentation/scheduler/sched-rt-group.rst for more information. |
7c9414385
|
850 851 |
endif #CGROUP_SCHED |
2480c0931
|
852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 |
config UCLAMP_TASK_GROUP bool "Utilization clamping per group of tasks" depends on CGROUP_SCHED depends on UCLAMP_TASK default n help This feature enables the scheduler to track the clamped utilization of each CPU based on RUNNABLE tasks currently scheduled on that CPU. When this option is enabled, the user can specify a min and max CPU bandwidth which is allowed for each single task in a group. The max bandwidth allows to clamp the maximum frequency a task can use, while the min bandwidth allows to define a minimum frequency a task will always use. When task group based utilization clamping is enabled, an eventually specified task-specific clamp value is constrained by the cgroup specified clamp value. Both minimum and maximum task clamping cannot be bigger than the corresponding clamping defined at task group level. If in doubt, say N. |
6bf024e69
|
873 874 875 876 877 878 879 880 881 |
config CGROUP_PIDS bool "PIDs controller" help Provides enforcement of process number limits in the scope of a cgroup. Any attempt to fork more processes than is allowed in the cgroup will fail. PIDs are fundamentally a global resource because it is fairly trivial to reach PID exhaustion before you reach even a conservative kmemcg limit. As a result, it is possible to grind a system to halt without being limited by other cgroup policies. The |
6cc578df4
|
882 |
PIDs controller is designed to stop this from happening. |
6bf024e69
|
883 884 |
It should be noted that organisational operations (such as attaching |
980768338
|
885 |
to a cgroup hierarchy) will *not* be blocked by the PIDs controller, |
6bf024e69
|
886 887 |
since the PIDs limit only affects a process's ability to fork, not to attach to a cgroup. |
39d3e7584
|
888 889 890 891 892 893 894 895 896 |
config CGROUP_RDMA bool "RDMA controller" help Provides enforcement of RDMA resources defined by IB stack. It is fairly easy for consumers to exhaust RDMA resources, which can result into resource unavailability to other consumers. RDMA controller is designed to stop this from happening. Attaching processes with active RDMA resources to the cgroup hierarchy is allowed even if can cross the hierarchy's limit. |
6bf024e69
|
897 898 899 900 901 |
config CGROUP_FREEZER bool "Freezer controller" help Provides a way to freeze and unfreeze all tasks in a cgroup. |
489c2a20a
|
902 903 904 905 |
This option affects the ORIGINAL cgroup interface. The cgroup2 memory controller includes important in-kernel memory consumers per default. If you're using cgroup2, say N. |
6bf024e69
|
906 907 908 909 |
config CGROUP_HUGETLB bool "HugeTLB controller" depends on HUGETLB_PAGE select PAGE_COUNTER |
afc24d49c
|
910 |
default n |
6bf024e69
|
911 912 913 914 915 916 917 918 919 920 |
help Provides a cgroup controller for HugeTLB pages. When you enable this, you can put a per cgroup limit on HugeTLB usage. The limit is enforced during page fault. Since HugeTLB doesn't support page reclaim, enforcing the limit at page fault time implies that, the application will get SIGBUS signal if it tries to access HugeTLB pages beyond its limit. This requires the application to know beforehand how much HugeTLB pages it would require for its use. The control group is tracked in the third page lru pointer. This means that we cannot use the controller with huge page less than 3 pages. |
afc24d49c
|
921 |
|
6bf024e69
|
922 923 |
config CPUSETS bool "Cpuset controller" |
e1d4eeec5
|
924 |
depends on SMP |
6bf024e69
|
925 926 927 928 929 |
help This option will let you create and manage CPUSETs which allow dynamically partitioning a system into sets of CPUs and Memory Nodes and assigning tasks to run only within those sets. This is primarily useful on large SMP or NUMA systems. |
afc24d49c
|
930 |
|
6bf024e69
|
931 |
Say N if unsure. |
afc24d49c
|
932 |
|
6bf024e69
|
933 934 935 936 |
config PROC_PID_CPUSET bool "Include legacy /proc/<pid>/cpuset file" depends on CPUSETS default y |
afc24d49c
|
937 |
|
6bf024e69
|
938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 |
config CGROUP_DEVICE bool "Device controller" help Provides a cgroup controller implementing whitelists for devices which a process in the cgroup can mknod or open. config CGROUP_CPUACCT bool "Simple CPU accounting controller" help Provides a simple controller for monitoring the total CPU consumed by the tasks in a cgroup. config CGROUP_PERF bool "Perf controller" depends on PERF_EVENTS help This option extends the perf per-cpu mode to restrict monitoring to threads which belong to the cgroup specified and run on the designated cpu. Say N if unsure. |
300709849
|
959 960 |
config CGROUP_BPF bool "Support for eBPF programs attached to cgroups" |
483c4933e
|
961 962 |
depends on BPF_SYSCALL select SOCK_CGROUP_DATA |
300709849
|
963 964 965 966 967 968 969 970 |
help Allow attaching eBPF programs to a cgroup using the bpf(2) syscall command BPF_PROG_ATTACH. In which context these programs are accessed depends on the type of attachment. For instance, programs that are attached using BPF_CGROUP_INET_INGRESS will be executed on the ingress path of inet sockets. |
6bf024e69
|
971 |
config CGROUP_DEBUG |
23b0be480
|
972 |
bool "Debug controller" |
afc24d49c
|
973 |
default n |
23b0be480
|
974 |
depends on DEBUG_KERNEL |
6bf024e69
|
975 976 |
help This option enables a simple controller that exports |
23b0be480
|
977 978 979 |
debugging information about the cgroups framework. This controller is for control cgroup debugging only. Its interfaces are not stable. |
afc24d49c
|
980 |
|
6bf024e69
|
981 |
Say N. |
89e9b9e07
|
982 |
|
73b351473
|
983 984 985 |
config SOCK_CGROUP_DATA bool default n |
23964d2d0
|
986 |
endif # CGROUPS |
c077719be
|
987 |
|
8dd2a82c2
|
988 |
menuconfig NAMESPACES |
6a108a14f
|
989 |
bool "Namespaces support" if EXPERT |
2813893f8
|
990 |
depends on MULTIUSER |
6a108a14f
|
991 |
default !EXPERT |
c5289a694
|
992 993 994 995 996 |
help Provides the way to make tasks work with different objects using the same id. For example same IPC id may refer to different objects or same user id or pid may refer to different tasks when used in different namespaces. |
8dd2a82c2
|
997 |
if NAMESPACES |
58bfdd6de
|
998 999 |
config UTS_NS bool "UTS namespace" |
17a6d4411
|
1000 |
default y |
58bfdd6de
|
1001 1002 1003 |
help In this namespace tasks see different info provided with the uname() system call |
769071ac9
|
1004 1005 |
config TIME_NS bool "TIME namespace" |
660fd04f9
|
1006 |
depends on GENERIC_VDSO_TIME_NS |
769071ac9
|
1007 1008 1009 1010 |
default y help In this namespace boottime and monotonic clocks can be set. The time will keep going with the same pace. |
ae5e1b22f
|
1011 1012 |
config IPC_NS bool "IPC namespace" |
8dd2a82c2
|
1013 |
depends on (SYSVIPC || POSIX_MQUEUE) |
17a6d4411
|
1014 |
default y |
ae5e1b22f
|
1015 1016 |
help In this namespace tasks work with IPC ids which correspond to |
614b84cf4
|
1017 |
different IPC objects in different namespaces. |
ae5e1b22f
|
1018 |
|
aee16ce73
|
1019 |
config USER_NS |
19c923998
|
1020 |
bool "User namespace" |
5673a94c1
|
1021 |
default n |
aee16ce73
|
1022 1023 1024 |
help This allows containers, i.e. vservers, to use user namespaces to provide different user info for different servers. |
e11f0ae38
|
1025 1026 |
When user namespaces are enabled in the kernel it is |
d886f4e48
|
1027 1028 1029 |
recommended that the MEMCG option also be enabled and that user-space use the memory control groups to limit the amount of memory a memory unprivileged users can use. |
e11f0ae38
|
1030 |
|
aee16ce73
|
1031 |
If unsure, say N. |
74bd59bb3
|
1032 |
config PID_NS |
9bd38c2cd
|
1033 |
bool "PID Namespaces" |
17a6d4411
|
1034 |
default y |
74bd59bb3
|
1035 |
help |
12d2b8f95
|
1036 |
Support process id namespaces. This allows having multiple |
692105b8a
|
1037 |
processes with the same pid as long as they are in different |
74bd59bb3
|
1038 |
pid namespaces. This is a building block of containers. |
d6eb633fe
|
1039 1040 |
config NET_NS bool "Network namespace" |
8dd2a82c2
|
1041 |
depends on NET |
17a6d4411
|
1042 |
default y |
d6eb633fe
|
1043 1044 1045 |
help Allow user space to create what appear to be multiple instances of the network stack. |
8dd2a82c2
|
1046 |
endif # NAMESPACES |
5cb366bb3
|
1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 |
config CHECKPOINT_RESTORE bool "Checkpoint/restore support" select PROC_CHILDREN default n help Enables additional kernel features in a sake of checkpoint/restore. In particular it adds auxiliary prctl codes to setup process text, data and heap segment sizes, and a few additional /proc filesystem entries. If unsure, say N here. |
5091faa44
|
1058 1059 |
config SCHED_AUTOGROUP bool "Automatic process group scheduling" |
5091faa44
|
1060 1061 1062 1063 1064 1065 1066 1067 1068 |
select CGROUPS select CGROUP_SCHED select FAIR_GROUP_SCHED help This option optimizes the scheduler for common desktop workloads by automatically creating and populating task groups. This separation of workloads isolates aggressive CPU burners (like build jobs) from desktop applications. Task group autogeneration is currently based upon task session. |
7af37bec4
|
1069 |
config SYSFS_DEPRECATED |
5d6a4ea57
|
1070 |
bool "Enable deprecated sysfs features to support old userspace tools" |
7af37bec4
|
1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 |
depends on SYSFS default n help This option adds code that switches the layout of the "block" class devices, to not show up in /sys/class/block/, but only in /sys/block/. This switch is only active when the sysfs.deprecated=1 boot option is passed or the SYSFS_DEPRECATED_V2 option is set. This option allows new kernels to run on old distributions and tools, which might get confused by /sys/class/block/. Since 2007/2008 all major distributions and tools handle this just fine. Recent distributions and userspace tools after 2009/2010 depend on the existence of /sys/class/block/, and will not work with this option enabled. Only if you are using a new kernel on an old distribution, you might need to say Y here. config SYSFS_DEPRECATED_V2 |
5d6a4ea57
|
1093 |
bool "Enable deprecated sysfs features by default" |
7af37bec4
|
1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 |
default n depends on SYSFS depends on SYSFS_DEPRECATED help Enable deprecated sysfs by default. See the CONFIG_SYSFS_DEPRECATED option for more details about this option. Only if you are using a new kernel on an old distribution, you might need to say Y here. Even then, odds are you would not need it enabled, you can always pass the boot option if absolutely necessary. config RELAY bool "Kernel->user space relay support (formerly relayfs)" |
26b5679e4
|
1109 |
select IRQ_WORK |
7af37bec4
|
1110 1111 1112 1113 1114 1115 1116 1117 |
help This option enables support for relay interface support in certain file systems (such as debugfs). It is designed to provide an efficient mechanism for tools and facilities to relay large amounts of data from kernel space to user space. If unsure, say N. |
f991633de
|
1118 1119 |
config BLK_DEV_INITRD bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support" |
f991633de
|
1120 1121 1122 1123 1124 |
help The initial RAM filesystem is a ramfs which is loaded by the boot loader (loadlin or lilo) and that is mounted as root before the normal boot procedure. It is typically used to load modules needed to mount the "real" root file system, |
8c27ceff3
|
1125 |
etc. See <file:Documentation/admin-guide/initrd.rst> for details. |
f991633de
|
1126 1127 1128 1129 1130 1131 |
If RAM disk support (BLK_DEV_RAM) is also included, this also enables initial RAM disk (initrd) support and adds 15 Kbytes (more on some other architectures) to the kernel size. If unsure say Y. |
c33df4eaa
|
1132 |
if BLK_DEV_INITRD |
dbec48663
|
1133 |
source "usr/Kconfig" |
c33df4eaa
|
1134 |
endif |
76db5a27a
|
1135 1136 |
config BOOT_CONFIG bool "Boot config support" |
2910b5aa6
|
1137 |
select BLK_DEV_INITRD |
76db5a27a
|
1138 1139 1140 |
help Extra boot config allows system admin to pass a config file as complemental extension of kernel cmdline when booting. |
0947db01d
|
1141 |
The boot config file must be attached at the end of initramfs |
85c46b78d
|
1142 |
with checksum, size and magic word. |
0947db01d
|
1143 |
See <file:Documentation/admin-guide/bootconfig.rst> for details. |
76db5a27a
|
1144 1145 |
If unsure, say Y. |
877417e6f
|
1146 1147 |
choice prompt "Compiler optimization level" |
2cc3ce24a
|
1148 |
default CC_OPTIMIZE_FOR_PERFORMANCE |
877417e6f
|
1149 1150 |
config CC_OPTIMIZE_FOR_PERFORMANCE |
15f5db60a
|
1151 |
bool "Optimize for performance (-O2)" |
877417e6f
|
1152 1153 1154 1155 |
help This is the default optimization level for the kernel, building with the "-O2" compiler flag for best performance and most helpful compile-time warnings. |
15f5db60a
|
1156 1157 1158 |
config CC_OPTIMIZE_FOR_PERFORMANCE_O3 bool "Optimize more for performance (-O3)" depends on ARC |
b303c6df8
|
1159 |
imply CC_DISABLE_WARN_MAYBE_UNINITIALIZED # avoid false positives |
c45b4f1f1
|
1160 |
help |
15f5db60a
|
1161 1162 |
Choosing this option will pass "-O3" to your compiler to optimize the kernel yet more for performance. |
c45b4f1f1
|
1163 |
|
c45b4f1f1
|
1164 |
config CC_OPTIMIZE_FOR_SIZE |
15f5db60a
|
1165 |
bool "Optimize for size (-Os)" |
b303c6df8
|
1166 |
imply CC_DISABLE_WARN_MAYBE_UNINITIALIZED # avoid false positives |
c45b4f1f1
|
1167 |
help |
ce3b487f6
|
1168 1169 |
Choosing this option will pass "-Os" to your compiler resulting in a smaller kernel. |
c45b4f1f1
|
1170 |
|
877417e6f
|
1171 |
endchoice |
5d20ee319
|
1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 |
config HAVE_LD_DEAD_CODE_DATA_ELIMINATION bool help This requires that the arch annotates or otherwise protects its external entry points from being discarded. Linker scripts must also merge .text.*, .data.*, and .bss.* correctly into output sections. Care must be taken not to pull in unrelated sections (e.g., '.text.init'). Typically '.' in section names is used to distinguish them from label names / C identifiers. config LD_DEAD_CODE_DATA_ELIMINATION bool "Dead code and data elimination (EXPERIMENTAL)" depends on HAVE_LD_DEAD_CODE_DATA_ELIMINATION depends on EXPERT |
16fd20aa9
|
1186 |
depends on !(FUNCTION_TRACER && CC_IS_GCC && GCC_VERSION < 40800) |
e85d1d65c
|
1187 1188 |
depends on $(cc-option,-ffunction-sections -fdata-sections) depends on $(ld-option,--gc-sections) |
5d20ee319
|
1189 |
help |
8b9d27124
|
1190 1191 1192 |
Enable this if you want to do dead code and data elimination with the linker by compiling with -ffunction-sections -fdata-sections, and linking with --gc-sections. |
5d20ee319
|
1193 1194 1195 1196 1197 1198 1199 |
This can reduce on disk and in-memory size of the kernel code and static data, particularly for small configs and on small systems. This has the possibility of introducing silently broken kernel if the required annotations are not present. This option is not well tested yet, so use at your own risk. |
0847062ad
|
1200 1201 |
config SYSCTL bool |
657a52095
|
1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 |
config HAVE_UID16 bool config SYSCTL_EXCEPTION_TRACE bool help Enable support for /proc/sys/debug/exception-trace. config SYSCTL_ARCH_UNALIGN_NO_WARN bool help Enable support for /proc/sys/kernel/ignore-unaligned-usertrap Allows arch to define/use @no_unaligned_warning to possibly warn about unaligned access emulation going on under the hood. config SYSCTL_ARCH_UNALIGN_ALLOW bool help Enable support for /proc/sys/kernel/unaligned-trap Allows arches to define/use @unaligned_enabled to runtime toggle the unaligned access emulation. see arch/parisc/kernel/unaligned.c for reference |
657a52095
|
1224 1225 |
config HAVE_PCSPKR_PLATFORM bool |
f89b7755f
|
1226 1227 1228 |
# interpreter that classic socket filters depend on config BPF bool |
6a108a14f
|
1229 1230 |
menuconfig EXPERT bool "Configure standard kernel features (expert users)" |
f505c553d
|
1231 1232 |
# Unhide debug options, to make the on-by-default options visible select DEBUG_KERNEL |
1da177e4c
|
1233 1234 |
help This option allows certain base kernel options and settings |
e8cf4e9ca
|
1235 1236 1237 |
to be disabled or tweaked. This is for specialized environments which can tolerate a "non-standard" kernel. Only use this if you really know what you are doing. |
1da177e4c
|
1238 |
|
ae81f9e37
|
1239 |
config UID16 |
6a108a14f
|
1240 |
bool "Enable 16-bit UID system calls" if EXPERT |
2813893f8
|
1241 |
depends on HAVE_UID16 && MULTIUSER |
ae81f9e37
|
1242 1243 1244 |
default y help This enables the legacy 16-bit UID syscall wrappers. |
2813893f8
|
1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 |
config MULTIUSER bool "Multiple users, groups and capabilities support" if EXPERT default y help This option enables support for non-root users, groups and capabilities. If you say N here, all processes will run with UID 0, GID 0, and all possible capabilities. Saying N here also compiles out support for system calls related to UIDs, GIDs, and capabilities, such as setuid, setgid, and capset. If unsure, say Y here. |
f6187769d
|
1258 1259 |
config SGETMASK_SYSCALL bool "sgetmask/ssetmask syscalls support" if EXPERT |
a687a5337
|
1260 |
def_bool PARISC || M68K || PPC || MIPS || X86 || SPARC || MICROBLAZE || SUPERH |
f6187769d
|
1261 1262 1263 1264 1265 1266 |
---help--- sys_sgetmask and sys_ssetmask are obsolete system calls no longer supported in libc but still enabled by default in some architectures. If unsure, leave the default option here. |
6af9f7bf3
|
1267 1268 1269 1270 1271 1272 1273 1274 1275 |
config SYSFS_SYSCALL bool "Sysfs syscall support" if EXPERT default y ---help--- sys_sysfs is an obsolete system call no longer supported in libc. Note that disabling this option is more secure but might break compatibility with some systems. If unsure say Y here. |
d1b069f5f
|
1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 |
config FHANDLE bool "open by fhandle syscalls" if EXPERT select EXPORTFS default y help If you say Y here, a user level program will be able to map file names to handle and then later use the handle for different file system operations. This is useful in implementing userspace file servers, which now track files using handles instead of names. The handle would remain the same even if file names get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2) syscalls. |
baa73d9e4
|
1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 |
config POSIX_TIMERS bool "Posix Clocks & timers" if EXPERT default y help This includes native support for POSIX timers to the kernel. Some embedded systems have no use for them and therefore they can be configured out to reduce the size of the kernel image. When this option is disabled, the following syscalls won't be available: timer_create, timer_gettime: timer_getoverrun, timer_settime, timer_delete, clock_adjtime, getitimer, setitimer, alarm. Furthermore, the clock_settime, clock_gettime, clock_getres and clock_nanosleep syscalls will be limited to CLOCK_REALTIME, CLOCK_MONOTONIC and CLOCK_BOOTTIME only. If unsure say y. |
d59745ce3
|
1304 1305 |
config PRINTK default y |
6a108a14f
|
1306 |
bool "Enable support for printk" if EXPERT |
74876a98a
|
1307 |
select IRQ_WORK |
d59745ce3
|
1308 1309 1310 1311 1312 1313 |
help This option enables normal printk support. Removing it eliminates most of the message strings from the kernel image and makes the kernel more or less silent. As this makes it very difficult to diagnose system problems, saying N here is strongly discouraged. |
42a0bb3f7
|
1314 1315 1316 1317 |
config PRINTK_NMI def_bool y depends on PRINTK depends on HAVE_NMI |
c8538a7aa
|
1318 |
config BUG |
6a108a14f
|
1319 |
bool "BUG() support" if EXPERT |
c8538a7aa
|
1320 1321 |
default y help |
e8cf4e9ca
|
1322 1323 1324 1325 1326 |
Disabling this option eliminates support for BUG and WARN, reducing the size of your kernel image and potentially quietly ignoring numerous fatal conditions. You should only consider disabling this option for embedded systems with no facilities for reporting errors. Just say Y. |
c8538a7aa
|
1327 |
|
708e9a794
|
1328 |
config ELF_CORE |
046d662f4
|
1329 |
depends on COREDUMP |
708e9a794
|
1330 |
default y |
6a108a14f
|
1331 |
bool "Enable ELF core dumps" if EXPERT |
708e9a794
|
1332 1333 |
help Enable support for generating core dumps. Disabling saves about 4k. |
8761f1ab7
|
1334 |
|
e5e1d3cb2
|
1335 |
config PCSPKR_PLATFORM |
6a108a14f
|
1336 |
bool "Enable PC-Speaker support" if EXPERT |
8761f1ab7
|
1337 |
depends on HAVE_PCSPKR_PLATFORM |
15f304b66
|
1338 |
select I8253_LOCK |
e5e1d3cb2
|
1339 1340 |
default y help |
e8cf4e9ca
|
1341 1342 |
This option allows to disable the internal PC-Speaker support, saving some memory. |
e5e1d3cb2
|
1343 |
|
1da177e4c
|
1344 1345 |
config BASE_FULL default y |
6a108a14f
|
1346 |
bool "Enable full-sized data structures for core" if EXPERT |
1da177e4c
|
1347 1348 1349 1350 1351 1352 |
help Disabling this option reduces the size of miscellaneous core kernel data structures. This saves memory on small machines, but may reduce performance. config FUTEX |
6a108a14f
|
1353 |
bool "Enable futex support" if EXPERT |
1da177e4c
|
1354 |
default y |
bc2eecd7e
|
1355 |
imply RT_MUTEXES |
1da177e4c
|
1356 1357 1358 1359 |
help Disabling this option will cause the kernel to be built without support for "fast userspace mutexes". The resulting kernel may not run glibc-based applications correctly. |
bc2eecd7e
|
1360 1361 1362 1363 |
config FUTEX_PI bool depends on FUTEX && RT_MUTEXES default y |
03b8c7b62
|
1364 1365 |
config HAVE_FUTEX_CMPXCHG bool |
62b4d2041
|
1366 |
depends on FUTEX |
03b8c7b62
|
1367 1368 1369 1370 |
help Architectures should select this if futex_atomic_cmpxchg_inatomic() is implemented and always working. This removes a couple of runtime checks. |
1da177e4c
|
1371 |
config EPOLL |
6a108a14f
|
1372 |
bool "Enable eventpoll support" if EXPERT |
1da177e4c
|
1373 1374 1375 1376 |
default y help Disabling this option will cause the kernel to be built without support for epoll family of system calls. |
fba2afaae
|
1377 |
config SIGNALFD |
6a108a14f
|
1378 |
bool "Enable signalfd() system call" if EXPERT |
fba2afaae
|
1379 1380 1381 1382 1383 1384 |
default y help Enable the signalfd() system call that allows to receive signals on a file descriptor. If unsure, say Y. |
b215e2839
|
1385 |
config TIMERFD |
6a108a14f
|
1386 |
bool "Enable timerfd() system call" if EXPERT |
b215e2839
|
1387 1388 1389 1390 1391 1392 |
default y help Enable the timerfd() system call that allows to receive timer events on a file descriptor. If unsure, say Y. |
e1ad7468c
|
1393 |
config EVENTFD |
6a108a14f
|
1394 |
bool "Enable eventfd() system call" if EXPERT |
e1ad7468c
|
1395 1396 1397 1398 1399 1400 |
default y help Enable the eventfd() system call that allows to receive both kernel notification (ie. KAIO) or userspace notifications. If unsure, say Y. |
1da177e4c
|
1401 |
config SHMEM |
6a108a14f
|
1402 |
bool "Use full shmem filesystem" if EXPERT |
1da177e4c
|
1403 1404 1405 1406 1407 1408 1409 1410 |
default y depends on MMU help The shmem is an internal filesystem used to manage shared memory. It is backed by swap and manages resource limits. It is also exported to userspace as tmpfs if TMPFS is enabled. Disabling this option replaces shmem and tmpfs with the much simpler ramfs code, which may be appropriate on small systems without swap. |
ebf3f09c6
|
1411 |
config AIO |
6a108a14f
|
1412 |
bool "Enable AIO support" if EXPERT |
ebf3f09c6
|
1413 1414 1415 |
default y help This option enables POSIX asynchronous I/O which may by used |
657a52095
|
1416 1417 |
by some high performance threaded applications. Disabling this option saves about 7k. |
2b188cc1b
|
1418 1419 1420 |
config IO_URING bool "Enable IO uring support" if EXPERT select ANON_INODES |
561fb04a6
|
1421 |
select IO_WQ |
2b188cc1b
|
1422 1423 1424 1425 1426 |
default y help This option enables support for the io_uring interface, enabling applications to submit and complete IO through submission and completion rings that are shared between the kernel and application. |
d3ac21cac
|
1427 1428 1429 1430 1431 1432 1433 1434 1435 |
config ADVISE_SYSCALLS bool "Enable madvise/fadvise syscalls" if EXPERT default y help This option enables the madvise and fadvise syscalls, used by applications to advise the kernel about their future memory or file usage, improving performance. If building an embedded system where no applications use these syscalls, you can disable this option to save space. |
5b25b13ab
|
1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 |
config MEMBARRIER bool "Enable membarrier() system call" if EXPERT default y help Enable the membarrier() system call that allows issuing memory barriers across all running threads, which can be used to distribute the cost of user-space memory barriers asymmetrically by transforming pairs of memory barriers into pairs consisting of membarrier() and a compiler barrier. If unsure, say Y. |
d1b069f5f
|
1447 |
config KALLSYMS |
e8cf4e9ca
|
1448 1449 1450 1451 1452 1453 |
bool "Load all symbols for debugging/ksymoops" if EXPERT default y help Say Y here to let the kernel print out symbolic crash information and symbolic stack backtraces. This increases the size of the kernel somewhat, as all symbols have to be loaded into the kernel image. |
d1b069f5f
|
1454 1455 1456 1457 1458 |
config KALLSYMS_ALL bool "Include all symbols in kallsyms" depends on DEBUG_KERNEL && KALLSYMS help |
e8cf4e9ca
|
1459 1460 1461 1462 1463 |
Normally kallsyms only contains the symbols of functions for nicer OOPS messages and backtraces (i.e., symbols from the text and inittext sections). This is sufficient for most cases. And only in very rare cases (e.g., when a debugger is used) all symbols are required (e.g., names of variables from the data sections, etc). |
d1b069f5f
|
1464 |
|
e8cf4e9ca
|
1465 1466 1467 1468 |
This option makes sure that all symbols are loaded into the kernel image (i.e., symbols from all sections) in cost of increased kernel size (depending on the kernel configuration, it may be 300KiB or something like this). |
d1b069f5f
|
1469 |
|
e8cf4e9ca
|
1470 |
Say N unless you really need all symbols. |
d1b069f5f
|
1471 1472 1473 1474 1475 1476 1477 1478 1479 |
config KALLSYMS_ABSOLUTE_PERCPU bool depends on KALLSYMS default X86_64 && SMP config KALLSYMS_BASE_RELATIVE bool depends on KALLSYMS |
a687a5337
|
1480 |
default !IA64 |
d1b069f5f
|
1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 |
help Instead of emitting them as absolute values in the native word size, emit the symbol references in the kallsyms table as 32-bit entries, each containing a relative value in the range [base, base + U32_MAX] or, when KALLSYMS_ABSOLUTE_PERCPU is in effect, each containing either an absolute value in the range [0, S32_MAX] or a relative value in the range [base, base + S32_MAX], where base is the lowest relative symbol address encountered in the image. On 64-bit builds, this reduces the size of the address table by 50%, but more importantly, it results in entries whose values are build time constants, and no relocation pass is required at runtime to fix up the entries based on the runtime load address of the kernel. # end of the "standard kernel features (expert users)" menu # syscall, maps, verifier |
fc611f47f
|
1498 1499 1500 |
config BPF_LSM bool "LSM Instrumentation with BPF" |
4edf16b72
|
1501 |
depends on BPF_EVENTS |
fc611f47f
|
1502 1503 1504 1505 1506 1507 1508 1509 |
depends on BPF_SYSCALL depends on SECURITY depends on BPF_JIT help Enables instrumentation of the security hooks with eBPF programs for implementing dynamic MAC and Audit Policies. If you are unsure how to answer this question, answer N. |
d1b069f5f
|
1510 1511 |
config BPF_SYSCALL bool "Enable bpf() system call" |
d1b069f5f
|
1512 |
select BPF |
bae77c5eb
|
1513 |
select IRQ_WORK |
d1b069f5f
|
1514 1515 1516 1517 |
default n help Enable the bpf() system call that allows to manipulate eBPF programs and maps via file descriptors. |
81c22041d
|
1518 1519 |
config ARCH_WANT_DEFAULT_BPF_JIT bool |
290af8662
|
1520 1521 1522 1523 1524 1525 |
config BPF_JIT_ALWAYS_ON bool "Permanently enable BPF JIT and remove BPF interpreter" depends on BPF_SYSCALL && HAVE_EBPF_JIT && BPF_JIT help Enables BPF JIT and removes BPF interpreter to avoid speculative execution of BPF instructions by the interpreter |
81c22041d
|
1526 1527 1528 |
config BPF_JIT_DEFAULT_ON def_bool ARCH_WANT_DEFAULT_BPF_JIT || BPF_JIT_ALWAYS_ON depends on HAVE_EBPF_JIT && BPF_JIT |
d1b069f5f
|
1529 1530 |
config USERFAULTFD bool "Enable userfaultfd() system call" |
d1b069f5f
|
1531 1532 1533 1534 |
depends on MMU help Enable the userfaultfd() system call that allows to intercept and handle page faults in userland. |
3ccfebedd
|
1535 1536 |
config ARCH_HAS_MEMBARRIER_CALLBACKS bool |
70216e18e
|
1537 1538 |
config ARCH_HAS_MEMBARRIER_SYNC_CORE bool |
d7822b1e2
|
1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 |
config RSEQ bool "Enable rseq() system call" if EXPERT default y depends on HAVE_RSEQ select MEMBARRIER help Enable the restartable sequences system call. It provides a user-space cache for the current CPU number value, which speeds up getting the current CPU number from user-space, as well as an ABI to speed up user-space operations on per-CPU data. If unsure, say Y. config DEBUG_RSEQ default n bool "Enabled debugging of rseq() system call" if EXPERT depends on RSEQ && DEBUG_KERNEL help Enable extra debugging checks for the rseq system call. If unsure, say N. |
6befe5f69
|
1561 1562 |
config EMBEDDED bool "Embedded system" |
5d2acfc7b
|
1563 |
option allnoconfig_y |
6befe5f69
|
1564 1565 1566 1567 1568 |
select EXPERT help This option should be enabled if compiling the kernel for an embedded system so certain expert options are available for configuration. |
cdd6c482c
|
1569 |
config HAVE_PERF_EVENTS |
0793a61d4
|
1570 |
bool |
018df72dd
|
1571 1572 |
help See tools/perf/design.txt for details. |
0793a61d4
|
1573 |
|
906010b21
|
1574 1575 1576 1577 |
config PERF_USE_VMALLOC bool help See tools/perf/design.txt for details |
ad90a3de9
|
1578 |
config PC104 |
424529fb7
|
1579 |
bool "PC/104 support" if EXPERT |
ad90a3de9
|
1580 1581 1582 1583 |
help Expose PC/104 form factor device drivers and options available for selection and configuration. Enable this option if your target machine has a PC/104 bus. |
57c0c15b5
|
1584 |
menu "Kernel Performance Events And Counters" |
0793a61d4
|
1585 |
|
cdd6c482c
|
1586 |
config PERF_EVENTS |
57c0c15b5
|
1587 |
bool "Kernel performance events and counters" |
392d65a9a
|
1588 |
default y if PROFILING |
cdd6c482c
|
1589 |
depends on HAVE_PERF_EVENTS |
e360adbe2
|
1590 |
select IRQ_WORK |
83fe27ea5
|
1591 |
select SRCU |
0793a61d4
|
1592 |
help |
57c0c15b5
|
1593 1594 |
Enable kernel support for various performance events provided by software and hardware. |
0793a61d4
|
1595 |
|
dd77038d2
|
1596 |
Software events are supported either built-in or via the |
57c0c15b5
|
1597 |
use of generic tracepoints. |
0793a61d4
|
1598 |
|
57c0c15b5
|
1599 1600 |
Most modern CPUs support performance events via performance counter registers. These registers count the number of certain |
0793a61d4
|
1601 1602 1603 1604 1605 |
types of hw events: such as instructions executed, cachemisses suffered, or branches mis-predicted - without slowing down the kernel or applications. These registers can also trigger interrupts when a threshold number of events have passed - and can thus be used to profile the code that runs on that CPU. |
57c0c15b5
|
1606 |
The Linux Performance Event subsystem provides an abstraction of |
dd77038d2
|
1607 |
these software and hardware event capabilities, available via a |
57c0c15b5
|
1608 |
system call and used by the "perf" utility in tools/perf/. It |
0793a61d4
|
1609 1610 1611 1612 |
provides per task and per CPU counters, and it provides event capabilities on top of those. Say Y if unsure. |
906010b21
|
1613 1614 1615 |
config DEBUG_PERF_USE_VMALLOC default n bool "Debug: use vmalloc to back perf mmap() buffers" |
cb3071137
|
1616 |
depends on PERF_EVENTS && DEBUG_KERNEL && !PPC |
906010b21
|
1617 1618 |
select PERF_USE_VMALLOC help |
e8cf4e9ca
|
1619 |
Use vmalloc memory to back perf mmap() buffers. |
906010b21
|
1620 |
|
e8cf4e9ca
|
1621 1622 |
Mostly useful for debugging the vmalloc code on platforms that don't require it. |
906010b21
|
1623 |
|
e8cf4e9ca
|
1624 |
Say N if unsure. |
906010b21
|
1625 |
|
0793a61d4
|
1626 |
endmenu |
f8891e5e1
|
1627 1628 |
config VM_EVENT_COUNTERS default y |
6a108a14f
|
1629 |
bool "Enable VM event counters for /proc/vmstat" if EXPERT |
f8891e5e1
|
1630 |
help |
2aea4fb61
|
1631 1632 |
VM event counters are needed for event counts to be shown. This option allows the disabling of the VM event counters |
6a108a14f
|
1633 |
on EXPERT systems. /proc/vmstat will only show page counts |
2aea4fb61
|
1634 |
if VM event counters are disabled. |
f8891e5e1
|
1635 |
|
41ecc55b8
|
1636 1637 |
config SLUB_DEBUG default y |
6a108a14f
|
1638 |
bool "Enable SLUB debugging support" if EXPERT |
f6acb6350
|
1639 |
depends on SLUB && SYSFS |
41ecc55b8
|
1640 1641 1642 1643 1644 |
help SLUB has extensive debug support features. Disabling these can result in significant savings in code size. This also disables SLUB sysfs support. /sys/slab will not exist and there will be no support for cache validation etc. |
1663f26df
|
1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 |
config SLUB_MEMCG_SYSFS_ON default n bool "Enable memcg SLUB sysfs support by default" if EXPERT depends on SLUB && SYSFS && MEMCG help SLUB creates a directory under /sys/kernel/slab for each allocation cache to host info and debug files. If memory cgroup is enabled, each cache can have per memory cgroup caches. SLUB can create the same sysfs directories for these caches under /sys/kernel/slab/CACHE/cgroup but it can lead to a very high number of debug files being created. This is controlled by slub_memcg_sysfs boot parameter and this config option determines the parameter's default value. |
b943c460f
|
1658 1659 1660 1661 1662 1663 1664 |
config COMPAT_BRK bool "Disable heap randomization" default y help Randomizing heap placement makes heap exploits harder, but it also breaks ancient binaries (including anything libc5 based). This option changes the bootup default to heap randomization |
692105b8a
|
1665 |
disabled, and can be overridden at runtime by setting |
b943c460f
|
1666 1667 1668 |
/proc/sys/kernel/randomize_va_space to 2. On non-ancient distros (post-2000 ones) N is usually a safe choice. |
81819f0fc
|
1669 1670 |
choice prompt "Choose SLAB allocator" |
a0acd8208
|
1671 |
default SLUB |
81819f0fc
|
1672 1673 1674 1675 1676 |
help This option allows to select a slab allocator. config SLAB bool "SLAB" |
04385fc5e
|
1677 |
select HAVE_HARDENED_USERCOPY_ALLOCATOR |
81819f0fc
|
1678 1679 |
help The regular slab allocator that is established and known to work |
34013886e
|
1680 |
well in all environments. It organizes cache hot objects in |
02f562104
|
1681 |
per cpu and per node queues. |
81819f0fc
|
1682 1683 |
config SLUB |
81819f0fc
|
1684 |
bool "SLUB (Unqueued Allocator)" |
ed18adc1c
|
1685 |
select HAVE_HARDENED_USERCOPY_ALLOCATOR |
81819f0fc
|
1686 1687 1688 1689 1690 |
help SLUB is a slab allocator that minimizes cache line usage instead of managing queues of cached objects (SLAB approach). Per cpu caching is realized using slabs of objects instead of queues of objects. SLUB can use memory efficiently |
02f562104
|
1691 1692 |
and has enhanced diagnostics. SLUB is the default choice for a slab allocator. |
81819f0fc
|
1693 1694 |
config SLOB |
6a108a14f
|
1695 |
depends on EXPERT |
81819f0fc
|
1696 1697 |
bool "SLOB (Simple Allocator)" help |
372914582
|
1698 1699 1700 |
SLOB replaces the stock allocator with a drastically simpler allocator. SLOB is generally more space efficient but does not perform as well on large systems. |
81819f0fc
|
1701 1702 |
endchoice |
7660a6fdd
|
1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 |
config SLAB_MERGE_DEFAULT bool "Allow slab caches to be merged" default y help For reduced kernel memory fragmentation, slab caches can be merged when they share the same size and other characteristics. This carries a risk of kernel heap overflows being able to overwrite objects from merged caches (and more easily control cache layout), which makes such heap attacks easier to exploit by attackers. By keeping caches unmerged, these kinds of exploits can usually only damage objects in the same cache. To disable merging at runtime, "slab_nomerge" can be passed on the kernel command line. |
c7ce4f60a
|
1716 1717 |
config SLAB_FREELIST_RANDOM default n |
210e7a43f
|
1718 |
depends on SLAB || SLUB |
c7ce4f60a
|
1719 1720 |
bool "SLAB freelist randomization" help |
210e7a43f
|
1721 |
Randomizes the freelist order used on creating new pages. This |
c7ce4f60a
|
1722 1723 |
security feature reduces the predictability of the kernel slab allocator against heap overflows. |
2482ddec6
|
1724 1725 1726 1727 1728 1729 |
config SLAB_FREELIST_HARDENED bool "Harden slab freelist metadata" depends on SLUB help Many kernel heap attacks try to target slab cache metadata and other infrastructure. This options makes minor performance |
92bae787c
|
1730 |
sacrifices to harden the kernel slab allocator against common |
2482ddec6
|
1731 |
freelist exploit methods. |
e900a918b
|
1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 |
config SHUFFLE_PAGE_ALLOCATOR bool "Page allocator randomization" default SLAB_FREELIST_RANDOM && ACPI_NUMA help Randomization of the page allocator improves the average utilization of a direct-mapped memory-side-cache. See section 5.2.27 Heterogeneous Memory Attribute Table (HMAT) in the ACPI 6.2a specification for an example of how a platform advertises the presence of a memory-side-cache. There are also incidental security benefits as it reduces the predictability of page allocations to compliment SLAB_FREELIST_RANDOM, but the default granularity of shuffling on the "MAX_ORDER - 1" i.e, 10th order of pages is selected based on cache utilization benefits on x86. While the randomization improves cache utilization it may negatively impact workloads on platforms without a cache. For this reason, by default, the randomization is enabled only after runtime detection of a direct-mapped memory-side-cache. Otherwise, the randomization may be force enabled with the 'page_alloc.shuffle' kernel command line parameter. Say Y if unsure. |
345c905d1
|
1755 1756 |
config SLUB_CPU_PARTIAL default y |
b39ffbf8b
|
1757 |
depends on SLUB && SMP |
345c905d1
|
1758 1759 |
bool "SLUB per cpu partial cache" help |
92bae787c
|
1760 |
Per cpu partial caches accelerate objects allocation and freeing |
345c905d1
|
1761 1762 1763 1764 |
that is local to a processor at the price of more indeterminism in the latency of the free. On overflow these caches will be cleared which requires the taking of locks that may cause latency spikes. Typically one would choose no for a realtime system. |
ea6376395
|
1765 1766 |
config MMAP_ALLOW_UNINITIALIZED bool "Allow mmapped anonymous memory to be uninitialized" |
6a108a14f
|
1767 |
depends on EXPERT && !MMU |
ea6376395
|
1768 1769 1770 |
default n help Normally, and according to the Linux spec, anonymous memory obtained |
3903bf940
|
1771 |
from mmap() has its contents cleared before it is passed to |
ea6376395
|
1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 |
userspace. Enabling this config option allows you to request that mmap() skip that if it is given an MAP_UNINITIALIZED flag, thus providing a huge performance boost. If this option is not enabled, then the flag will be ignored. This is taken advantage of by uClibc's malloc(), and also by ELF-FDPIC binfmt's brk and stack allocator. Because of the obvious security issues, this option should only be enabled on embedded devices where you control what is run in userspace. Since that isn't generally a problem on no-MMU systems, it is normally safe to say Y here. See Documentation/nommu-mmap.txt for more information. |
091f6e26e
|
1786 1787 1788 1789 1790 |
config SYSTEM_DATA_VERIFICATION def_bool n select SYSTEM_TRUSTED_KEYRING select KEYS select CRYPTO |
d43de6c78
|
1791 |
select CRYPTO_RSA |
091f6e26e
|
1792 1793 |
select ASYMMETRIC_KEY_TYPE select ASYMMETRIC_PUBLIC_KEY_SUBTYPE |
091f6e26e
|
1794 1795 1796 1797 |
select ASN1 select OID_REGISTRY select X509_CERTIFICATE_PARSER select PKCS7_MESSAGE_PARSER |
82c04ff89
|
1798 |
help |
091f6e26e
|
1799 1800 1801 1802 |
Provide PKCS#7 message verification using the contents of the system trusted keyring to provide public keys. This then can be used for module verification, kexec image verification and firmware blob verification. |
82c04ff89
|
1803 |
|
125e56458
|
1804 |
config PROFILING |
b309a294e
|
1805 |
bool "Profiling support" |
125e56458
|
1806 1807 1808 |
help Say Y here to enable the extended profiling support mechanisms used by profilers such as OProfile. |
5f87f1121
|
1809 1810 1811 1812 |
# # Place an empty function call at each tracepoint site. Can be # dynamically changed for a probe function. # |
97e1c18e8
|
1813 |
config TRACEPOINTS |
5f87f1121
|
1814 |
bool |
97e1c18e8
|
1815 |
|
1da177e4c
|
1816 |
endmenu # General setup |
1572497cb
|
1817 |
source "arch/Kconfig" |
ae81f9e37
|
1818 |
config RT_MUTEXES |
6341e62b2
|
1819 |
bool |
ae81f9e37
|
1820 |
|
1da177e4c
|
1821 1822 1823 1824 |
config BASE_SMALL int default 0 if BASE_FULL default 1 if !BASE_FULL |
c8424e776
|
1825 1826 1827 |
config MODULE_SIG_FORMAT def_bool n select SYSTEM_DATA_VERIFICATION |
66da57332
|
1828 |
menuconfig MODULES |
1da177e4c
|
1829 |
bool "Enable loadable module support" |
11097a036
|
1830 |
option modules |
1da177e4c
|
1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 |
help Kernel modules are small pieces of compiled code which can be inserted in the running kernel, rather than being permanently built into the kernel. You use the "modprobe" tool to add (and sometimes remove) them. If you say Y here, many parts of the kernel can be built as modules (by answering M instead of Y where indicated): this is most useful for infrequently used options which are not required for booting. For more information, see the man pages for modprobe, lsmod, modinfo, insmod and rmmod. If you say Y here, you will need to run "make modules_install" to put the modules under /lib/modules/ where modprobe can find them (you may need to be root to do this). If unsure, say Y. |
0b0de1443
|
1848 |
if MODULES |
826e4506a
|
1849 1850 |
config MODULE_FORCE_LOAD bool "Forced module loading" |
826e4506a
|
1851 1852 |
default n help |
91e37a793
|
1853 1854 1855 |
Allow loading of modules without version information (ie. modprobe --force). Forced module loading sets the 'F' (forced) taint flag and is usually a really bad idea. |
826e4506a
|
1856 |
|
1da177e4c
|
1857 1858 |
config MODULE_UNLOAD bool "Module unloading" |
1da177e4c
|
1859 1860 1861 |
help Without this option you will not be able to unload any modules (note that some modules may not be unloadable |
f7f5b6755
|
1862 1863 |
anyway), which makes your kernel smaller, faster and simpler. If unsure, say Y. |
1da177e4c
|
1864 1865 1866 |
config MODULE_FORCE_UNLOAD bool "Forced module unloading" |
19c923998
|
1867 |
depends on MODULE_UNLOAD |
1da177e4c
|
1868 1869 1870 1871 1872 1873 |
help This option allows you to force a module to unload, even if the kernel believes it is unsafe: the kernel will remove the module without waiting for anyone to stop using it (using the -f option to rmmod). This is mainly for kernel developers and desperate users. If unsure, say N. |
1da177e4c
|
1874 |
config MODVERSIONS |
0d5416433
|
1875 |
bool "Module versioning support" |
1da177e4c
|
1876 1877 1878 1879 1880 1881 1882 |
help Usually, you have to use modules compiled with your kernel. Saying Y here makes it sometimes possible to use modules compiled for different kernels, by adding enough information to the modules to (hopefully) spot any changes which would make them incompatible with the kernel you are running. If unsure, say N. |
2ff2b7ec6
|
1883 1884 1885 1886 1887 1888 1889 |
config ASM_MODVERSIONS bool default HAVE_ASM_MODVERSIONS && MODVERSIONS help This enables module versioning for exported symbols also from assembly. This can be enabled only when the target architecture supports it. |
56067812d
|
1890 1891 1892 |
config MODULE_REL_CRCS bool depends on MODVERSIONS |
1da177e4c
|
1893 1894 |
config MODULE_SRCVERSION_ALL bool "Source checksum for all modules" |
1da177e4c
|
1895 1896 1897 1898 1899 1900 1901 1902 |
help Modules which contain a MODULE_VERSION get an extra "srcversion" field inserted into their modinfo section, which contains a sum of the source files which made it. This helps maintainers see exactly which source was used to build a module (since others sometimes change the module source without updating the version). With this option, such a "srcversion" field will be created for all modules. If unsure, say N. |
106a4ee25
|
1903 1904 |
config MODULE_SIG bool "Module signature verification" |
c8424e776
|
1905 |
select MODULE_SIG_FORMAT |
106a4ee25
|
1906 1907 1908 |
help Check modules for valid signatures upon load: the signature is simply appended to the module. For more information see |
cbdc82170
|
1909 |
<file:Documentation/admin-guide/module-signing.rst>. |
106a4ee25
|
1910 |
|
228c37ff9
|
1911 1912 1913 |
Note that this option adds the OpenSSL development packages as a kernel build dependency so that the signing tool can use its crypto library. |
49fcf732b
|
1914 1915 1916 1917 |
You should enable this option if you wish to use either CONFIG_SECURITY_LOCKDOWN_LSM or lockdown functionality imposed via another LSM - otherwise unsigned modules will be loadable regardless of the lockdown policy. |
ea0b6dcf7
|
1918 1919 1920 1921 |
!!!WARNING!!! If you enable this option, you MUST make sure that the module DOES NOT get stripped after being signed. This includes the debuginfo strip done by some packagers (such as rpmbuild) and inclusion into an initramfs that wants the module size reduced. |
106a4ee25
|
1922 1923 1924 1925 1926 1927 |
config MODULE_SIG_FORCE bool "Require modules to be validly signed" depends on MODULE_SIG help Reject unsigned modules or signed modules for which we don't have a key. Without this, such modules will simply taint the kernel. |
ea0b6dcf7
|
1928 |
|
d9d8d7ed4
|
1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 |
config MODULE_SIG_ALL bool "Automatically sign all modules" default y depends on MODULE_SIG help Sign all modules during make modules_install. Without this option, modules must be signed manually, using the scripts/sign-file tool. comment "Do not forget to sign required modules with scripts/sign-file" depends on MODULE_SIG_FORCE && !MODULE_SIG_ALL |
ea0b6dcf7
|
1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 |
choice prompt "Which hash algorithm should modules be signed with?" depends on MODULE_SIG help This determines which sort of hashing algorithm will be used during signature generation. This algorithm _must_ be built into the kernel directly so that signature verification can take place. It is not possible to load a signed module containing the algorithm to check the signature on that module. config MODULE_SIG_SHA1 bool "Sign modules with SHA-1" select CRYPTO_SHA1 config MODULE_SIG_SHA224 bool "Sign modules with SHA-224" select CRYPTO_SHA256 config MODULE_SIG_SHA256 bool "Sign modules with SHA-256" select CRYPTO_SHA256 config MODULE_SIG_SHA384 bool "Sign modules with SHA-384" select CRYPTO_SHA512 config MODULE_SIG_SHA512 bool "Sign modules with SHA-512" select CRYPTO_SHA512 endchoice |
227536740
|
1970 1971 1972 1973 1974 1975 1976 1977 |
config MODULE_SIG_HASH string depends on MODULE_SIG default "sha1" if MODULE_SIG_SHA1 default "sha224" if MODULE_SIG_SHA224 default "sha256" if MODULE_SIG_SHA256 default "sha384" if MODULE_SIG_SHA384 default "sha512" if MODULE_SIG_SHA512 |
beb50df39
|
1978 1979 |
config MODULE_COMPRESS bool "Compress modules on installation" |
beb50df39
|
1980 |
help |
beb50df39
|
1981 |
|
b6c09b512
|
1982 1983 |
Compresses kernel modules when 'make modules_install' is run; gzip or xz depending on "Compression algorithm" below. |
beb50df39
|
1984 |
|
b6c09b512
|
1985 |
module-init-tools MAY support gzip, and kmod MAY support gzip and xz. |
beb50df39
|
1986 |
|
b6c09b512
|
1987 1988 |
Out-of-tree kernel modules installed using Kbuild will also be compressed upon installation. |
beb50df39
|
1989 |
|
b6c09b512
|
1990 1991 |
Note: for modules inside an initrd or initramfs, it's more efficient to compress the whole initrd or initramfs instead. |
beb50df39
|
1992 |
|
b6c09b512
|
1993 1994 1995 |
Note: This is fully compatible with signed modules. If in doubt, say N. |
beb50df39
|
1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 |
choice prompt "Compression algorithm" depends on MODULE_COMPRESS default MODULE_COMPRESS_GZIP help This determines which sort of compression will be used during 'make modules_install'. GZIP (default) and XZ are supported. config MODULE_COMPRESS_GZIP bool "GZIP" config MODULE_COMPRESS_XZ bool "XZ" endchoice |
3d52ec5e5
|
2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
config MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS bool "Allow loading of modules with missing namespace imports" help Symbols exported with EXPORT_SYMBOL_NS*() are considered exported in a namespace. A module that makes use of a symbol exported with such a namespace is required to import the namespace via MODULE_IMPORT_NS(). There is no technical reason to enforce correct namespace imports, but it creates consistency between symbols defining namespaces and users importing namespaces they make use of. This option relaxes this requirement and lifts the enforcement when loading a module. If unsure, say N. |
efd9763d8
|
2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 |
config UNUSED_SYMBOLS bool "Enable unused/obsolete exported symbols" default y if X86 help Unused but exported symbols make the kernel needlessly bigger. For that reason most of these unused exports will soon be removed. This option is provided temporarily to provide a transition period in case some external kernel module needs one of these symbols anyway. If you encounter such a case in your module, consider if you are actually using the right API. (rationale: since nobody in the kernel is using this in a module, there is a pretty good chance it's actually the wrong interface to use). If you really need the symbol, please send a mail to the linux kernel mailing list mentioning the symbol and why you really need it, and what the merge plan to the mainline kernel for your module is. |
dbacb0ef6
|
2041 2042 |
config TRIM_UNUSED_KSYMS bool "Trim unused exported kernel symbols" |
d189c2a4b
|
2043 |
depends on !UNUSED_SYMBOLS |
dbacb0ef6
|
2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 |
help The kernel and some modules make many symbols available for other modules to use via EXPORT_SYMBOL() and variants. Depending on the set of modules being selected in your kernel configuration, many of those exported symbols might never be used. This option allows for unused exported symbols to be dropped from the build. In turn, this provides the compiler more opportunities (especially when using LTO) for optimizing the code and reducing binary size. This might have some security advantages as well. |
f1cb637e7
|
2054 |
If unsure, or if you need to build out-of-tree modules, say N. |
dbacb0ef6
|
2055 |
|
1518c633d
|
2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 |
config UNUSED_KSYMS_WHITELIST string "Whitelist of symbols to keep in ksymtab" depends on TRIM_UNUSED_KSYMS help By default, all unused exported symbols will be un-exported from the build when TRIM_UNUSED_KSYMS is selected. UNUSED_KSYMS_WHITELIST allows to whitelist symbols that must be kept exported at all times, even in absence of in-tree users. The value to set here is the path to a text file containing the list of symbols, one per line. The path can be absolute, or relative to the kernel source tree. |
0b0de1443
|
2068 |
endif # MODULES |
6c9692e2d
|
2069 2070 2071 |
config MODULES_TREE_LOOKUP def_bool y depends on PERF_EVENTS || TRACING |
98a79d6a5
|
2072 2073 2074 |
config INIT_ALL_POSSIBLE bool help |
5f054e31c
|
2075 2076 |
Back when each arch used to define their own cpu_online_mask and cpu_possible_mask, some of them chose to initialize cpu_possible_mask |
98a79d6a5
|
2077 2078 |
with all 1s, and others with all 0s. When they were centralised, it was better to provide this option than to break all the archs |
692105b8a
|
2079 |
and have several arch maintainers pursuing me down dark alleys. |
98a79d6a5
|
2080 |
|
3a65dfe8c
|
2081 |
source "block/Kconfig" |
e98c32029
|
2082 2083 2084 |
config PREEMPT_NOTIFIERS bool |
e260be673
|
2085 |
|
16295bec6
|
2086 2087 2088 |
config PADATA depends on SMP bool |
4520c6a49
|
2089 2090 2091 2092 2093 2094 2095 |
config ASN1 tristate help Build a simple ASN.1 grammar compiler that produces a bytecode output that can be interpreted by the ASN.1 stream decoder and used to inform it as to what tags are to be expected in a stream and what functions to call on what tags. |
6beb00092
|
2096 |
source "kernel/Kconfig.locks" |
e61938a92
|
2097 2098 2099 |
config ARCH_HAS_SYNC_CORE_BEFORE_USERMODE bool |
1bd21c6c2
|
2100 2101 |
# It may be useful for an architecture to override the definitions of the |
7303e30ec
|
2102 2103 2104 2105 2106 2107 |
# SYSCALL_DEFINE() and __SYSCALL_DEFINEx() macros in <linux/syscalls.h> # and the COMPAT_ variants in <linux/compat.h>, in particular to use a # different calling convention for syscalls. They can also override the # macros for not-implemented syscalls in kernel/sys_ni.c and # kernel/time/posix-stubs.c. All these overrides need to be available in # <asm/syscall_wrapper.h>. |
1bd21c6c2
|
2108 2109 |
config ARCH_HAS_SYSCALL_WRAPPER def_bool n |