Kconfig 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182
  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 KPROBES
  28. bool "Kprobes"
  29. depends on MODULES
  30. depends on HAVE_KPROBES
  31. select KALLSYMS
  32. help
  33. Kprobes allows you to trap at almost any kernel address and
  34. execute a callback function. register_kprobe() establishes
  35. a probepoint and specifies the callback. Kprobes is useful
  36. for kernel debugging, non-intrusive instrumentation and testing.
  37. If in doubt, say "N".
  38. config JUMP_LABEL
  39. bool "Optimize trace point call sites"
  40. depends on HAVE_ARCH_JUMP_LABEL
  41. help
  42. If it is detected that the compiler has support for "asm goto",
  43. the kernel will compile trace point locations with just a
  44. nop instruction. When trace points are enabled, the nop will
  45. be converted to a jump to the trace function. This technique
  46. lowers overhead and stress on the branch prediction of the
  47. processor.
  48. On i386, options added to the compiler flags may increase
  49. the size of the kernel slightly.
  50. config OPTPROBES
  51. def_bool y
  52. depends on KPROBES && HAVE_OPTPROBES
  53. depends on !PREEMPT
  54. config HAVE_EFFICIENT_UNALIGNED_ACCESS
  55. bool
  56. help
  57. Some architectures are unable to perform unaligned accesses
  58. without the use of get_unaligned/put_unaligned. Others are
  59. unable to perform such accesses efficiently (e.g. trap on
  60. unaligned access and require fixing it up in the exception
  61. handler.)
  62. This symbol should be selected by an architecture if it can
  63. perform unaligned accesses efficiently to allow different
  64. code paths to be selected for these cases. Some network
  65. drivers, for example, could opt to not fix up alignment
  66. problems with received packets if doing so would not help
  67. much.
  68. See Documentation/unaligned-memory-access.txt for more
  69. information on the topic of unaligned memory accesses.
  70. config HAVE_SYSCALL_WRAPPERS
  71. bool
  72. config KRETPROBES
  73. def_bool y
  74. depends on KPROBES && HAVE_KRETPROBES
  75. config USER_RETURN_NOTIFIER
  76. bool
  77. depends on HAVE_USER_RETURN_NOTIFIER
  78. help
  79. Provide a kernel-internal notification when a cpu is about to
  80. switch to user mode.
  81. config HAVE_IOREMAP_PROT
  82. bool
  83. config HAVE_KPROBES
  84. bool
  85. config HAVE_KRETPROBES
  86. bool
  87. config HAVE_OPTPROBES
  88. bool
  89. #
  90. # An arch should select this if it provides all these things:
  91. #
  92. # task_pt_regs() in asm/processor.h or asm/ptrace.h
  93. # arch_has_single_step() if there is hardware single-step support
  94. # arch_has_block_step() if there is hardware block-step support
  95. # asm/syscall.h supplying asm-generic/syscall.h interface
  96. # linux/regset.h user_regset interfaces
  97. # CORE_DUMP_USE_REGSET #define'd in linux/elf.h
  98. # TIF_SYSCALL_TRACE calls tracehook_report_syscall_{entry,exit}
  99. # TIF_NOTIFY_RESUME calls tracehook_notify_resume()
  100. # signal delivery calls tracehook_signal_handler()
  101. #
  102. config HAVE_ARCH_TRACEHOOK
  103. bool
  104. config HAVE_DMA_ATTRS
  105. bool
  106. config USE_GENERIC_SMP_HELPERS
  107. bool
  108. config HAVE_REGS_AND_STACK_ACCESS_API
  109. bool
  110. help
  111. This symbol should be selected by an architecure if it supports
  112. the API needed to access registers and stack entries from pt_regs,
  113. declared in asm/ptrace.h
  114. For example the kprobes-based event tracer needs this API.
  115. config HAVE_CLK
  116. bool
  117. help
  118. The <linux/clk.h> calls support software clock gating and
  119. thus are a key power management tool on many systems.
  120. config HAVE_DMA_API_DEBUG
  121. bool
  122. config HAVE_HW_BREAKPOINT
  123. bool
  124. depends on PERF_EVENTS
  125. config HAVE_MIXED_BREAKPOINTS_REGS
  126. bool
  127. depends on HAVE_HW_BREAKPOINT
  128. help
  129. Depending on the arch implementation of hardware breakpoints,
  130. some of them have separate registers for data and instruction
  131. breakpoints addresses, others have mixed registers to store
  132. them but define the access type in a control register.
  133. Select this option if your arch implements breakpoints under the
  134. latter fashion.
  135. config HAVE_USER_RETURN_NOTIFIER
  136. bool
  137. config HAVE_PERF_EVENTS_NMI
  138. bool
  139. help
  140. System hardware can generate an NMI using the perf event
  141. subsystem. Also has support for calculating CPU cycle events
  142. to determine how many clock cycles in a given period.
  143. config HAVE_ARCH_JUMP_LABEL
  144. bool
  145. config HAVE_ARCH_MUTEX_CPU_RELAX
  146. bool
  147. config HAVE_RCU_TABLE_FREE
  148. bool
  149. source "kernel/gcov/Kconfig"