All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Servat <harald.servat@bsc.es>
To: David Ahern <dsahern@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Information regarding the perf tool
Date: Mon, 04 Nov 2013 18:26:57 +0100	[thread overview]
Message-ID: <5277D8E1.9000009@bsc.es> (raw)
In-Reply-To: <52729FE5.3090109@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2091 bytes --]

On 31/10/13 19:22, David Ahern wrote:
> On 10/31/13, 11:23 AM, Harald Servat wrote:
>> Which is the relation between perf_clock() (or local_clock()) and
>> clock_gettime (CLOCK_MONOTONIC, ). Are they the same? If not, is there a
>> way to correlate them? Or alternatively, is it possible to call
>> local_clock() from the userland?
>
> We still do not have a means of correlating perf_clock to time-of-day,
> monotonic or any other clock source. Still trying.
>
> Pawell Moll has a couple of patches posted -- one uses an ioctl to get
> perf_clock timestamps the other makes perf_clock accessible through
> clock_gettime. See attached.
>
> David

Hello,

   thank you David! Those patches are great! I decided to access perf 
clock through clock_gettime because I'm more used to this call since I 
used it before.

   I understand that the patches are a bit hardcoded, right? I tried to 
#include "/usr/include/linux/time.h" after #include <time.h> but they 
seem to conflict. If I just extract the interesting bits (#define 
CLOCK_PERF) it seems to work. Is there a cleaner way to use this right now?

   JFTR, I have written a very small app that demonstrate the usage of 
this clock_gettime + perf (attached). It is very interesting to see that 
the difference between the monotonic and the perf clock is rather 
similar. However, as time goes by, at least in my machine, perf clock 
seems to advance at a faster pace than the monotonic clock.

Best regards.
-- 



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

[-- Attachment #2: perf-clock.tar.bz2 --]
[-- Type: application/x-bzip, Size: 842 bytes --]

  reply	other threads:[~2013-11-04 17:27 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
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 [this message]
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=5277D8E1.9000009@bsc.es \
    --to=harald.servat@bsc.es \
    --cc=dsahern@gmail.com \
    --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.