Kconfig 5.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213
  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 trace point call sites"
  43. depends on HAVE_ARCH_JUMP_LABEL
  44. help
  45. If it is detected that the compiler has support for "asm goto",
  46. the kernel will compile trace point locations with just a
  47. nop instruction. When trace points are enabled, the nop will
  48. be converted to a jump to the trace function. This technique
  49. lowers overhead and stress on the branch prediction of the
  50. processor.
  51. On i386, options added to the compiler flags may increase
  52. the size of the kernel slightly.
  53. config OPTPROBES
  54. def_bool y
  55. depends on KPROBES && HAVE_OPTPROBES
  56. depends on !PREEMPT
  57. config UPROBES
  58. bool "User-space probes (EXPERIMENTAL)"
  59. depends on ARCH_SUPPORTS_UPROBES
  60. default n
  61. help
  62. Uprobes enables kernel subsystems to establish probepoints
  63. in user applications and execute handler functions when
  64. the probepoints are hit.
  65. If in doubt, say "N".
  66. config HAVE_EFFICIENT_UNALIGNED_ACCESS
  67. bool
  68. help
  69. Some architectures are unable to perform unaligned accesses
  70. without the use of get_unaligned/put_unaligned. Others are
  71. unable to perform such accesses efficiently (e.g. trap on
  72. unaligned access and require fixing it up in the exception
  73. handler.)
  74. This symbol should be selected by an architecture if it can
  75. perform unaligned accesses efficiently to allow different
  76. code paths to be selected for these cases. Some network
  77. drivers, for example, could opt to not fix up alignment
  78. problems with received packets if doing so would not help
  79. much.
  80. See Documentation/unaligned-memory-access.txt for more
  81. information on the topic of unaligned memory accesses.
  82. config HAVE_SYSCALL_WRAPPERS
  83. bool
  84. config KRETPROBES
  85. def_bool y
  86. depends on KPROBES && HAVE_KRETPROBES
  87. config USER_RETURN_NOTIFIER
  88. bool
  89. depends on HAVE_USER_RETURN_NOTIFIER
  90. help
  91. Provide a kernel-internal notification when a cpu is about to
  92. switch to user mode.
  93. config HAVE_IOREMAP_PROT
  94. bool
  95. config HAVE_KPROBES
  96. bool
  97. config HAVE_KRETPROBES
  98. bool
  99. config HAVE_OPTPROBES
  100. bool
  101. #
  102. # An arch should select this if it provides all these things:
  103. #
  104. # task_pt_regs() in asm/processor.h or asm/ptrace.h
  105. # arch_has_single_step() if there is hardware single-step support
  106. # arch_has_block_step() if there is hardware block-step support
  107. # asm/syscall.h supplying asm-generic/syscall.h interface
  108. # linux/regset.h user_regset interfaces
  109. # CORE_DUMP_USE_REGSET #define'd in linux/elf.h
  110. # TIF_SYSCALL_TRACE calls tracehook_report_syscall_{entry,exit}
  111. # TIF_NOTIFY_RESUME calls tracehook_notify_resume()
  112. # signal delivery calls tracehook_signal_handler()
  113. #
  114. config HAVE_ARCH_TRACEHOOK
  115. bool
  116. config HAVE_DMA_ATTRS
  117. bool
  118. config USE_GENERIC_SMP_HELPERS
  119. bool
  120. config HAVE_REGS_AND_STACK_ACCESS_API
  121. bool
  122. help
  123. This symbol should be selected by an architecure if it supports
  124. the API needed to access registers and stack entries from pt_regs,
  125. declared in asm/ptrace.h
  126. For example the kprobes-based event tracer needs this API.
  127. config HAVE_CLK
  128. bool
  129. help
  130. The <linux/clk.h> calls support software clock gating and
  131. thus are a key power management tool on many systems.
  132. config HAVE_DMA_API_DEBUG
  133. bool
  134. config HAVE_HW_BREAKPOINT
  135. bool
  136. depends on PERF_EVENTS
  137. config HAVE_MIXED_BREAKPOINTS_REGS
  138. bool
  139. depends on HAVE_HW_BREAKPOINT
  140. help
  141. Depending on the arch implementation of hardware breakpoints,
  142. some of them have separate registers for data and instruction
  143. breakpoints addresses, others have mixed registers to store
  144. them but define the access type in a control register.
  145. Select this option if your arch implements breakpoints under the
  146. latter fashion.
  147. config HAVE_USER_RETURN_NOTIFIER
  148. bool
  149. config HAVE_PERF_EVENTS_NMI
  150. bool
  151. help
  152. System hardware can generate an NMI using the perf event
  153. subsystem. Also has support for calculating CPU cycle events
  154. to determine how many clock cycles in a given period.
  155. config HAVE_ARCH_JUMP_LABEL
  156. bool
  157. config HAVE_ARCH_MUTEX_CPU_RELAX
  158. bool
  159. config HAVE_RCU_TABLE_FREE
  160. bool
  161. config ARCH_HAVE_NMI_SAFE_CMPXCHG
  162. bool
  163. config HAVE_ALIGNED_STRUCT_PAGE
  164. bool
  165. help
  166. This makes sure that struct pages are double word aligned and that
  167. e.g. the SLUB allocator can perform double word atomic operations
  168. on a struct page for better performance. However selecting this
  169. might increase the size of a struct page by a word.
  170. config HAVE_CMPXCHG_LOCAL
  171. bool
  172. config HAVE_CMPXCHG_DOUBLE
  173. bool
  174. source "kernel/gcov/Kconfig"