All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@gmail.com>
To: Christian Convey <christian.convey@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: newbie question: tracing userspace call/return sequences
Date: Sat, 7 Jan 2017 13:37:34 +0900	[thread overview]
Message-ID: <CAM9d7cjdNdeUKge_LbSwWyCdnrvzP2VxKGLy3tAw3q03D5Jf3w@mail.gmail.com> (raw)
In-Reply-To: <CAPfS4Zx6ZzWWUsSEbstsd2En6bqo=z94NTWe6xh_tJ9eZd17+A@mail.gmail.com>

Hello,

On Sat, Jan 7, 2017 at 4:07 AM, Christian Convey
<christian.convey@gmail.com> wrote:
>> Use the right tool for the job.
>>
>> On Intel, use a Broadwell or Skylake or Goldmont and use processor trace.
>>
>> perf record -e intel_pt//u foo
>> perf script --itrace=cr
>
> Hi Andi,
>
> Thanks for the idea.  It sounds promising.
>
> Unfortunately for my current situation, the CPU's on which I need to
> run this are too old to have intel_pt.

You can use uftrace for function tracing.  It doesn't have a hardware dependency
but you need to rebuild your program with instrumentation enabled (like -pg
or -finstrument-functions in gcc).

https://github.com/namhyung/uftrace

-- 
Thanks,
Namhyung Kim

  reply	other threads:[~2017-01-07  4:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06  3:49 newbie question: tracing userspace call/return sequences Christian Convey
2017-01-06 10:16 ` Milian Wolff
2017-01-06 20:05   ` Christian Convey
2017-01-07 23:44     ` Masami Hiramatsu
2017-01-09 15:19       ` Christian Convey
2017-01-09 17:03         ` Naveen N. Rao
2017-01-09 17:59           ` Christian Convey
2017-01-10  0:25             ` Masami Hiramatsu
2017-01-10  2:32               ` Christian Convey
2017-01-06 18:49 ` Andi Kleen
2017-01-06 19:07   ` Christian Convey
2017-01-07  4:37     ` Namhyung Kim [this message]
2017-01-07 18:26       ` Christian Convey
2017-01-07 19:08       ` Andi Kleen
2017-01-08  8:08         ` Namhyung Kim
2017-01-06 19:23   ` Arnaldo Carvalho de Melo
2017-01-09 17:20 ` Frank Ch. Eigler
2017-01-09 18:08   ` Christian Convey

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=CAM9d7cjdNdeUKge_LbSwWyCdnrvzP2VxKGLy3tAw3q03D5Jf3w@mail.gmail.com \
    --to=namhyung@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=christian.convey@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.