From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
namhyung@kernel.org, Jiri Olsa <jolsa@redhat.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH perf/core ] perf-probe: Fix to track down unnamed union/structure members
Date: Wed, 1 Apr 2015 11:41:11 -0300 [thread overview]
Message-ID: <20150401144111.GA4549@kernel.org> (raw)
In-Reply-To: <551BB581.6000002@hitachi.com>
Em Wed, Apr 01, 2015 at 06:08:17PM +0900, Masami Hiramatsu escreveu:
> Ping?
<SNIP>
> > With this patch, perf probe can access unnamed fields.
> > -----
> > #./perf probe -nfx ./perf lock__delete ops 'locked_ops=ops->locked.ops'
> > Added new event:
> > probe_perf:lock__delete (on lock__delete in /home/mhiramat/ksrc/linux-3/tools/perf/perf with ops locked_ops=ops->locked.ops)
> > You can now use it in all perf tools, such as:
> > perf record -e probe_perf:lock__delete -aR sleep 1
> > -----
> > The original report of this issue is: https://lkml.org/lkml/2015/3/5/431
what am I doing wrong?
[root@ssdandy ~]# perf probe ~acme/bin/perf lock__delete 'locked_ops=ops'
Added new event:
probe_perf:lock__delete (on lock__delete in /home/acme/bin/perf with locked_ops=ops)
You can now use it in all perf tools, such as:
perf record -e probe_perf:lock__delete -aR sleep 1
[root@ssdandy ~]# perf probe -d probe_perf:*
Removed event: probe_perf:lock__delete
[root@ssdandy ~]# perf probe ~acme/bin/perf lock__delete 'locked_ops=ops->locked'
Semantic error: locked must be referred by '.'
Error: Failed to add events.
[root@ssdandy ~]# perf probe ~acme/bin/perf lock__delete 'locked_ops=ops.locked'
Semantic error: locked must be referred by '->'
Error: Failed to add events.
[root@ssdandy ~]# perf probe ~acme/bin/perf lock__delete 'locked_ops=ops->locked'
Semantic error: locked must be referred by '.'
Error: Failed to add events.
[root@ssdandy ~]# perf probe ~acme/bin/perf lock__delete 'locked_ops=ops->locked.ops'
Semantic error: locked must be referred by '.'
Error: Failed to add events.
[root@ssdandy ~]#
next prev parent reply other threads:[~2015-04-01 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 15:32 perf probe: can't find unnamed union members Arnaldo Carvalho de Melo
2015-03-06 12:02 ` Masami Hiramatsu
2015-03-09 2:15 ` [PATCH perf/core ] perf-probe: Fix to track down unnamed union/structure members Masami Hiramatsu
2015-04-01 9:08 ` Masami Hiramatsu
2015-04-01 14:41 ` Arnaldo Carvalho de Melo [this message]
2015-04-02 3:49 ` Masami Hiramatsu
2015-04-02 7:33 ` [PATCH perf/core v2] " Masami Hiramatsu
2015-04-02 14:57 ` Arnaldo Carvalho de Melo
2015-04-03 5:07 ` [tip:perf/core] perf probe: Fix to track down unnamed union/ structure members tip-bot for Masami Hiramatsu
2015-04-02 7:31 ` [PATCH perf/core ] perf-probe: Fix to track down unnamed union/structure members Masami Hiramatsu
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=20150401144111.GA4549@kernel.org \
--to=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).