Kconfig 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388
  1. #
  2. # General architecture dependent options
  3. #
  4. config OPROFILE
  5. tristate "OProfile system profiling"
  6. depends on PROFILING
  7. depends on HAVE_OPROFILE
  8. select RING_BUFFER
  9. select RING_BUFFER_ALLOW_SWAP
  10. help
  11. OProfile is a profiling system capable of profiling the
  12. whole system, include the kernel, kernel modules, libraries,
  13. and applications.
  14. If unsure, say N.
  15. config OPROFILE_EVENT_MULTIPLEX
  16. bool "OProfile multiplexing support (EXPERIMENTAL)"
  17. default n
  18. depends on OPROFILE && X86
  19. help
  20. The number of hardware counters is limited. The multiplexing
  21. feature enables OProfile to gather more events than counters
  22. are provided by the hardware. This is realized by switching
  23. between events at an user specified time interval.
  24. If unsure, say N.
  25. config HAVE_OPROFILE
  26. bool
  27. config OPROFILE_NMI_TIMER
  28. def_bool y
  29. depends on PERF_EVENTS && HAVE_PERF_EVENTS_NMI
  30. config KPROBES
  31. bool "Kprobes"
  32. depends on MODULES
  33. depends on HAVE_KPROBES
  34. select KALLSYMS
  35. help
  36. Kprobes allows you to trap at almost any kernel address and
  37. execute a callback function. register_kprobe() establishes
  38. a probepoint and specifies the callback. Kprobes is useful
  39. for kernel debugging, non-intrusive instrumentation and testing.
  40. If in doubt, say "N".
  41. config JUMP_LABEL
  42. bool "Optimize very unlikely/likely branches"
  43. depends on HAVE_ARCH_JUMP_LABEL
  44. help
  45. This option enables a transparent branch optimization that
  46. makes certain almost-always-true or almost-always-false branch
  47. conditions even cheaper to execute within the kernel.
  48. Certain performance-sensitive kernel code, such as trace points,
  49. scheduler functionality, networking code and KVM have such
  50. branches and include support for this optimization technique.
  51. If it is detected that the compiler has support for "asm goto",
  52. the kernel will compile such branches with just a nop
  53. instruction. When the condition flag is toggled to true, the
  54. nop will be converted to a jump instruction to execute the
  55. conditional block of instructions.
  56. This technique lowers overhead and stress on the branch prediction
  57. of the processor and generally makes the kernel faster. The update
  58. of the condition is slower, but those are always very rare.
  59. ( On 32-bit x86, the necessary options added to the compiler
  60. flags may increase the size of the kernel slightly. )
  61. config OPTPROBES
  62. def_bool y
  63. depends on KPROBES && HAVE_OPTPROBES
  64. depends on !PREEMPT
  65. config KPROBES_ON_FTRACE
  66. def_bool y
  67. depends on KPROBES && HAVE_KPROBES_ON_FTRACE
  68. depends on DYNAMIC_FTRACE_WITH_REGS
  69. help
  70. If function tracer is enabled and the arch supports full
  71. passing of pt_regs to function tracing, then kprobes can
  72. optimize on top of function tracing.
  73. config UPROBES
  74. bool "Transparent user-space probes (EXPERIMENTAL)"
  75. depends on UPROBE_EVENT && PERF_EVENTS
  76. default n
  77. select PERCPU_RWSEM
  78. help
  79. Uprobes is the user-space counterpart to kprobes: they
  80. enable instrumentation applications (such as 'perf probe')
  81. to establish unintrusive probes in user-space binaries and
  82. libraries, by executing handler functions when the probes
  83. are hit by user-space applications.
  84. ( These probes come in the form of single-byte breakpoints,
  85. managed by the kernel and kept transparent to the probed
  86. application. )
  87. If in doubt, say "N".
  88. config HAVE_EFFICIENT_UNALIGNED_ACCESS
  89. bool
  90. help
  91. Some architectures are unable to perform unaligned accesses
  92. without the use of get_unaligned/put_unaligned. Others are
  93. unable to perform such accesses efficiently (e.g. trap on
  94. unaligned access and require fixing it up in the exception
  95. handler.)
  96. This symbol should be selected by an architecture if it can
  97. perform unaligned accesses efficiently to allow different
  98. code paths to be selected for these cases. Some network
  99. drivers, for example, could opt to not fix up alignment
  100. problems with received packets if doing so would not help
  101. much.
  102. See Documentation/unaligned-memory-access.txt for more
  103. information on the topic of unaligned memory accesses.
  104. config ARCH_USE_BUILTIN_BSWAP
  105. bool
  106. help
  107. Modern versions of GCC (since 4.4) have builtin functions
  108. for handling byte-swapping. Using these, instead of the old
  109. inline assembler that the architecture code provides in the
  110. __arch_bswapXX() macros, allows the compiler to see what's
  111. happening and offers more opportunity for optimisation. In
  112. particular, the compiler will be able to combine the byteswap
  113. with a nearby load or store and use load-and-swap or
  114. store-and-swap instructions if the architecture has them. It
  115. should almost *never* result in code which is worse than the
  116. hand-coded assembler in <asm/swab.h>. But just in case it
  117. does, the use of the builtins is optional.
  118. Any architecture with load-and-swap or store-and-swap
  119. instructions should set this. And it shouldn't hurt to set it
  120. on architectures that don't have such instructions.
  121. config HAVE_SYSCALL_WRAPPERS
  122. bool
  123. config KRETPROBES
  124. def_bool y
  125. depends on KPROBES && HAVE_KRETPROBES
  126. config USER_RETURN_NOTIFIER
  127. bool
  128. depends on HAVE_USER_RETURN_NOTIFIER
  129. help
  130. Provide a kernel-internal notification when a cpu is about to
  131. switch to user mode.
  132. config HAVE_IOREMAP_PROT
  133. bool
  134. config HAVE_KPROBES
  135. bool
  136. config HAVE_KRETPROBES
  137. bool
  138. config HAVE_OPTPROBES
  139. bool
  140. config HAVE_KPROBES_ON_FTRACE
  141. bool
  142. config HAVE_NMI_WATCHDOG
  143. bool
  144. #
  145. # An arch should select this if it provides all these things:
  146. #
  147. # task_pt_regs() in asm/processor.h or asm/ptrace.h
  148. # arch_has_single_step() if there is hardware single-step support
  149. # arch_has_block_step() if there is hardware block-step support
  150. # asm/syscall.h supplying asm-generic/syscall.h interface
  151. # linux/regset.h user_regset interfaces
  152. # CORE_DUMP_USE_REGSET #define'd in linux/elf.h
  153. # TIF_SYSCALL_TRACE calls tracehook_report_syscall_{entry,exit}
  154. # TIF_NOTIFY_RESUME calls tracehook_notify_resume()
  155. # signal delivery calls tracehook_signal_handler()
  156. #
  157. config HAVE_ARCH_TRACEHOOK
  158. bool
  159. config HAVE_DMA_ATTRS
  160. bool
  161. config HAVE_DMA_CONTIGUOUS
  162. bool
  163. config USE_GENERIC_SMP_HELPERS
  164. bool
  165. config GENERIC_SMP_IDLE_THREAD
  166. bool
  167. # Select if arch init_task initializer is different to init/init_task.c
  168. config ARCH_INIT_TASK
  169. bool
  170. # Select if arch has its private alloc_task_struct() function
  171. config ARCH_TASK_STRUCT_ALLOCATOR
  172. bool
  173. # Select if arch has its private alloc_thread_info() function
  174. config ARCH_THREAD_INFO_ALLOCATOR
  175. bool
  176. config HAVE_REGS_AND_STACK_ACCESS_API
  177. bool
  178. help
  179. This symbol should be selected by an architecure if it supports
  180. the API needed to access registers and stack entries from pt_regs,
  181. declared in asm/ptrace.h
  182. For example the kprobes-based event tracer needs this API.
  183. config HAVE_CLK
  184. bool
  185. help
  186. The <linux/clk.h> calls support software clock gating and
  187. thus are a key power management tool on many systems.
  188. config HAVE_DMA_API_DEBUG
  189. bool
  190. config HAVE_HW_BREAKPOINT
  191. bool
  192. depends on PERF_EVENTS
  193. config HAVE_MIXED_BREAKPOINTS_REGS
  194. bool
  195. depends on HAVE_HW_BREAKPOINT
  196. help
  197. Depending on the arch implementation of hardware breakpoints,
  198. some of them have separate registers for data and instruction
  199. breakpoints addresses, others have mixed registers to store
  200. them but define the access type in a control register.
  201. Select this option if your arch implements breakpoints under the
  202. latter fashion.
  203. config HAVE_USER_RETURN_NOTIFIER
  204. bool
  205. config HAVE_PERF_EVENTS_NMI
  206. bool
  207. help
  208. System hardware can generate an NMI using the perf event
  209. subsystem. Also has support for calculating CPU cycle events
  210. to determine how many clock cycles in a given period.
  211. config HAVE_PERF_REGS
  212. bool
  213. help
  214. Support selective register dumps for perf events. This includes
  215. bit-mapping of each registers and a unique architecture id.
  216. config HAVE_PERF_USER_STACK_DUMP
  217. bool
  218. help
  219. Support user stack dumps for perf event samples. This needs
  220. access to the user stack pointer which is not unified across
  221. architectures.
  222. config HAVE_ARCH_JUMP_LABEL
  223. bool
  224. config HAVE_ARCH_MUTEX_CPU_RELAX
  225. bool
  226. config HAVE_RCU_TABLE_FREE
  227. bool
  228. config ARCH_HAVE_NMI_SAFE_CMPXCHG
  229. bool
  230. config HAVE_ALIGNED_STRUCT_PAGE
  231. bool
  232. help
  233. This makes sure that struct pages are double word aligned and that
  234. e.g. the SLUB allocator can perform double word atomic operations
  235. on a struct page for better performance. However selecting this
  236. might increase the size of a struct page by a word.
  237. config HAVE_CMPXCHG_LOCAL
  238. bool
  239. config HAVE_CMPXCHG_DOUBLE
  240. bool
  241. config ARCH_WANT_IPC_PARSE_VERSION
  242. bool
  243. config ARCH_WANT_COMPAT_IPC_PARSE_VERSION
  244. bool
  245. config ARCH_WANT_OLD_COMPAT_IPC
  246. select ARCH_WANT_COMPAT_IPC_PARSE_VERSION
  247. bool
  248. config HAVE_ARCH_SECCOMP_FILTER
  249. bool
  250. help
  251. An arch should select this symbol if it provides all of these things:
  252. - syscall_get_arch()
  253. - syscall_get_arguments()
  254. - syscall_rollback()
  255. - syscall_set_return_value()
  256. - SIGSYS siginfo_t support
  257. - secure_computing is called from a ptrace_event()-safe context
  258. - secure_computing return value is checked and a return value of -1
  259. results in the system call being skipped immediately.
  260. config SECCOMP_FILTER
  261. def_bool y
  262. depends on HAVE_ARCH_SECCOMP_FILTER && SECCOMP && NET
  263. help
  264. Enable tasks to build secure computing environments defined
  265. in terms of Berkeley Packet Filter programs which implement
  266. task-defined system call filtering polices.
  267. See Documentation/prctl/seccomp_filter.txt for details.
  268. config HAVE_CONTEXT_TRACKING
  269. bool
  270. help
  271. Provide kernel/user boundaries probes necessary for subsystems
  272. that need it, such as userspace RCU extended quiescent state.
  273. Syscalls need to be wrapped inside user_exit()-user_enter() through
  274. the slow path using TIF_NOHZ flag. Exceptions handlers must be
  275. wrapped as well. Irqs are already protected inside
  276. rcu_irq_enter/rcu_irq_exit() but preemption or signal handling on
  277. irq exit still need to be protected.
  278. config HAVE_VIRT_CPU_ACCOUNTING
  279. bool
  280. config HAVE_IRQ_TIME_ACCOUNTING
  281. bool
  282. help
  283. Archs need to ensure they use a high enough resolution clock to
  284. support irq time accounting and then call enable_sched_clock_irqtime().
  285. config HAVE_ARCH_TRANSPARENT_HUGEPAGE
  286. bool
  287. config HAVE_MOD_ARCH_SPECIFIC
  288. bool
  289. help
  290. The arch uses struct mod_arch_specific to store data. Many arches
  291. just need a simple module loader without arch specific data - those
  292. should not enable this.
  293. config MODULES_USE_ELF_RELA
  294. bool
  295. help
  296. Modules only use ELF RELA relocations. Modules with ELF REL
  297. relocations will give an error.
  298. config MODULES_USE_ELF_REL
  299. bool
  300. help
  301. Modules only use ELF REL relocations. Modules with ELF RELA
  302. relocations will give an error.
  303. config GENERIC_SIGALTSTACK
  304. bool
  305. #
  306. # ABI hall of shame
  307. #
  308. config CLONE_BACKWARDS
  309. bool
  310. help
  311. Architecture has tls passed as the 4th argument of clone(2),
  312. not the 5th one.
  313. config CLONE_BACKWARDS2
  314. bool
  315. help
  316. Architecture has the first two arguments of clone(2) swapped.
  317. source "kernel/gcov/Kconfig"