aaef2cad85
Certain tracing related options are required to be able to build ktapvm.ko, enable those. Enable CONFIG_FUNTCTION_TRACER as otherwise, CONFIG_EVENT_TRACING won't stick. (Some tracer needs to be enabled for this). [Peter: add a note to ktap Config.in explaining this is done] Signed-off-by: Anders Darander <anders@chargestorm.se> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
29 lines
877 B
Plaintext
29 lines
877 B
Plaintext
config BR2_PACKAGE_KTAP
|
|
bool "ktap"
|
|
depends on BR2_LINUX_KERNEL
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS
|
|
help
|
|
ktap is a script-based dynamic tracing tool for Linux
|
|
|
|
It uses a scripting language and lets users trace the Linux kernel
|
|
dynamically. ktap is designed to give operational insights with
|
|
interoperability that allows users to tune, troubleshoot and extend
|
|
kernel and application. It's similar to Linux Systemtap and
|
|
Solaris Dtrace.
|
|
|
|
ktap doesn't support kernels older than 3.1.
|
|
|
|
Your kernel must have CONFIG_EVENT_TRACING,
|
|
CONFIG_PERF_EVENTS, and CONFIG_DEBUG_FS enabled to compile.
|
|
|
|
Buildroot automatically enables these in the kernel configuration.
|
|
|
|
http://www.ktap.org
|
|
|
|
comment "ktap needs a Linux kernel to be built"
|
|
depends on !BR2_LINUX_KERNEL
|
|
|
|
comment "ktap needs a toolchain w/ threads"
|
|
depends on !BR2_TOOLCHAIN_HAS_THREADS
|
|
|