summaryrefslogtreecommitdiffstats
path: root/meta/packages/trace-cmd/trace-cmd_git.bb
Commit message (Collapse)AuthorAgeFilesLines
* Major layout change to the packages directoryRichard Purdie2010-08-271-21/+0
| | | | | | | | | | | | | | | | | Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* ftrace: add trace-cmd for ftrace control and configBruce Ashfield2010-08-271-0/+21
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>