From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/4] perf-probe: Avoid setting probes on same address on same event
Date: Fri, 10 Jul 2020 16:48:47 +0530 [thread overview]
Message-ID: <20200710111847.GN874@linux.vnet.ibm.com> (raw)
In-Reply-To: <159428202173.56570.3555041287477206859.stgit@devnote2>
* Masami Hiramatsu <mhiramat@kernel.org> [2020-07-09 17:07:01]:
> There is a case that the several same-name symbols points
> same address. In that case, perf probe returns an error.
>
> E.g.
>
> With this patch;
>
> # perf probe -x /lib64/libc-2.30.so -a "memcpy arg1=%di"
> Failed to find the location of the '%di' variable at this address.
> Perhaps it has been optimized out.
> Use -V with the --range option to show '%di' location range.
> Added new events:
> probe_libc:memcpy (on memcpy in /usr/lib64/libc-2.30.so with arg1=%di)
> probe_libc:memcpy (on memcpy in /usr/lib64/libc-2.30.so with arg1=%di)
>
> You can now use it in all perf tools, such as:
>
> perf record -e probe_libc:memcpy -aR sleep 1
>
>
> Reported-by: Andi Kleen <andi@firstfloor.org>
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
One small nit:
> ---
> tools/perf/util/probe-event.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
> index df713a5d1e26..1e95a336862c 100644
> --- a/tools/perf/util/probe-event.c
> +++ b/tools/perf/util/probe-event.c
> @@ -2968,6 +2968,15 @@ static int find_probe_trace_events_from_map(struct perf_probe_event *pev,
> for (j = 0; j < num_matched_functions; j++) {
> sym = syms[j];
>
> + /* There can be duplicated symbols in the map */
> + for (i = 0; i < j; i++)
> + if (sym->start == syms[i]->start) {
> + pr_debug("find duplicated symbol %s @ %lx\n", sym->name, sym->start);
Would "Found" sound better than "find"?
> + break;
> + }
> + if (i != j)
> + continue;
> +
Reviewed-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> tev = (*tevs) + ret;
> tp = &tev->point;
> if (ret == num_matched_functions) {
>
--
Thanks and Regards
Srikar Dronamraju
next prev parent reply other threads:[~2020-07-10 11:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 8:06 [PATCH 0/4] perf-probe: Fix GNU IFUNC probe issue etc Masami Hiramatsu
2020-07-09 8:07 ` [PATCH 1/4] perf-probe: Avoid setting probes on same address on same event Masami Hiramatsu
2020-07-10 11:18 ` Srikar Dronamraju [this message]
2020-07-10 12:14 ` Masami Hiramatsu
2020-07-09 8:07 ` [PATCH 2/4] perf-probe: Fix wrong variable warning when the probe point is not found Masami Hiramatsu
2020-07-09 14:37 ` Andi Kleen
2020-07-10 11:16 ` Srikar Dronamraju
2020-07-09 8:07 ` [PATCH 3/4] perf-probe: Fix memory leakage " Masami Hiramatsu
2020-07-10 11:16 ` Srikar Dronamraju
2020-07-09 8:07 ` [PATCH 4/4] perf-probe: Warn if the target function is GNU Indirect function Masami Hiramatsu
2020-07-09 14:36 ` Andi Kleen
2020-07-10 3:30 ` Masami Hiramatsu
2020-07-10 11:55 ` Arnaldo Carvalho de Melo
2020-07-10 12:56 ` Masami Hiramatsu
2020-07-10 11:15 ` Srikar Dronamraju
2020-07-10 12:14 ` 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=20200710111847.GN874@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=oleg@redhat.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