From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: ananth@in.ibm.com, Peter Zijlstra <peterz@infradead.org>,
hemant@linux.vnet.ibm.com,
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: [PATCH perf/core v2 0/4] perf-probe code cleanup and support wildcard for probe points
Date: Fri, 08 May 2015 10:03:26 +0900 [thread overview]
Message-ID: <20150508010326.24812.56013.stgit@localhost.localdomain> (raw)
Hi,
Here is a patches for wild card support. I've added two patches to
reduce API parameters by introducing probe_conf. This simplifies
--no-inlines option. (Thanks Arnaldo!)
Changes from v1:
- Update for the latest perf/core
- Use perf_probe_event.target instead of passing it as an independent
parameter [1/4]
- Introduce probe_conf for configuring parameters of probe-finder and
probe-event [2/4]
Thank you,
---
Masami Hiramatsu (4):
perf probe: Use perf_probe_event.target instead of passing as an argument
perf probe: Introduce probe_conf global configs
perf-probe: Add --no-inlines option to avoid searching inline functions
perf-probe: Support glob wildcards for function name
tools/perf/Documentation/perf-probe.txt | 4 +
tools/perf/builtin-probe.c | 24 +++----
tools/perf/util/dwarf-aux.c | 16 +++++
tools/perf/util/dwarf-aux.h | 3 +
tools/perf/util/probe-event.c | 105 +++++++++++++++----------------
tools/perf/util/probe-event.h | 15 +++-
tools/perf/util/probe-finder.c | 44 +++++++++----
tools/perf/util/probe-finder.h | 7 +-
tools/perf/util/util.h | 4 +
9 files changed, 128 insertions(+), 94 deletions(-)
--
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 reply other threads:[~2015-05-08 1:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 1:03 Masami Hiramatsu [this message]
2015-05-08 1:03 ` [PATCH perf/core v2 1/4] perf probe: Use perf_probe_event.target instead of passing as an argument Masami Hiramatsu
2015-05-10 7:11 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2015-05-08 1:03 ` [PATCH perf/core v2 2/4] perf probe: Introduce probe_conf global configs Masami Hiramatsu
2015-05-10 7:11 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2015-05-08 1:03 ` [PATCH perf/core v2 3/4] perf-probe: Add --no-inlines option to avoid searching inline functions Masami Hiramatsu
2015-05-10 7:11 ` [tip:perf/core] perf probe: " tip-bot for Masami Hiramatsu
2015-05-08 1:03 ` [PATCH perf/core v2 4/4] perf-probe: Support glob wildcards for function name Masami Hiramatsu
2015-05-10 7:12 ` [tip:perf/core] perf probe: " tip-bot for Masami Hiramatsu
2015-05-08 19:38 ` [PATCH perf/core v2 0/4] perf-probe code cleanup and support wildcard for probe points Arnaldo Carvalho de Melo
2015-05-10 3:02 ` 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=20150508010326.24812.56013.stgit@localhost.localdomain \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=acme@kernel.org \
--cc=ananth@in.ibm.com \
--cc=dsahern@gmail.com \
--cc=hemant@linux.vnet.ibm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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