Kconfig 4.9 KB

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