Kconfig 10 KB

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