All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	LKML <linux-kernel@vger.kernel.org>,
	perf group <linux-perf-users@vger.kernel.org>
Subject: Re: Announcing simple-pt -- a simple Processor Trace implementation for Linux
Date: Mon, 17 Aug 2015 20:21:04 +0200	[thread overview]
Message-ID: <20150817182104.GJ1747@two.firstfloor.org> (raw)
In-Reply-To: <CAFTL4hwfk4ezi=MVpvURmW=hKdXX6mJQYabwisHejd77CW3Sjg@mail.gmail.com>

> >         % sptdecode --sideband ptout.sideband --pt ptout.0 | less
> >         TIME      DELTA  INSNs   OPERATION
> >         frequency 32
> >         0        [+0]     [+   1] _dl_aux_init+436
> >                           [+   6] __libc_start_main+455 -> _dl_discover_osversion
> >         ...
> >                           [+  13] __libc_start_main+446 -> main
> >                           [+   9]     main+22 -> f1
> >                           [+   4]             f1+9 -> f2
> >                           [+   2]             f1+19 -> f2
> >                           [+   5]     main+22 -> f1
> >                           [+   4]             f1+9 -> f2
> >                           [+   2]             f1+19 -> f2
> >                           [+   5]     main+22 -> f1
> 
> Nice. So I guess +x is the address offset. How hard would it be to
> translate to file lines?

Yes it's the address offset. Translating to lines wouldn't be too hard,
just needs to be implemented with a dwarf reader.

BTW the PT trace has all branches, just not the calls, but it's more
difficult to display them all in a nice way.

-Andi

      reply	other threads:[~2015-08-17 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17  4:31 Announcing simple-pt -- a simple Processor Trace implementation for Linux Andi Kleen
2015-08-17 13:09 ` Frederic Weisbecker
2015-08-17 18:21   ` Andi Kleen [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=20150817182104.GJ1747@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.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.