linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hemant Kumar <hemant@linux.vnet.ibm.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Milian Wolff <milian.wolff@kdab.com>,
	perf group <linux-perf-users@vger.kernel.org>
Subject: Re: user-defined static trace points
Date: Wed, 02 Mar 2016 12:21:42 +0530	[thread overview]
Message-ID: <56D68D7E.6080601@linux.vnet.ibm.com> (raw)
In-Reply-To: <871t7unh0j.fsf@tassilo.jf.intel.com>



On 03/02/2016 12:48 AM, Andi Kleen wrote:
> Milian Wolff <milian.wolff@kdab.com> writes:
>
>> Hey all,
>>
>> I'm aware that we can add custum user-defined dynamic trace points using `perf
>> probe`. But this is unwieldy for some larger applications, esp. if we
>> recompile them often. Is there a public API (that I could not find so far), to
>> define static trace points in userspace code?
>>
>> I found
>> http://www.brendangregg.com/blog/2015-07-03/hacking-linux-usdt-ftrace.html
>> which references https://www.sourceware.org/systemtap/wiki/
>> AddingUserSpaceProbingToApps for systemtap, but on my machine I don't have a
>> <sys/sdt.h> header.
> You need to install systemtap-devel or similar.
>
>> Would such trace points be useable by perf? https://
>> lwn.net/Articles/570818/ doesn't seem to be included, i.e. I don't have `perf
>> probe --markers` with a recent build of perf.
> There is a patch to teach perf about SDT probes, but so far it has not
> been integrated. You can use them from systemtap or gdb though.
>
> https://lwn.net/Articles/569622/
>
> Perhaps Hemant needs to resubmit?
>

So far, the patches for SDT support for perf have undergone several changes
and ultimately got picked up by Masami. Masami was working on the probe 
cache
feature along with the SDT support and sent a v3 :
https://lkml.org/lkml/2015/8/15/52
(" [RFC PATCH perf/core v3 00/17] perf-probe --cache and SDT support")

Although, I don't think the SDT related patches got picked up.

Masami, are you working on a v4 patchset?

-- 
Thanks,
Hemant Kumar

      reply	other threads:[~2016-03-02  6:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 15:53 user-defined static trace points Milian Wolff
2016-03-01 19:18 ` Andi Kleen
2016-03-02  6:51   ` Hemant Kumar [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=56D68D7E.6080601@linux.vnet.ibm.com \
    --to=hemant@linux.vnet.ibm.com \
    --cc=andi@firstfloor.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=milian.wolff@kdab.com \
    /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).