2 # General architecture dependent options
6 tristate "OProfile system profiling"
8 depends on HAVE_OPROFILE
10 select RING_BUFFER_ALLOW_SWAP
12 OProfile is a profiling system capable of profiling the
13 whole system, include the kernel, kernel modules, libraries,
18 config OPROFILE_EVENT_MULTIPLEX
19 bool "OProfile multiplexing support (EXPERIMENTAL)"
21 depends on OPROFILE && X86
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.
35 depends on KALLSYMS && MODULES
36 depends on HAVE_KPROBES
38 Kprobes allows you to trap at almost any kernel address and
39 execute a callback function. register_kprobe() establishes
40 a probepoint and specifies the callback. Kprobes is useful
41 for kernel debugging, non-intrusive instrumentation and testing.
45 bool "Kprobes jump optimization support (EXPERIMENTAL)"
49 depends on HAVE_OPTPROBES
52 This option will allow kprobes to optimize breakpoint to
53 a jump for reducing its overhead.
55 config HAVE_EFFICIENT_UNALIGNED_ACCESS
58 Some architectures are unable to perform unaligned accesses
59 without the use of get_unaligned/put_unaligned. Others are
60 unable to perform such accesses efficiently (e.g. trap on
61 unaligned access and require fixing it up in the exception
64 This symbol should be selected by an architecture if it can
65 perform unaligned accesses efficiently to allow different
66 code paths to be selected for these cases. Some network
67 drivers, for example, could opt to not fix up alignment
68 problems with received packets if doing so would not help
71 See Documentation/unaligned-memory-access.txt for more
72 information on the topic of unaligned memory accesses.
74 config HAVE_SYSCALL_WRAPPERS
79 depends on KPROBES && HAVE_KRETPROBES
81 config USER_RETURN_NOTIFIER
83 depends on HAVE_USER_RETURN_NOTIFIER
85 Provide a kernel-internal notification when a cpu is about to
88 config HAVE_IOREMAP_PROT
94 config HAVE_KRETPROBES
100 # An arch should select this if it provides all these things:
102 # task_pt_regs() in asm/processor.h or asm/ptrace.h
103 # arch_has_single_step() if there is hardware single-step support
104 # arch_has_block_step() if there is hardware block-step support
105 # asm/syscall.h supplying asm-generic/syscall.h interface
106 # linux/regset.h user_regset interfaces
107 # CORE_DUMP_USE_REGSET #define'd in linux/elf.h
108 # TIF_SYSCALL_TRACE calls tracehook_report_syscall_{entry,exit}
109 # TIF_NOTIFY_RESUME calls tracehook_notify_resume()
110 # signal delivery calls tracehook_signal_handler()
112 config HAVE_ARCH_TRACEHOOK
115 config HAVE_DMA_ATTRS
118 config USE_GENERIC_SMP_HELPERS
121 config HAVE_REGS_AND_STACK_ACCESS_API
124 This symbol should be selected by an architecure if it supports
125 the API needed to access registers and stack entries from pt_regs,
126 declared in asm/ptrace.h
127 For example the kprobes-based event tracer needs this API.
132 The <linux/clk.h> calls support software clock gating and
133 thus are a key power management tool on many systems.
135 config HAVE_DMA_API_DEBUG
138 config HAVE_DEFAULT_NO_SPIN_MUTEXES
141 config HAVE_HW_BREAKPOINT
143 depends on PERF_EVENTS
145 config HAVE_USER_RETURN_NOTIFIER
148 source "kernel/gcov/Kconfig"