From: Masami Hiramatsu <mhiramat@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
bhargavb <bhargavaramudu@gmail.com>,
linux-kernel@vger.kernel.org, Paul Clarke <pc@us.ibm.com>,
linux-rt-users@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH 0/5] perf-probe: Improve probing on versioned symbols
Date: Wed, 6 Dec 2017 12:06:20 +0900 [thread overview]
Message-ID: <151252958056.12861.954203514347167563.stgit@devbox> (raw)
Hi,
Here is the series for probing on versioned symbols
in libraries. This includes 5 patches to fix the
issues discussed on perf-users ML
(https://www.spinics.net/lists/linux-perf-users/msg04637.html)
[1/5] Warn if the event name is invalid. This notices
user that there is internal error which caused by
unexpected input.
[2/5] Cut off the version suffix when making event name
from symbol name. This fixes a issue when a wildcard
hits versioned symbol.
[3/5] Add "__return" suffix to the event name
automatically for the return probe, so that user
can easily identify which event is on function
return.
[4/5] Find versioned symbol from map without wildcard.
This allows user to specify a symbol without version
suffix nor wildcard. Anyway, at this point we have
no way to specify version suffix, because parser
recognizes "@" is a separator of "function@file"
syntax. This is fixed in next patch.
[5/5] Allow user to use backslash-escaped characters
on command line. This has 2 effects, user can specify
version suffix directly, and we can use special
characters in source file.
Thanks,
---
Masami Hiramatsu (5):
perf-probe: Add warning message if there is unexpected event name
perf-probe: Cut off the version suffix from event name
perf-probe: Add __return suffix for return events
perf-probe: Find versioned symbols from map
perf-probe: Support escaped character in parser
tools/perf/arch/powerpc/util/sym-handling.c | 8 +++
tools/perf/util/probe-event.c | 81 +++++++++++++++++++--------
tools/perf/util/string.c | 46 +++++++++++++++
tools/perf/util/string2.h | 2 +
tools/perf/util/symbol.c | 5 ++
tools/perf/util/symbol.h | 1
6 files changed, 120 insertions(+), 23 deletions(-)
--
Masami Hiramatsu (Linaro Ltd.) <mhiramat@kernel.org>
next reply other threads:[~2017-12-06 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 3:06 Masami Hiramatsu [this message]
2017-12-06 3:06 ` [PATCH 1/5] perf-probe: Add warning message if there is unexpected event name Masami Hiramatsu
2017-12-06 3:07 ` [PATCH 2/5] perf-probe: Cut off the version suffix from " Masami Hiramatsu
2017-12-06 3:07 ` [PATCH 3/5] perf-probe: Add __return suffix for return events Masami Hiramatsu
2017-12-06 3:08 ` [PATCH 4/5] perf-probe: Find versioned symbols from map Masami Hiramatsu
2017-12-06 3:08 ` [PATCH 5/5] perf-probe: Support escaped character in parser Masami Hiramatsu
2017-12-07 4:43 ` [PATCH 0/5] perf-probe: Improve probing on versioned symbols Ravi Bangoria
2017-12-07 6:11 ` 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=151252958056.12861.954203514347167563.stgit@devbox \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=bhargavaramudu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pc@us.ibm.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).