From: fche@redhat.com (Frank Ch. Eigler)
To: "Kornievskaia, Olga" <Olga.Kornievskaia@netapp.com>
Cc: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: timing information with perf
Date: Mon, 16 Nov 2015 13:08:15 -0500 [thread overview]
Message-ID: <y0my4dxx1f4.fsf@fche.csb> (raw)
In-Reply-To: <94D0C06D-C3A7-4BD1-9898-124EE0AA923D@netapp.com> (Olga Kornievskaia's message of "Thu, 12 Nov 2015 21:07:20 +0000")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 677 bytes --]
Olga.Kornievskaia wrote:
> [...] say there are two tracepoints üfoobar_enterý and
> üfoobar_exitý. Each tracepoint logs a timestamp. Iùd like to be able
> to say that on average it takes that many time-units between üenterý
> and üexitý tracepoints. [...]
For completeness, a complete systemtap implementation of this could look like:
# stap -e '
global s, t%
probe kernel.trace("foobar_enter") {
t[tid()]=gettimeofday_us()
}
probe kernel.trace("foobar_exit") {
if (tid() in t) { s <<< gettimeofday_us() - t[tid()] }
}
probe timer.s(5),end {
printf("cumulative average us: %d\n", @avg(s))
}
'
- FChE
next prev parent reply other threads:[~2015-11-16 18:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 21:07 timing information with perf Kornievskaia, Olga
2015-11-12 21:57 ` Arnaldo Carvalho de Melo
2015-11-12 22:04 ` Arnaldo Carvalho de Melo
2015-11-12 23:19 ` David Ahern
2015-11-12 23:09 ` Kornievskaia, Olga
2015-11-12 23:22 ` David Ahern
2015-11-12 23:34 ` Arnaldo Carvalho de Melo
2015-11-13 17:01 ` Kornievskaia, Olga
2015-11-13 19:47 ` Arnaldo Carvalho de Melo
2015-11-13 21:57 ` Kornievskaia, Olga
2015-11-16 18:08 ` Frank Ch. Eigler [this message]
2015-11-17 0:12 ` Arnaldo Carvalho de Melo
2015-11-17 0:30 ` Frank Ch. Eigler
2015-11-17 1:31 ` Arnaldo Carvalho de Melo
2015-11-17 3:57 ` David Ahern
2015-11-17 13:31 ` Frank Ch. Eigler
2015-11-17 13:39 ` Arnaldo Carvalho de Melo
2015-11-17 14:04 ` Frank Ch. Eigler
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=y0my4dxx1f4.fsf@fche.csb \
--to=fche@redhat.com \
--cc=Olga.Kornievskaia@netapp.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 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).