From: Masami Hiramatsu <mhiramat@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH perf/core v2 0/4] perf-probe: Fix and improve module probe events
Date: Mon, 16 Jan 2017 17:08:44 +0900 [thread overview]
Message-ID: <20170116170844.1c882f52be7c26bb0f029dc3@kernel.org> (raw)
In-Reply-To: <148411429514.9978.10060675441541429175.stgit@devbox>
Ping?
Arnaldo, could you merge it if it is acceptable?
Thank you,
On Wed, 11 Jan 2017 14:58:25 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Hello,
>
> This is the 2nd version of the series for fixing offline/online
> module probe support and improving perf-probe to probe module
> without -m option (Thanks Arnaldo!).
> This includes below patches.
>
> - [1/4] Fix perf-probe --list to show correct probe location
> in module.
> - [2/4] Improve error checking for the probes for offline
> kernel.
> - [3/4] Fix perf-probe to probe correctly on gcc generated
> functions in module.
> - [4/4] Improve perf-probe to find probe events in module
> without -m option.
>
> In this version, I updated the patch description of 1/4
> and fix a bug in 4/4.
>
> Thank you,
>
> ---
>
> Masami Hiramatsu (4):
> perf-probe: Fix to show correct locations for events on modules
> perf-probe: Add error checks to offline probe post-processing
> perf-probe: Fix to probe on gcc generated functions in modules
> perf-probe: Find probe events without target module
>
>
> tools/perf/util/probe-event.c | 160 ++++++++++++++++++++++++++++------------
> tools/perf/util/probe-finder.c | 15 ++--
> tools/perf/util/probe-finder.h | 3 +
> 3 files changed, 121 insertions(+), 57 deletions(-)
>
> --
> Masami Hiramatsu (Linaro)
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2017-01-16 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 5:58 [PATCH perf/core v2 0/4] perf-probe: Fix and improve module probe events Masami Hiramatsu
2017-01-11 5:59 ` [PATCH perf/core v2 1/4] perf-probe: Fix to show correct locations for events on modules Masami Hiramatsu
2017-01-16 18:32 ` Arnaldo Carvalho de Melo
2017-01-18 9:22 ` [tip:perf/urgent] perf probe: " tip-bot for Masami Hiramatsu
2017-01-11 6:00 ` [PATCH perf/core v2 2/4] perf-probe: Add error checks to offline probe post-processing Masami Hiramatsu
2017-01-18 9:22 ` [tip:perf/urgent] perf probe: " tip-bot for Masami Hiramatsu
2017-01-11 6:01 ` [PATCH perf/core v2 3/4] perf-probe: Fix to probe on gcc generated functions in modules Masami Hiramatsu
2017-01-18 9:23 ` [tip:perf/urgent] perf probe: " tip-bot for Masami Hiramatsu
2017-01-11 6:03 ` [PATCH perf/core v2 4/4] perf-probe: Find probe events without target module Masami Hiramatsu
2017-01-16 18:44 ` Arnaldo Carvalho de Melo
2017-01-16 22:21 ` Masami Hiramatsu
2017-01-16 8:08 ` Masami Hiramatsu [this message]
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=20170116170844.1c882f52be7c26bb0f029dc3@kernel.org \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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