blob: 574541c571eb507d5c7ad8cdece8c10a2a355bc9 [file] [log] [blame]
config BR2_PACKAGE_TRACE_CMD
bool "trace-cmd"
depends on BR2_TOOLCHAIN_HAS_THREADS
depends on BR2_USE_MMU # fork()
depends on !BR2_STATIC_LIBS # dlopen()
help
Command line reader for ftrace.
To use this profiling tool, you should enable ftrace in your
kernel configuration. This command collect traces on your
target. You can analyse these traces on the target or on
the host via the gui "kernel shark"
http://git.kernel.org/cgit/linux/kernel/git/rostedt/trace-cmd.git
comment "trace-cmd needs a toolchain w/ threads, dynamic library"
depends on BR2_USE_MMU
depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS