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>,
Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>,
linux-rt-users@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH v2 0/5] perf-probe: Improve probing on versioned symbols
Date: Thu, 7 Dec 2017 16:19:16 +0900 [thread overview]
Message-ID: <151263115609.13843.6362262297053841418.stgit@devbox> (raw)
Hi,
Here is the 2nd version of 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)
The first version is here; https://lkml.org/lkml/2017/12/5/1124
Here is the updates;
[3/5] Add a description in Documentation/perf-probe.txt
[5/5] Add a description and examples in Documentation/perf-probe.txt
Thank you,
---
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/Documentation/perf-probe.txt | 18 ++++++
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
7 files changed, 137 insertions(+), 24 deletions(-)
--
Masami Hiramatsu (Linaro Ltd.) <mhiramat@kernel.org>
next reply other threads:[~2017-12-07 7:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 7:19 Masami Hiramatsu [this message]
2017-12-07 7:19 ` [PATCH v2 1/5] perf-probe: Add warning message if there is unexpected event name Masami Hiramatsu
2017-12-07 15:53 ` Arnaldo Carvalho de Melo
2017-12-08 2:48 ` Masami Hiramatsu
2017-12-07 7:20 ` [PATCH v2 2/5] perf-probe: Cut off the version suffix from " Masami Hiramatsu
2017-12-07 16:34 ` Paul Clarke
2017-12-08 3:01 ` Masami Hiramatsu
2017-12-08 14:49 ` Paul Clarke
2017-12-08 16:12 ` Masami Hiramatsu
2017-12-11 18:25 ` Arnaldo Carvalho de Melo
2017-12-12 15:02 ` Masami Hiramatsu
2017-12-07 16:56 ` Arnaldo Carvalho de Melo
2017-12-07 17:24 ` Paul Clarke
2017-12-07 17:55 ` Arnaldo Carvalho de Melo
2017-12-08 3:15 ` Masami Hiramatsu
2017-12-07 7:20 ` [PATCH v2 3/5] perf-probe: Add __return suffix for return events Masami Hiramatsu
2017-12-07 7:21 ` [PATCH v2 4/5] perf-probe: Find versioned symbols from map Masami Hiramatsu
2017-12-08 11:08 ` Thomas-Mich Richter
2017-12-08 14:22 ` Masami Hiramatsu
2017-12-07 7:21 ` [PATCH v2 5/5] perf-probe: Support escaped character in parser Masami Hiramatsu
2017-12-08 11:45 ` Thomas-Mich Richter
2017-12-08 15:54 ` Masami Hiramatsu
2017-12-07 12:47 ` [PATCH v2 0/5] perf-probe: Improve probing on versioned symbols Ravi Bangoria
2017-12-08 16:24 ` Masami Hiramatsu
2017-12-08 17:13 ` Ravi Bangoria
2017-12-08 11:56 ` Thomas-Mich Richter
2017-12-08 16:12 ` 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=151263115609.13843.6362262297053841418.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 \
--cc=ravi.bangoria@linux.vnet.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 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.