<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openembedded-core.git/meta/packages/trace-cmd, branch master</title>
<subtitle></subtitle>
<id>https://trygvis.io/git/2012/05/openembedded-core.git/atom?h=master</id>
<link rel='self' href='https://trygvis.io/git/2012/05/openembedded-core.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://trygvis.io/git/2012/05/openembedded-core.git/'/>
<updated>2010-08-27T14:29:45Z</updated>
<entry>
<title>Major layout change to the packages directory</title>
<updated>2010-08-27T14:29:45Z</updated>
<author>
<name>Richard Purdie</name>
<email>rpurdie@linux.intel.com</email>
</author>
<published>2010-08-27T14:14:24Z</published>
<link rel='alternate' type='text/html' href='https://trygvis.io/git/2012/05/openembedded-core.git/commit/?id=29d6678fd546377459ef75cf54abeef5b969b5cf'/>
<id>urn:sha1:29d6678fd546377459ef75cf54abeef5b969b5cf</id>
<content type='text'>
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 &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>ftrace: add trace-cmd for ftrace control and config</title>
<updated>2010-08-27T12:00:06Z</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2010-08-20T16:24:43Z</published>
<link rel='alternate' type='text/html' href='https://trygvis.io/git/2012/05/openembedded-core.git/commit/?id=e76f76a37d046957f46814d9a106f0f5b4f8af72'/>
<id>urn:sha1:e76f76a37d046957f46814d9a106f0f5b4f8af72</id>
<content type='text'>
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 &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
</feed>
