From: Milian Wolff <mail@milianw.de>
To: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: Chronogram with pref ?
Date: Wed, 23 Jan 2013 14:17:03 +0100 [thread overview]
Message-ID: <1898984.QcIki0Uqq8@minime> (raw)
In-Reply-To: <1358934556.33108.YahooMailNeo@web171501.mail.ir2.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On Wednesday 23 January 2013 09:49:16 dark_footix wrote:
> Hello All,
>
>
> Is there some workshop about timestamping the enter / exit of all the
> functions ?
Perf is sampling based, so you won't get *all* enter/exit functions - see e.g.
http://en.wikipedia.org/wiki/Profiling_%28computer_programming%29#Statistical_profilers
> Is it possible to have the info of timestamp on the enter / exit of each
> function with the backtrace info, and the sub-functions called ? and the
> thread id .
Recording that should be possible with "perf record -g -s -T" I think.
> If I am interested to start a development of an graphic interface to visual
> the result, do you have some result of log which one I could parse ? which
> could be the formalism of the result ?
>
> What is the best way to develop this kind of feature ?
> Does it already exist ?
I think what we need is a proper public perf library to parse its generated
data. That would then allow one to integrate Perf into KCacheGrind or similar
which would give one a really nice GUI. Though a timeline GUI similar to what
VTune offers would be very interesting as well. Afaik it does not exist yet.
Cheers
--
Milian Wolff
mail@milianw.de
http://milianw.de
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-01-23 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1358934288.36342.YahooMailNeo@web171503.mail.ir2.yahoo.com>
2013-01-23 9:49 ` Chronogram with pref ? dark_footix
2013-01-23 13:17 ` Milian Wolff [this message]
2013-01-24 7:39 ` Namhyung Kim
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=1898984.QcIki0Uqq8@minime \
--to=mail@milianw.de \
--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