Kconfig 13 KB

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