From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
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: [RFE] perf probe: Support globbing/regex in -a
Date: Thu, 9 Apr 2015 07:36:38 -0300 [thread overview]
Message-ID: <20150409103638.GK5403@kernel.org> (raw)
In-Reply-To: <55260DD8.50409@hitachi.com>
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?
<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
next prev parent reply other threads:[~2015-04-09 10:36 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 [this message]
2015-04-11 0:25 ` Masami Hiramatsu
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=20150409103638.GK5403@kernel.org \
--to=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--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 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).