summaryrefslogtreecommitdiff
path: root/meta/packages/gtk-engines
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2010-08-20 12:24:43 -0400
committerRichard Purdie <rpurdie@linux.intel.com>2010-08-27 13:00:06 +0100
commite76f76a37d046957f46814d9a106f0f5b4f8af72 (patch)
treecadd962b3cdc9e64cde697a8efa9f032371217f0 /meta/packages/gtk-engines
parent70cd1ff43ff1109847cce2f2fe891fb9bdfdb3b2 (diff)
downloadopenembedded-core-e76f76a37d046957f46814d9a106f0f5b4f8af72.tar.gz
openembedded-core-e76f76a37d046957f46814d9a106f0f5b4f8af72.tar.bz2
openembedded-core-e76f76a37d046957f46814d9a106f0f5b4f8af72.tar.xz
openembedded-core-e76f76a37d046957f46814d9a106f0f5b4f8af72.zip
ftrace: add trace-cmd for ftrace control and config
Rather than manually configuring ftrace, trace-cmd was created to provide a more user friendly interface to the tracer. Some examples are: # ./trace-cmd record -e all ls /bin Then to see the information: # ./trace-cmd report To see just a subsystem: # ./trace-cmd record -e irq ls /bin To list the available trace events: # ./trace-cmd list -e You can also trace a single trace point with one of two methods: # ./trace-cmd record -e sched:sched_wakeup ls /bin Or simply: # ./trace-cmd record -e sched_wakeup ls /bin This tool also works with tracers (plugins) as well as events # ./trace-cmd list -p Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'meta/packages/gtk-engines')
0 files changed, 0 insertions, 0 deletions