From: Masami Hiramatsu <mhiramat@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
Sandipan Das <sandipan@linux.ibm.com>,
linux-perf-users@vger.kernel.org,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf probe: Fix to delete multiple probe event
Date: Wed, 8 Jan 2020 11:36:50 +0900 [thread overview]
Message-ID: <20200108113650.a625f11c3cfa510d41edbd63@kernel.org> (raw)
In-Reply-To: <20191204112952.7b7d61feb2b14173ae625378@kernel.org>
Hi Arnaldo,
Could you pick this fix?
Sandipan, could you also test this?
Thank you,
On Wed, 4 Dec 2019 11:29:52 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> On Tue, 3 Dec 2019 17:01:54 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> > Fix to delete multiple probe event with filter correctly.
> >
> > When we put an event with multiple probes, perf-probe fails
> > to delete with filters. This comes from a failure to list
> > up the event name because of overwrapping its name.
> >
> > To fix this issue, skip to list up the event which has
> > same name.
> >
> > Without this patch:
> > # perf probe -l \*
> > probe_perf:map__map_ip (on perf_sample__fprintf_brstackoff:21@
> > probe_perf:map__map_ip (on perf_sample__fprintf_brstackoff:25@
> > probe_perf:map__map_ip (on append_inlines:12@util/machine.c in
> > probe_perf:map__map_ip (on unwind_entry:19@util/machine.c in /
> > probe_perf:map__map_ip (on map__map_ip@util/map.h in /home/mhi
> > probe_perf:map__map_ip (on map__map_ip@util/map.h in /home/mhi
> > # perf probe -d \*
> > "*" does not hit any event.
> > Error: Failed to delete events. Reason: No such file or directory (Code: -2)
> >
> > With this:
> > # perf probe -d \*
> > Removed event: probe_perf:map__map_ip
> >
>
> Oops, I missed Fixed tag.
>
> Fixes: 72363540c009 ("perf probe: Support multiprobe event")
>
> Thanks,
>
> > Reported-by: Arnaldo Carvalho de Melo <acme@kernel.org>
> > Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> > ---
> > tools/perf/util/probe-file.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/tools/perf/util/probe-file.c b/tools/perf/util/probe-file.c
> > index 5003ba403345..c03a591d41a4 100644
> > --- a/tools/perf/util/probe-file.c
> > +++ b/tools/perf/util/probe-file.c
> > @@ -206,6 +206,9 @@ static struct strlist *__probe_file__get_namelist(int fd, bool include_group)
> > } else
> > ret = strlist__add(sl, tev.event);
> > clear_probe_trace_event(&tev);
> > + /* Skip if there is same name multi-probe event in the list */
> > + if (ret == -EEXIST)
> > + ret = 0;
> > if (ret < 0)
> > break;
> > }
> >
>
>
> --
> Masami Hiramatsu <mhiramat@kernel.org>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-01-08 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 8:01 [PATCH] perf probe: Fix to delete multiple probe event Masami Hiramatsu
2019-12-04 2:29 ` Masami Hiramatsu
2020-01-08 2:36 ` Masami Hiramatsu [this message]
2020-01-08 5:53 ` Sandipan Das
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=20200108113650.a625f11c3cfa510d41edbd63@kernel.org \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=ravi.bangoria@linux.ibm.com \
--cc=sandipan@linux.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.