All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Gnad <dennis.gnad@kit.edu>
To: linux-perf-users@vger.kernel.org
Subject: Understanding timestamps in perf.data
Date: Wed, 2 Sep 2015 11:28:00 +0200	[thread overview]
Message-ID: <55E6C120.3030504@kit.edu> (raw)

Hi,

I am interested in timestamped performance counter data (with a 
specified sampling rate) as there is supposed to be saved in perf.data 
when I use "perf record -T".

However, I don't understand the complete output of "perf report -D", and 
can't figure out which parts of it are the timestamps. Is there any 
documentation that I overlooked?

Actually if it helps, I am only interested in the name/raw event, value, 
and timestamp, without any code/library information. Maybe the 
information on which CPU it is from (on a multicore) could be 
interesting as well.

Do I need to start looking into the code? Any good place to start? I 
probably need to do this anyway, instead of parsing the really large 
perf report -D output.

Thanks for your help and best regards,
Dennis

             reply	other threads:[~2015-09-02  9:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02  9:28 Dennis Gnad [this message]
2015-09-02 13:43 ` Understanding timestamps in perf.data David Ahern
2015-09-02 15:18   ` Dennis Gnad
2015-09-02 16:44     ` David Ahern
2015-09-02 17:00       ` Vince Weaver
2015-09-02 17:00         ` David Ahern
2015-09-03  7:19         ` Dennis Gnad
2015-09-03 12:52           ` Vince Weaver
2015-09-03 14:46             ` Dennis Gnad
2015-09-03 15:17               ` Vince Weaver
2015-09-02 19:23       ` Andi Kleen
2015-09-02 19:25         ` David Ahern
2015-09-03  9:50         ` Dennis Gnad

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=55E6C120.3030504@kit.edu \
    --to=dennis.gnad@kit.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.