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