Kconfig 11 KB

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