All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Namhyung Kim <namhyung@kernel.org>,
	Hemant Kumar <hkshaw@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, srikar@linux.vnet.ibm.com,
	peterz@infradead.org, oleg@redhat.com,
	hegdevasant@linux.vnet.ibm.com, mingo@redhat.com,
	anton@redhat.com, systemtap@sourceware.org,
	aravinda@linux.vnet.ibm.com, penberg@iki.fi
Subject: Re: Re: [RFC PATCH v1 0/2] perf: Support for SDT markers
Date: Wed, 26 Feb 2014 18:22:03 +0900	[thread overview]
Message-ID: <530DB23B.6050503@hitachi.com> (raw)
In-Reply-To: <87ha7muw14.fsf@sejong.aot.lge.com>

(2014/02/26 17:18), Namhyung Kim wrote:
> Hi Masami and Hemant,
> 
> On Tue, 25 Feb 2014 21:27:07 +0530, Hemant Kumar wrote:
>> On 02/25/2014 05:14 PM, Masami Hiramatsu wrote:
>>> (2014/02/24 18:14), Hemant Kumar wrote:
>>>> First, scan the binaries using :
>>>> # perf list sdt --scan
>>>>
>>>> Creating a cache of SDT markers...
>>>> perf sdt cache created!
>>>>   Use : "perf list sdt"
>>>>   to see the SDT markers
>>> Hmm, in that case, I think you'd better introduce perf-sdt for scanning.
>>> e.g.
>>>
>>>   # perf sdt --scan app
>>
>> Hmm, this seems a better idea :)
>>
>>>   then you can add app to sdt cache, without app,
>>>
>>>   # perf sdt --scan
>>>
>>>   will just scans all binaries on the PATH and the libraries which listed
>>> by `ldconfig --print-caceh`
> 
> What should be done with the new perf sdt command?  If it's only
> intended to list the markers, I'd just suggest to add "perf list sdt" as
> this patch did.
> 
> Plus I think it'd be better if event_glob pattern also looks for sdt
> markers so that user can find out a specific markers easily, e.g.:
> 
>   # perf list rtld:*
> 
> or
> 
>   # perf list %rtld:*

Ah, that's a good idea :)

>>>
>>> And perf-list shows only the SDTs in the cache.
>>
>> Well, what will be better? perf-list or perf-sdt or perf-list sdt??
>> If perf-list, then wouldn't it be a huge list!!
> 
> The output of perf list is already a huge list and we paginate it.  So I
> don't think it's gonna be a problem. :)

Agreed.

>>>> - Add support to probe these SDT markers and integrate with a previous patch
>>>>    (support to perf to probe SDT markers) posted in lkml.
>>>>    https://lkml.org/lkml/2013/10/23/10
>>> Yeah, but I think we'd better choose another way to integrate it.
>>> Since SDT is like markers(static events), setting each of them via perf-probe is
>>> not intuitive. :)  I'd like to use it as an event, e.g.
>>>
>>>   # perf top -e "%libgcc:unwind"
>>>
>>> And perf top internally calls perf-probe to add new uprobe event, and
>>> clean the new event at exit.
>>
>> Yeah! Right :) Makes sense.

Note that we will need an option to make it permanent (not clear the event on exit)
for people who want to use SDT event from ftrace. :)

>> Will implement the suggestions in the next version asap!
> 
> That would be great!

Thank you!


-- 
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com



      parent reply	other threads:[~2014-02-26  9:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24  9:14 [RFC PATCH v1 0/2] perf: Support for SDT markers Hemant Kumar
2014-02-24  9:15 ` [RFC PATCH v1 1/2] perf/sdt : Listing of SDT markers by perf Hemant Kumar
2014-02-25  6:56   ` Namhyung Kim
2014-02-25  9:03     ` Hemant Kumar
2014-02-26  7:58       ` Namhyung Kim
2014-02-24  9:16 ` [RFC PATCH v1 2/2] perf/sdt : Documentation Hemant Kumar
2014-02-25 11:44 ` [RFC PATCH v1 0/2] perf: Support for SDT markers Masami Hiramatsu
2014-02-25 15:57   ` Hemant Kumar
2014-02-26  8:18     ` Namhyung Kim
2014-02-26  9:03       ` Hemant Kumar
2014-02-26  9:42         ` Masami Hiramatsu
2014-02-26 16:11           ` Hemant Kumar
2014-02-26  9:22       ` Masami Hiramatsu [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=530DB23B.6050503@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=anton@redhat.com \
    --cc=aravinda@linux.vnet.ibm.com \
    --cc=hegdevasant@linux.vnet.ibm.com \
    --cc=hkshaw@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=oleg@redhat.com \
    --cc=penberg@iki.fi \
    --cc=peterz@infradead.org \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=systemtap@sourceware.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.