From: David Ahern <daahern@cisco.com>
To: Arun Sharma <arun@sharma-home.net>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [RFC] --dump-sym-trace
Date: Tue, 25 Jan 2011 19:29:47 -0700 [thread overview]
Message-ID: <4D3F871B.3060906@cisco.com> (raw)
In-Reply-To: <AANLkTin3bp90ybuUDFQijspV0uBw=zTnczcPLBaZvO7p@mail.gmail.com>
On 01/25/11 18:47, Arun Sharma wrote:
> Some of my coworkers want to build tools to aggregate perf.data files
> from many different machines and provide web front ends and possibly
> other ways of visualizing the data (graphviz dot format comes to
> mind). One potential path is to use perf report -D (raw dump) and
> analyze that. But it made no sense to duplicate the functionality
> already in perf.
>
> Attached is a preliminary patch that dumps the trace, but also
> symbolizes the addresses. It's probably not terribly efficient - but I
> wanted to post it anyway to figure out if this is a good starting
> point or there are other ways of getting perf to report call graphs
> that are easy to parse in another program.
>
> -Arun
From a brief glance seems similar to the timehist patch I proposed. See:
http://www.mail-archive.com/linux-perf-users@vger.kernel.org/msg00049.html
http://www.mail-archive.com/linux-perf-users@vger.kernel.org/msg00047.html
http://www.mail-archive.com/linux-perf-users@vger.kernel.org/msg00048.html
The last URL shows an example of the output (abbreviated for email;
unwind the continuation lines for a better display).
That essentially dumps each sample point with the address-to-symbol
conversions done. The output of that is then fed to homegrown commands
to visualize/process the data.
David
next prev parent reply other threads:[~2011-01-26 2:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 1:47 [RFC] --dump-sym-trace Arun Sharma
2011-01-26 2:29 ` David Ahern [this message]
2011-01-28 21:18 ` Arun Sharma
2011-01-28 21:41 ` David Ahern
2011-01-29 20:50 ` Arnaldo Carvalho de Melo
2011-02-05 1:48 ` Arun Sharma
2011-02-05 2:38 ` David Ahern
2011-02-15 0:00 ` Arun Sharma
2011-02-15 0:03 ` David Ahern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D3F871B.3060906@cisco.com \
--to=daahern@cisco.com \
--cc=arun@sharma-home.net \
--cc=linux-perf-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).