Kconfig 11 KB

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