1*4882a593Smuzhiyunconfig BR2_PACKAGE_TRACE_CMD 2*4882a593Smuzhiyun bool "trace-cmd" 3*4882a593Smuzhiyun depends on BR2_TOOLCHAIN_HAS_THREADS 4*4882a593Smuzhiyun depends on BR2_USE_MMU # fork() 5*4882a593Smuzhiyun depends on !BR2_STATIC_LIBS # dlopen() 6*4882a593Smuzhiyun help 7*4882a593Smuzhiyun Command line reader for ftrace. 8*4882a593Smuzhiyun 9*4882a593Smuzhiyun To use this profiling tool, you should enable ftrace in your 10*4882a593Smuzhiyun kernel configuration. This command collect traces on your 11*4882a593Smuzhiyun target. You can analyse these traces on the target or on 12*4882a593Smuzhiyun the host via the gui "kernel shark" 13*4882a593Smuzhiyun 14*4882a593Smuzhiyun http://git.kernel.org/cgit/linux/kernel/git/rostedt/trace-cmd.git 15*4882a593Smuzhiyun 16*4882a593Smuzhiyuncomment "trace-cmd needs a toolchain w/ threads, dynamic library" 17*4882a593Smuzhiyun depends on BR2_USE_MMU 18*4882a593Smuzhiyun depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS 19