2008-02-02 13:10:33 -07:00
|
|
|
#
|
|
|
|
# General architecture dependent options
|
|
|
|
#
|
2008-02-02 13:10:36 -07:00
|
|
|
|
|
|
|
config OPROFILE
|
2010-02-26 07:01:23 -07:00
|
|
|
tristate "OProfile system profiling"
|
2008-02-02 13:10:36 -07:00
|
|
|
depends on PROFILING
|
|
|
|
depends on HAVE_OPROFILE
|
2008-12-12 01:38:57 -07:00
|
|
|
select RING_BUFFER
|
2009-09-16 13:56:49 -06:00
|
|
|
select RING_BUFFER_ALLOW_SWAP
|
2008-02-02 13:10:36 -07:00
|
|
|
help
|
|
|
|
OProfile is a profiling system capable of profiling the
|
|
|
|
whole system, include the kernel, kernel modules, libraries,
|
|
|
|
and applications.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2009-07-08 05:49:38 -06:00
|
|
|
config OPROFILE_EVENT_MULTIPLEX
|
|
|
|
bool "OProfile multiplexing support (EXPERIMENTAL)"
|
|
|
|
default n
|
|
|
|
depends on OPROFILE && X86
|
|
|
|
help
|
|
|
|
The number of hardware counters is limited. The multiplexing
|
|
|
|
feature enables OProfile to gather more events than counters
|
|
|
|
are provided by the hardware. This is realized by switching
|
|
|
|
between events at an user specified time interval.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2008-02-02 13:10:36 -07:00
|
|
|
config HAVE_OPROFILE
|
2008-10-15 23:01:38 -06:00
|
|
|
bool
|
2008-02-02 13:10:36 -07:00
|
|
|
|
|
|
|
config KPROBES
|
|
|
|
bool "Kprobes"
|
2010-09-13 04:25:41 -06:00
|
|
|
depends on MODULES
|
2008-02-02 13:10:36 -07:00
|
|
|
depends on HAVE_KPROBES
|
2010-09-13 04:25:41 -06:00
|
|
|
select KALLSYMS
|
2008-02-02 13:10:36 -07:00
|
|
|
help
|
|
|
|
Kprobes allows you to trap at almost any kernel address and
|
|
|
|
execute a callback function. register_kprobe() establishes
|
|
|
|
a probepoint and specifies the callback. Kprobes is useful
|
|
|
|
for kernel debugging, non-intrusive instrumentation and testing.
|
|
|
|
If in doubt, say "N".
|
|
|
|
|
2010-10-29 10:33:43 -06:00
|
|
|
config JUMP_LABEL
|
|
|
|
bool "Optimize trace point call sites"
|
|
|
|
depends on HAVE_ARCH_JUMP_LABEL
|
|
|
|
help
|
|
|
|
If it is detected that the compiler has support for "asm goto",
|
|
|
|
the kernel will compile trace point locations with just a
|
|
|
|
nop instruction. When trace points are enabled, the nop will
|
|
|
|
be converted to a jump to the trace function. This technique
|
|
|
|
lowers overhead and stress on the branch prediction of the
|
|
|
|
processor.
|
|
|
|
|
|
|
|
On i386, options added to the compiler flags may increase
|
|
|
|
the size of the kernel slightly.
|
|
|
|
|
2010-02-25 06:34:07 -07:00
|
|
|
config OPTPROBES
|
2010-03-15 11:00:54 -06:00
|
|
|
def_bool y
|
|
|
|
depends on KPROBES && HAVE_OPTPROBES
|
2010-02-25 06:34:07 -07:00
|
|
|
depends on !PREEMPT
|
|
|
|
|
2008-07-25 02:45:33 -06:00
|
|
|
config HAVE_EFFICIENT_UNALIGNED_ACCESS
|
2008-10-15 23:01:38 -06:00
|
|
|
bool
|
2008-07-25 02:45:33 -06:00
|
|
|
help
|
|
|
|
Some architectures are unable to perform unaligned accesses
|
|
|
|
without the use of get_unaligned/put_unaligned. Others are
|
|
|
|
unable to perform such accesses efficiently (e.g. trap on
|
|
|
|
unaligned access and require fixing it up in the exception
|
|
|
|
handler.)
|
|
|
|
|
|
|
|
This symbol should be selected by an architecture if it can
|
|
|
|
perform unaligned accesses efficiently to allow different
|
|
|
|
code paths to be selected for these cases. Some network
|
|
|
|
drivers, for example, could opt to not fix up alignment
|
|
|
|
problems with received packets if doing so would not help
|
|
|
|
much.
|
|
|
|
|
|
|
|
See Documentation/unaligned-memory-access.txt for more
|
|
|
|
information on the topic of unaligned memory accesses.
|
|
|
|
|
2009-01-14 06:13:59 -07:00
|
|
|
config HAVE_SYSCALL_WRAPPERS
|
|
|
|
bool
|
|
|
|
|
2008-03-04 15:28:37 -07:00
|
|
|
config KRETPROBES
|
|
|
|
def_bool y
|
|
|
|
depends on KPROBES && HAVE_KRETPROBES
|
|
|
|
|
2009-09-19 00:40:22 -06:00
|
|
|
config USER_RETURN_NOTIFIER
|
|
|
|
bool
|
|
|
|
depends on HAVE_USER_RETURN_NOTIFIER
|
|
|
|
help
|
|
|
|
Provide a kernel-internal notification when a cpu is about to
|
|
|
|
switch to user mode.
|
|
|
|
|
2008-07-23 22:27:05 -06:00
|
|
|
config HAVE_IOREMAP_PROT
|
2008-10-15 23:01:38 -06:00
|
|
|
bool
|
2008-07-23 22:27:05 -06:00
|
|
|
|
2008-02-02 13:10:36 -07:00
|
|
|
config HAVE_KPROBES
|
2008-10-15 23:01:38 -06:00
|
|
|
bool
|
2008-03-04 15:28:37 -07:00
|
|
|
|
|
|
|
config HAVE_KRETPROBES
|
2008-10-15 23:01:38 -06:00
|
|
|
bool
|
2008-04-29 02:00:30 -06:00
|
|
|
|
2010-02-25 06:34:07 -07:00
|
|
|
config HAVE_OPTPROBES
|
|
|
|
bool
|
2008-07-25 20:45:57 -06:00
|
|
|
#
|
|
|
|
# An arch should select this if it provides all these things:
|
|
|
|
#
|
|
|
|
# task_pt_regs() in asm/processor.h or asm/ptrace.h
|
|
|
|
# arch_has_single_step() if there is hardware single-step support
|
|
|
|
# arch_has_block_step() if there is hardware block-step support
|
|
|
|
# asm/syscall.h supplying asm-generic/syscall.h interface
|
|
|
|
# linux/regset.h user_regset interfaces
|
|
|
|
# CORE_DUMP_USE_REGSET #define'd in linux/elf.h
|
|
|
|
# TIF_SYSCALL_TRACE calls tracehook_report_syscall_{entry,exit}
|
|
|
|
# TIF_NOTIFY_RESUME calls tracehook_notify_resume()
|
|
|
|
# signal delivery calls tracehook_signal_handler()
|
|
|
|
#
|
|
|
|
config HAVE_ARCH_TRACEHOOK
|
2008-10-15 23:01:38 -06:00
|
|
|
bool
|
2008-07-25 20:45:57 -06:00
|
|
|
|
2008-04-29 02:00:30 -06:00
|
|
|
config HAVE_DMA_ATTRS
|
2008-10-15 23:01:38 -06:00
|
|
|
bool
|
2008-06-26 03:21:34 -06:00
|
|
|
|
|
|
|
config USE_GENERIC_SMP_HELPERS
|
2008-10-15 23:01:38 -06:00
|
|
|
bool
|
2008-07-23 22:26:48 -06:00
|
|
|
|
2010-02-10 09:25:17 -07:00
|
|
|
config HAVE_REGS_AND_STACK_ACCESS_API
|
|
|
|
bool
|
2010-02-18 06:25:21 -07:00
|
|
|
help
|
|
|
|
This symbol should be selected by an architecure if it supports
|
|
|
|
the API needed to access registers and stack entries from pt_regs,
|
|
|
|
declared in asm/ptrace.h
|
|
|
|
For example the kprobes-based event tracer needs this API.
|
2010-02-10 09:25:17 -07:00
|
|
|
|
2008-07-23 22:26:48 -06:00
|
|
|
config HAVE_CLK
|
2008-10-15 23:01:38 -06:00
|
|
|
bool
|
2008-07-23 22:26:48 -06:00
|
|
|
help
|
|
|
|
The <linux/clk.h> calls support software clock gating and
|
|
|
|
thus are a key power management tool on many systems.
|
|
|
|
|
2009-01-09 04:14:24 -07:00
|
|
|
config HAVE_DMA_API_DEBUG
|
|
|
|
bool
|
2009-04-09 10:48:34 -06:00
|
|
|
|
|
|
|
config HAVE_DEFAULT_NO_SPIN_MUTEXES
|
|
|
|
bool
|
2009-06-01 12:13:33 -06:00
|
|
|
|
|
|
|
config HAVE_HW_BREAKPOINT
|
|
|
|
bool
|
2009-12-16 17:33:54 -07:00
|
|
|
depends on PERF_EVENTS
|
2009-06-01 12:13:33 -06:00
|
|
|
|
2010-04-11 10:55:56 -06:00
|
|
|
config HAVE_MIXED_BREAKPOINTS_REGS
|
|
|
|
bool
|
|
|
|
depends on HAVE_HW_BREAKPOINT
|
|
|
|
help
|
|
|
|
Depending on the arch implementation of hardware breakpoints,
|
|
|
|
some of them have separate registers for data and instruction
|
|
|
|
breakpoints addresses, others have mixed registers to store
|
|
|
|
them but define the access type in a control register.
|
|
|
|
Select this option if your arch implements breakpoints under the
|
|
|
|
latter fashion.
|
|
|
|
|
2009-09-19 00:40:22 -06:00
|
|
|
config HAVE_USER_RETURN_NOTIFIER
|
|
|
|
bool
|
2009-09-07 00:19:51 -06:00
|
|
|
|
2010-05-15 14:57:48 -06:00
|
|
|
config HAVE_PERF_EVENTS_NMI
|
|
|
|
bool
|
2010-05-15 15:15:20 -06:00
|
|
|
help
|
|
|
|
System hardware can generate an NMI using the perf event
|
|
|
|
subsystem. Also has support for calculating CPU cycle events
|
|
|
|
to determine how many clock cycles in a given period.
|
2010-05-15 14:57:48 -06:00
|
|
|
|
2010-09-17 09:09:00 -06:00
|
|
|
config HAVE_ARCH_JUMP_LABEL
|
|
|
|
bool
|
|
|
|
|
2009-06-17 17:28:08 -06:00
|
|
|
source "kernel/gcov/Kconfig"
|