linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: "Kornievskaia, Olga" <Olga.Kornievskaia@netapp.com>,
	linux-perf-users@vger.kernel.org
Subject: Re: timing information with perf
Date: Mon, 16 Nov 2015 22:31:44 -0300	[thread overview]
Message-ID: <20151117013144.GB22729@kernel.org> (raw)
In-Reply-To: <20151117003020.GD25870@redhat.com>

Em Mon, Nov 16, 2015 at 07:30:20PM -0500, Frank Ch. Eigler escreveu:
> acme wrote:
 
> > [...]
> > > 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() 
> > >    } [...]
> > > '

> > Is that done syncronously?

> Meaning - calculated live as the tracepoints hit?  Yes, right during
> the respective callbacks.  No trace files nor postprocessing.

Right, 'perf trace' is in between those extremes, i.e. no synchronous
processing, no trace file for postprocessing. Just the ring buffer, that
is continuously processed.

- Arnaldo

  reply	other threads:[~2015-11-17  1:31 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
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 [this message]
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=20151117013144.GB22729@kernel.org \
    --to=acme@kernel.org \
    --cc=Olga.Kornievskaia@netapp.com \
    --cc=fche@redhat.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).