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: Fri, 28 Jan 2011 14:41:37 -0700 [thread overview]
Message-ID: <4D433811.7020904@cisco.com> (raw)
In-Reply-To: <AANLkTinik0+Zp7N54bkh5fBzF1hb2XoubRbuMXwBeYGZ@mail.gmail.com>
On 01/28/11 14:18, Arun Sharma wrote:
> On Tue, Jan 25, 2011 at 6:29 PM, David Ahern <daahern@cisco.com> wrote:
>> 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 output could be a bit more compact (eg: print some info once per
> stack trace rather than once per frame). Also, it doesn't seem to
> print the DSO name when symbol lookup fails?
I am certainly interested in ideas on how to improve the output.
That version was derived from a local patch; in our case I wanted a
simple format for the output. Essentially, the timehist output is a
'text' version of the samples, with timestamps and address conversions
where possible.
Arnaldo has started a new version of it wherein the wall clock is a new
event that can be sampled (e.g., perf top) or generated at given rate. I
spent time looking at the changes to perf command, but have been
sidetracked with other priorities.
David
>
> Otherwise looks great. I'll drop the other patch.
>
> -Arun
next prev parent reply other threads:[~2011-01-28 21:41 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
2011-01-28 21:18 ` Arun Sharma
2011-01-28 21:41 ` David Ahern [this message]
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=4D433811.7020904@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).