From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Re: [RFE] perf probe: Support globbing/regex in -a
Date: Sat, 11 Apr 2015 09:25:54 +0900 [thread overview]
Message-ID: <55286A12.6050309@hitachi.com> (raw)
In-Reply-To: <20150409103638.GK5403@kernel.org>
(2015/04/09 19:36), Arnaldo Carvalho de Melo wrote:
> Em Thu, Apr 09, 2015 at 02:27:52PM +0900, Masami Hiramatsu escreveu:
>> Hi Arnaldo,
>>
>> (2015/04/09 4:48), Arnaldo Carvalho de Melo wrote:
>>> Hi Masami,
>>>
>>> In tools/perf constructors are named <CLASS>__new, and right now I want
>>> to know hoe many of each <CLASS> objects are being allocated, so I expected to
>>> be able to do:
>>>
>>> [root@zoo ~]# perf probe -x ~/bin/perf -a "*__new"
>>> Probe point '*__new' not found.
>>> Error: Failed to add events.
>>> [root@zoo ~]#
>>
>> Actually, I had sent it :)
>>
>> https://lkml.org/lkml/2014/10/31/207
>> https://lkml.org/lkml/2014/10/31/213
>>
>> I'll update and resend the wildcard support.
>
> Oops, but it was together with that cache thing, could it be sent
> separately?
Yes, it can be applied separately. However, it may open the Pandora's box,
which we have to face to someday anyway :)
- "perf probe -a \*" can try to put probes on all functions in the kernel
including the inline functions. The total number of probes will be
more than one hundred-thousand (100,000)...
- Currently ftrace-kprobe doesn't limit the number of dynamic events, so
it can cause out of memory on some machine.
- Also, enabling such events at once, could cause performance problem,
which I had tackled last year. See below slide.
http://events.linuxfoundation.org/sites/events/files/slides/Handling%20the%20Massive%20Multiple%20Kprobes%20v2_1.pdf
(note that this series is not applied yet)
So, currently perf probe limits the maximum number of definable events at once
you can expand it with --max-probes anyway. And also, I've introduced --no-inlines
option to perf probe which reduces the number of matched functions when user
puts the probes with wild cards. (I'm considering to apply this option automatically
if the function name includes wild cards)
Thank you,
>
> <SNIP>
>
>>> Also that -l should output to stdout, so that we can grep it, also it would be nice if it -l worked
>>> like in perf list:
>>>
>>> [root@zoo ~]# perf probe -l probe_perf:*
>>> Semantic error :There is non-digit char in line number.
>>> Error: Command Parse Error.
>>
>> Hmm, right. This should be fixed.
>
> Thanks!
>
> - Arnaldo
>
--
Masami HIRAMATSU
Linux Technology Research Center, System Productivity Research Dept.
Center for Technology Innovation - Systems Engineering
Hitachi, Ltd., Research & Development Group
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2015-04-11 0:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 19:48 [RFE] perf probe: Support globbing/regex in -a Arnaldo Carvalho de Melo
2015-04-09 5:27 ` Masami Hiramatsu
2015-04-09 10:36 ` Arnaldo Carvalho de Melo
2015-04-11 0:25 ` Masami Hiramatsu [this message]
2015-04-11 12:22 ` Arnaldo Carvalho de Melo
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=55286A12.6050309@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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.