Blame view
arch/Kconfig
15.2 KB
fb32e03fd
|
1 2 3 |
# # General architecture dependent options # |
125e56458
|
4 5 |
config OPROFILE |
b309a294e
|
6 |
tristate "OProfile system profiling" |
125e56458
|
7 8 |
depends on PROFILING depends on HAVE_OPROFILE |
d69d59f49
|
9 |
select RING_BUFFER |
9a5963eb4
|
10 |
select RING_BUFFER_ALLOW_SWAP |
125e56458
|
11 12 13 14 15 16 |
help OProfile is a profiling system capable of profiling the whole system, include the kernel, kernel modules, libraries, and applications. If unsure, say N. |
4d4036e0e
|
17 18 19 20 21 22 23 24 25 26 27 |
config OPROFILE_EVENT_MULTIPLEX bool "OProfile multiplexing support (EXPERIMENTAL)" default n depends on OPROFILE && X86 help The number of hardware counters is limited. The multiplexing feature enables OProfile to gather more events than counters are provided by the hardware. This is realized by switching between events at an user specified time interval. If unsure, say N. |
125e56458
|
28 |
config HAVE_OPROFILE |
9ba16087d
|
29 |
bool |
125e56458
|
30 |
|
dcfce4a09
|
31 32 33 |
config OPROFILE_NMI_TIMER def_bool y depends on PERF_EVENTS && HAVE_PERF_EVENTS_NMI |
125e56458
|
34 35 |
config KPROBES bool "Kprobes" |
05ed160e8
|
36 |
depends on MODULES |
125e56458
|
37 |
depends on HAVE_KPROBES |
05ed160e8
|
38 |
select KALLSYMS |
125e56458
|
39 40 41 42 43 44 |
help Kprobes allows you to trap at almost any kernel address and execute a callback function. register_kprobe() establishes a probepoint and specifies the callback. Kprobes is useful for kernel debugging, non-intrusive instrumentation and testing. If in doubt, say "N". |
45f81b1c9
|
45 |
config JUMP_LABEL |
c5905afb0
|
46 |
bool "Optimize very unlikely/likely branches" |
45f81b1c9
|
47 48 |
depends on HAVE_ARCH_JUMP_LABEL help |
c5905afb0
|
49 50 51 52 53 54 55 |
This option enables a transparent branch optimization that makes certain almost-always-true or almost-always-false branch conditions even cheaper to execute within the kernel. Certain performance-sensitive kernel code, such as trace points, scheduler functionality, networking code and KVM have such branches and include support for this optimization technique. |
45f81b1c9
|
56 |
If it is detected that the compiler has support for "asm goto", |
c5905afb0
|
57 58 59 60 61 62 63 64 |
the kernel will compile such branches with just a nop instruction. When the condition flag is toggled to true, the nop will be converted to a jump instruction to execute the conditional block of instructions. This technique lowers overhead and stress on the branch prediction of the processor and generally makes the kernel faster. The update of the condition is slower, but those are always very rare. |
45f81b1c9
|
65 |
|
c5905afb0
|
66 67 |
( On 32-bit x86, the necessary options added to the compiler flags may increase the size of the kernel slightly. ) |
45f81b1c9
|
68 |
|
afd66255b
|
69 |
config OPTPROBES |
5cc718b9d
|
70 71 |
def_bool y depends on KPROBES && HAVE_OPTPROBES |
afd66255b
|
72 |
depends on !PREEMPT |
afd66255b
|
73 |
|
e7dbfe349
|
74 75 76 77 78 79 80 81 |
config KPROBES_ON_FTRACE def_bool y depends on KPROBES && HAVE_KPROBES_ON_FTRACE depends on DYNAMIC_FTRACE_WITH_REGS help If function tracer is enabled and the arch supports full passing of pt_regs to function tracing, then kprobes can optimize on top of function tracing. |
2b1444983
|
82 |
config UPROBES |
7b2d81d48
|
83 |
bool "Transparent user-space probes (EXPERIMENTAL)" |
ec83db0f7
|
84 |
depends on UPROBE_EVENT && PERF_EVENTS |
2b1444983
|
85 |
default n |
22b361d1d
|
86 |
select PERCPU_RWSEM |
2b1444983
|
87 |
help |
7b2d81d48
|
88 89 90 91 92 93 94 95 96 |
Uprobes is the user-space counterpart to kprobes: they enable instrumentation applications (such as 'perf probe') to establish unintrusive probes in user-space binaries and libraries, by executing handler functions when the probes are hit by user-space applications. ( These probes come in the form of single-byte breakpoints, managed by the kernel and kept transparent to the probed application. ) |
2b1444983
|
97 98 |
If in doubt, say "N". |
c19fa94a8
|
99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 |
config HAVE_64BIT_ALIGNED_ACCESS def_bool 64BIT && !HAVE_EFFICIENT_UNALIGNED_ACCESS help Some architectures require 64 bit accesses to be 64 bit aligned, which also requires structs containing 64 bit values to be 64 bit aligned too. This includes some 32 bit architectures which can do 64 bit accesses, as well as 64 bit architectures without unaligned access. This symbol should be selected by an architecture if 64 bit accesses are required to be 64 bit aligned in this way even though it is not a 64 bit architecture. See Documentation/unaligned-memory-access.txt for more information on the topic of unaligned memory accesses. |
58340a07c
|
114 |
config HAVE_EFFICIENT_UNALIGNED_ACCESS |
9ba16087d
|
115 |
bool |
58340a07c
|
116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 |
help Some architectures are unable to perform unaligned accesses without the use of get_unaligned/put_unaligned. Others are unable to perform such accesses efficiently (e.g. trap on unaligned access and require fixing it up in the exception handler.) This symbol should be selected by an architecture if it can perform unaligned accesses efficiently to allow different code paths to be selected for these cases. Some network drivers, for example, could opt to not fix up alignment problems with received packets if doing so would not help much. See Documentation/unaligned-memory-access.txt for more information on the topic of unaligned memory accesses. |
cf66bb93e
|
132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 |
config ARCH_USE_BUILTIN_BSWAP bool help Modern versions of GCC (since 4.4) have builtin functions for handling byte-swapping. Using these, instead of the old inline assembler that the architecture code provides in the __arch_bswapXX() macros, allows the compiler to see what's happening and offers more opportunity for optimisation. In particular, the compiler will be able to combine the byteswap with a nearby load or store and use load-and-swap or store-and-swap instructions if the architecture has them. It should almost *never* result in code which is worse than the hand-coded assembler in <asm/swab.h>. But just in case it does, the use of the builtins is optional. Any architecture with load-and-swap or store-and-swap instructions should set this. And it shouldn't hurt to set it on architectures that don't have such instructions. |
9edddaa20
|
150 151 152 |
config KRETPROBES def_bool y depends on KPROBES && HAVE_KRETPROBES |
7c68af6e3
|
153 154 155 156 157 158 |
config USER_RETURN_NOTIFIER bool depends on HAVE_USER_RETURN_NOTIFIER help Provide a kernel-internal notification when a cpu is about to switch to user mode. |
28b2ee20c
|
159 |
config HAVE_IOREMAP_PROT |
9ba16087d
|
160 |
bool |
28b2ee20c
|
161 |
|
125e56458
|
162 |
config HAVE_KPROBES |
9ba16087d
|
163 |
bool |
9edddaa20
|
164 165 |
config HAVE_KRETPROBES |
9ba16087d
|
166 |
bool |
74bc7ceeb
|
167 |
|
afd66255b
|
168 169 |
config HAVE_OPTPROBES bool |
d314d74c6
|
170 |
|
e7dbfe349
|
171 172 |
config HAVE_KPROBES_ON_FTRACE bool |
d314d74c6
|
173 174 |
config HAVE_NMI_WATCHDOG bool |
1f5a4ad97
|
175 176 177 178 179 180 |
# # An arch should select this if it provides all these things: # # task_pt_regs() in asm/processor.h or asm/ptrace.h # arch_has_single_step() if there is hardware single-step support # arch_has_block_step() if there is hardware block-step support |
1f5a4ad97
|
181 182 183 184 185 186 187 188 |
# asm/syscall.h supplying asm-generic/syscall.h interface # linux/regset.h user_regset interfaces # CORE_DUMP_USE_REGSET #define'd in linux/elf.h # TIF_SYSCALL_TRACE calls tracehook_report_syscall_{entry,exit} # TIF_NOTIFY_RESUME calls tracehook_notify_resume() # signal delivery calls tracehook_signal_handler() # config HAVE_ARCH_TRACEHOOK |
9ba16087d
|
189 |
bool |
1f5a4ad97
|
190 |
|
74bc7ceeb
|
191 |
config HAVE_DMA_ATTRS |
9ba16087d
|
192 |
bool |
3d4422332
|
193 |
|
c64be2bb1
|
194 195 |
config HAVE_DMA_CONTIGUOUS bool |
29d5e0476
|
196 197 |
config GENERIC_SMP_IDLE_THREAD bool |
485cf5dac
|
198 199 |
config GENERIC_IDLE_POLL_SETUP bool |
a6359d1ee
|
200 201 |
# Select if arch init_task initializer is different to init/init_task.c config ARCH_INIT_TASK |
a4a2eb490
|
202 |
bool |
f5e102873
|
203 204 205 206 207 208 209 |
# Select if arch has its private alloc_task_struct() function config ARCH_TASK_STRUCT_ALLOCATOR bool # Select if arch has its private alloc_thread_info() function config ARCH_THREAD_INFO_ALLOCATOR bool |
f850c30c8
|
210 211 |
config HAVE_REGS_AND_STACK_ACCESS_API bool |
e01292b1f
|
212 213 214 215 216 |
help This symbol should be selected by an architecure if it supports the API needed to access registers and stack entries from pt_regs, declared in asm/ptrace.h For example the kprobes-based event tracer needs this API. |
f850c30c8
|
217 |
|
9483a578d
|
218 |
config HAVE_CLK |
9ba16087d
|
219 |
bool |
9483a578d
|
220 221 222 |
help The <linux/clk.h> calls support software clock gating and thus are a key power management tool on many systems. |
5ee00bd46
|
223 224 |
config HAVE_DMA_API_DEBUG bool |
36cd3c9f9
|
225 |
|
62a038d34
|
226 227 |
config HAVE_HW_BREAKPOINT bool |
99e8c5a3b
|
228 |
depends on PERF_EVENTS |
62a038d34
|
229 |
|
0102752e4
|
230 231 232 233 234 235 236 237 238 239 |
config HAVE_MIXED_BREAKPOINTS_REGS bool depends on HAVE_HW_BREAKPOINT help Depending on the arch implementation of hardware breakpoints, some of them have separate registers for data and instruction breakpoints addresses, others have mixed registers to store them but define the access type in a control register. Select this option if your arch implements breakpoints under the latter fashion. |
7c68af6e3
|
240 241 |
config HAVE_USER_RETURN_NOTIFIER bool |
a1922ed66
|
242 |
|
c01d43233
|
243 244 |
config HAVE_PERF_EVENTS_NMI bool |
23637d477
|
245 246 247 248 |
help System hardware can generate an NMI using the perf event subsystem. Also has support for calculating CPU cycle events to determine how many clock cycles in a given period. |
c01d43233
|
249 |
|
c5e63197d
|
250 251 252 253 254 |
config HAVE_PERF_REGS bool help Support selective register dumps for perf events. This includes bit-mapping of each registers and a unique architecture id. |
c5ebcedb5
|
255 256 257 258 259 260 |
config HAVE_PERF_USER_STACK_DUMP bool help Support user stack dumps for perf event samples. This needs access to the user stack pointer which is not unified across architectures. |
bf5438fca
|
261 262 |
config HAVE_ARCH_JUMP_LABEL bool |
267239116
|
263 264 |
config HAVE_RCU_TABLE_FREE bool |
df013ffb8
|
265 266 |
config ARCH_HAVE_NMI_SAFE_CMPXCHG bool |
43570fd2f
|
267 268 269 270 271 272 273 |
config HAVE_ALIGNED_STRUCT_PAGE bool help This makes sure that struct pages are double word aligned and that e.g. the SLUB allocator can perform double word atomic operations on a struct page for better performance. However selecting this might increase the size of a struct page by a word. |
4156153c4
|
274 275 |
config HAVE_CMPXCHG_LOCAL bool |
2565409fc
|
276 277 |
config HAVE_CMPXCHG_DOUBLE bool |
c1d7e01d7
|
278 279 280 281 282 |
config ARCH_WANT_IPC_PARSE_VERSION bool config ARCH_WANT_COMPAT_IPC_PARSE_VERSION bool |
48b25c43e
|
283 |
config ARCH_WANT_OLD_COMPAT_IPC |
c1d7e01d7
|
284 |
select ARCH_WANT_COMPAT_IPC_PARSE_VERSION |
48b25c43e
|
285 |
bool |
e2cfabdfd
|
286 287 288 |
config HAVE_ARCH_SECCOMP_FILTER bool help |
fb0fadf9b
|
289 |
An arch should select this symbol if it provides all of these things: |
bb6ea4301
|
290 291 292 293 |
- syscall_get_arch() - syscall_get_arguments() - syscall_rollback() - syscall_set_return_value() |
fb0fadf9b
|
294 295 296 297 |
- SIGSYS siginfo_t support - secure_computing is called from a ptrace_event()-safe context - secure_computing return value is checked and a return value of -1 results in the system call being skipped immediately. |
e2cfabdfd
|
298 299 300 301 302 303 304 305 306 307 |
config SECCOMP_FILTER def_bool y depends on HAVE_ARCH_SECCOMP_FILTER && SECCOMP && NET help Enable tasks to build secure computing environments defined in terms of Berkeley Packet Filter programs which implement task-defined system call filtering polices. See Documentation/prctl/seccomp_filter.txt for details. |
19952a920
|
308 309 310 311 312 313 314 315 |
config HAVE_CC_STACKPROTECTOR bool help An arch should select this symbol if: - its compiler supports the -fstack-protector option - it has implemented a stack canary (e.g. __stack_chk_guard) config CC_STACKPROTECTOR |
8779657d2
|
316 317 318 319 320 321 322 |
def_bool n help Set when a stack-protector mode is enabled, so that the build can enable kernel-side support for the GCC feature. choice prompt "Stack Protector buffer overflow detection" |
19952a920
|
323 |
depends on HAVE_CC_STACKPROTECTOR |
8779657d2
|
324 |
default CC_STACKPROTECTOR_NONE |
19952a920
|
325 |
help |
8779657d2
|
326 |
This option turns on the "stack-protector" GCC feature. This |
19952a920
|
327 328 329 330 331 332 |
feature puts, at the beginning of functions, a canary value on the stack just before the return address, and validates the value just before actually returning. Stack based buffer overflows (that need to overwrite this return address) now also overwrite the canary, which gets detected and the attack is then neutralized via a kernel panic. |
8779657d2
|
333 334 335 336 337 338 339 340 341 342 343 |
config CC_STACKPROTECTOR_NONE bool "None" help Disable "stack-protector" GCC feature. config CC_STACKPROTECTOR_REGULAR bool "Regular" select CC_STACKPROTECTOR help Functions will have the stack-protector canary logic added if they have an 8-byte or larger character array on the stack. |
19952a920
|
344 |
This feature requires gcc version 4.2 or above, or a distribution |
8779657d2
|
345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 |
gcc with the feature backported ("-fstack-protector"). On an x86 "defconfig" build, this feature adds canary checks to about 3% of all kernel functions, which increases kernel code size by about 0.3%. config CC_STACKPROTECTOR_STRONG bool "Strong" select CC_STACKPROTECTOR help Functions will have the stack-protector canary logic added in any of the following conditions: - local variable's address used as part of the right hand side of an assignment or function argument - local variable is an array (or union containing an array), regardless of array type or length - uses register local variables This feature requires gcc version 4.9 or above, or a distribution gcc with the feature backported ("-fstack-protector-strong"). On an x86 "defconfig" build, this feature adds canary checks to about 20% of all kernel functions, which increases the kernel code size by about 2%. endchoice |
19952a920
|
372 |
|
91d1aa43d
|
373 |
config HAVE_CONTEXT_TRACKING |
2b1d5024e
|
374 375 |
bool help |
91d1aa43d
|
376 377 378 379 380 381 382 |
Provide kernel/user boundaries probes necessary for subsystems that need it, such as userspace RCU extended quiescent state. Syscalls need to be wrapped inside user_exit()-user_enter() through the slow path using TIF_NOHZ flag. Exceptions handlers must be wrapped as well. Irqs are already protected inside rcu_irq_enter/rcu_irq_exit() but preemption or signal handling on irq exit still need to be protected. |
2b1d5024e
|
383 |
|
b952741c8
|
384 385 |
config HAVE_VIRT_CPU_ACCOUNTING bool |
554b0004d
|
386 387 388 389 390 391 392 393 394 395 |
config HAVE_VIRT_CPU_ACCOUNTING_GEN bool default y if 64BIT help With VIRT_CPU_ACCOUNTING_GEN, cputime_t becomes 64-bit. Before enabling this option, arch code must be audited to ensure there are no races in concurrent read/write of cputime_t. For example, reading/writing 64-bit cputime_t on some 32-bit arches may require multiple accesses, so proper locking is needed to protect against concurrent accesses. |
fdf9c3565
|
396 397 398 399 400 |
config HAVE_IRQ_TIME_ACCOUNTING bool help Archs need to ensure they use a high enough resolution clock to support irq time accounting and then call enable_sched_clock_irqtime(). |
15626062f
|
401 402 |
config HAVE_ARCH_TRANSPARENT_HUGEPAGE bool |
0f8975ec4
|
403 404 |
config HAVE_ARCH_SOFT_DIRTY bool |
786d35d45
|
405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 |
config HAVE_MOD_ARCH_SPECIFIC bool help The arch uses struct mod_arch_specific to store data. Many arches just need a simple module loader without arch specific data - those should not enable this. config MODULES_USE_ELF_RELA bool help Modules only use ELF RELA relocations. Modules with ELF REL relocations will give an error. config MODULES_USE_ELF_REL bool help Modules only use ELF REL relocations. Modules with ELF RELA relocations will give an error. |
b92021b09
|
423 424 425 426 427 |
config HAVE_UNDERSCORE_SYMBOL_PREFIX bool help Some architectures generate an _ in front of C symbols; things like module loading and assembly files need to know about this. |
cc1f02745
|
428 429 430 431 432 433 434 435 436 |
config HAVE_IRQ_EXIT_ON_IRQ_STACK bool help Architecture doesn't only execute the irq handler on the irq stack but also irq_exit(). This way we can process softirqs on this irq stack instead of switching to a new one when we call __do_softirq() in the end of an hardirq. This spares a stack switch and improves cache usage on softirq processing. |
d2125043a
|
437 438 439 440 441 442 443 444 445 446 447 448 449 |
# # ABI hall of shame # config CLONE_BACKWARDS bool help Architecture has tls passed as the 4th argument of clone(2), not the 5th one. config CLONE_BACKWARDS2 bool help Architecture has the first two arguments of clone(2) swapped. |
dfa9771a7
|
450 451 452 453 454 |
config CLONE_BACKWARDS3 bool help Architecture has tls passed as the 3rd argument of clone(2), not the 5th one. |
eaca6eae3
|
455 456 457 458 |
config ODD_RT_SIGACTION bool help Architecture has unusual rt_sigaction(2) arguments |
0a0e8cdf7
|
459 460 461 462 463 464 465 466 467 |
config OLD_SIGSUSPEND bool help Architecture has old sigsuspend(2) syscall, of one-argument variety config OLD_SIGSUSPEND3 bool help Even weirder antique ABI - three-argument sigsuspend(2) |
495dfbf76
|
468 469 470 471 472 473 474 475 476 477 |
config OLD_SIGACTION bool help Architecture has old sigaction(2) syscall. Nope, not the same as OLD_SIGSUSPEND | OLD_SIGSUSPEND3 - alpha has sigsuspend(2), but fairly different variant of sigaction(2), thanks to OSF/1 compatibility... config COMPAT_OLD_SIGACTION bool |
2521f2c22
|
478 |
source "kernel/gcov/Kconfig" |