blob: 9d454e494b244529625e2e1b8d36f2b07ac0bc1b [file] [log] [blame]
config BR2_PACKAGE_TRACE_CMD
bool "trace-cmd"
depends on BR2_LARGEFILE
depends on BR2_TOOLCHAIN_HAS_THREADS
depends on !BR2_avr32 # AVR32 does not have TLS support
depends on BR2_USE_MMU # fork()
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/ largefile, threads"
depends on !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADS