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 17:57:35 +0100 [thread overview]
Message-ID: <52728BFF.30100@bsc.es> (raw)
In-Reply-To: <20131031164801.GY29695@two.firstfloor.org>
On 31/10/13 17:48, Andi Kleen wrote:
>> 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.
>
> perf always uses threshold 1 for the PEBS buffer.
>
> But yes there is some delay until the handler executes, and the
> time stamp is only computed in the handler.
>
David, Andi,
thank you for your valuable comments, they're really helpful.
David, wrt to the clock, which actually calls local_clock() I'm a bit
worried about the comment in sched/clock.c
* Similar to cpu_clock() for the current cpu. Time will only be observed
* to be monotonic if care is taken to only compare timestampt taken on the
* same CPU.
I'll rerun my experiments making sure that I pin the processes to a
single CPU.
Again, thank you!
--
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
prev parent reply other threads:[~2013-10-31 16:57 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
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 [this message]
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=52728BFF.30100@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 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).