All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Servat <harald.servat@bsc.es>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Information regarding the perf tool
Date: Thu, 31 Oct 2013 16:45:16 +0100	[thread overview]
Message-ID: <52727B0C.5040402@bsc.es> (raw)
In-Reply-To: <87y55krw6f.fsf@tassilo.jf.intel.com>

On 23/10/13 14:47, Andi Kleen wrote:
> Harald Servat <harald.servat@bsc.es> writes:
>
>> Dear list,
>>
>>     I'm wondering whether it be possible to extend the "perf mem"
>> (tool) to emit the TSC of the sampling event?
>
> perf report -D reports everything, including time stamps.
>
> -Andi
>

Hello,

   returning to this topic, I'd like to mention that the time-stamps 
associated with the data samples seems to be a bit delayed from the 
actual computation.

   I tried to look at how are timestamps set in the perf samples and I 
took a look at

   arch/x86/kernel/cpu/perf_event_intel_ds.c

   and also at Intel Architectures Software Developer Manual [1].

   The first thing I notice is that pebs_record_core structure seems to 
be the same as the record of PEBS as indicated in Figure 17-10 of [1] 
(page 105), while pebs_record_nhm seems to be the record as indicated in 
Table 18-12 of [1] (page 147), but  neither Table 18-12 nor Figure 17-10 
provide the time when the record was generated, so the timestamp in the 
perf sample is generated elsewhere.

   In fact, I expected that for each entry into the PEBS a handler would 
be executed, but Intel documentations points that to use PEBS the tool 
(here perf) needs to allocate space for multiple PEBS entries, so the 
when the handler is invoked there may be multiple entries in the buffer, 
which makes things a little more obscure.

   Can anyone point me where and how is the timestamp calculated for 
every sample reported by perf?

Thank you very much.

[1] http://download.intel.com/products/processor/manual/253669.pdf

-- 


WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.

http://www.bsc.es/disclaimer

  parent reply	other threads:[~2013-10-31 15:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22 16:19 Information regarding the perf tool Harald Servat
2013-10-23 12:47 ` Andi Kleen
2013-10-23 13:51   ` Harald Servat
2013-10-31 15:45   ` Harald Servat [this message]
2013-10-31 16:39     ` David Ahern
2013-10-31 17:23       ` Harald Servat
2013-10-31 18:22         ` David Ahern
2013-11-04 17:26           ` Harald Servat
2013-11-04 17:53             ` David Ahern
2013-11-04 18:02               ` Pawel Moll
2013-12-12  0:56             ` David Ahern
2013-12-12  8:47               ` Harald Servat
2014-01-09 12:11                 ` Harald Servat
2013-10-31 16:48     ` Andi Kleen
2013-10-31 16:57       ` Harald Servat

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=52727B0C.5040402@bsc.es \
    --to=harald.servat@bsc.es \
    --cc=andi@firstfloor.org \
    --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.