<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Stripping perf out from kernel source</title>
	<atom:link href="http://www.politreco.com/2010/03/stripping-perf-out-from-kernel-source/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.politreco.com/2010/03/stripping-perf-out-from-kernel-source/</link>
	<description>by Lucas De Marchi</description>
	<lastBuildDate>Sat, 07 Jan 2012 13:33:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Lucas De Marchi</title>
		<link>http://www.politreco.com/2010/03/stripping-perf-out-from-kernel-source/comment-page-1/#comment-9850</link>
		<dc:creator>Lucas De Marchi</dc:creator>
		<pubDate>Sun, 21 Mar 2010 19:47:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.politreco.com/?p=241#comment-9850</guid>
		<description>Yes, it&#039;s related to opensolaris/freebsd DTrace. There are a few dependencies, namely: elfutils, zlib, perl (perl dependency was introduced with latest version). To compile it you also need asciidoc and xmlto for documentation and libdwarf.

Valgrind is used mostly to find bugs in memory accesses like using an uninitialized var, freed memory, wrong pointer dereference etc. It does can be used to profile cache references, but it uses a simulation model to give you the miss/hit-rate. Perf, instead, relies on hardware counters and thus you can profile your application with the architecture it is running on.

It was first born as an access to hardware counters, but now it&#039;s becoming the &lt;em&gt;de facto&lt;/em&gt; performance debugging utility for linux kernel.</description>
		<content:encoded><![CDATA[<p>Yes, it&#8217;s related to opensolaris/freebsd DTrace. There are a few dependencies, namely: elfutils, zlib, perl (perl dependency was introduced with latest version). To compile it you also need asciidoc and xmlto for documentation and libdwarf.</p>
<p>Valgrind is used mostly to find bugs in memory accesses like using an uninitialized var, freed memory, wrong pointer dereference etc. It does can be used to profile cache references, but it uses a simulation model to give you the miss/hit-rate. Perf, instead, relies on hardware counters and thus you can profile your application with the architecture it is running on.</p>
<p>It was first born as an access to hardware counters, but now it&#8217;s becoming the <em>de facto</em> performance debugging utility for linux kernel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ricardo Guiraldelli</title>
		<link>http://www.politreco.com/2010/03/stripping-perf-out-from-kernel-source/comment-page-1/#comment-9802</link>
		<dc:creator>Ricardo Guiraldelli</dc:creator>
		<pubDate>Tue, 16 Mar 2010 01:17:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.politreco.com/?p=241#comment-9802</guid>
		<description>Is this something like OpenSolaris/FreeBSD DTrace? Does it need a lot of dependencies, doesn&#039;t it? Is this suitable for embedded apps?

How different is perf from Valgrind?</description>
		<content:encoded><![CDATA[<p>Is this something like OpenSolaris/FreeBSD DTrace? Does it need a lot of dependencies, doesn&#8217;t it? Is this suitable for embedded apps?</p>
<p>How different is perf from Valgrind?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

