From: Masami Hiramatsu <mhiramat@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Wang Nan <wangnan0@huawei.com>,
guohanjun@huawei.com
Subject: Re: [PATCH] perf probe: Return errno when does not hit any event
Date: Thu, 16 Mar 2017 18:39:03 +0900 [thread overview]
Message-ID: <20170316183903.559f13536a3e94198ad972be@kernel.org> (raw)
In-Reply-To: <20170314133056.GE3089@kernel.org>
On Tue, 14 Mar 2017 10:30:56 -0300
Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> Em Tue, Mar 14, 2017 at 09:19:47PM +0800, Kefeng Wang escreveu:
> > Hi all, any comments, thanks.
>
> For 'perf probe' make sure Masami is in the CC list, adding him, Masami?
Thanks Arnaldo,
Hi Kefeng, I've made the error ignored by design, since user might pass
the wildcard pattern to perf probe -d just for making sure.
You can check the pattern hits any event by using perf-probe --list PATTERN.
Would you have any use case to check the result?
Thank you,
>
> - Arnaldo
>
> > On 2017/3/7 15:33, Kefeng Wang wrote:
> > > + Arnaldo Carvalho de Melo <acme@kernel.org>
> > >
> > > On 2017/3/6 17:34, Kefeng Wang wrote:
> > >> On old perf, when using perf probe -d to delete an inexistent event,
> > >> it return errno, eg,
> > >>
> > >> -bash-4.3# perf probe -d xxx || echo $?
> > >> Info: Event "*:xxx" does not exist.
> > >> Error: Failed to delete events.
> > >> 255
> > >>
> > >> But now perf_del_probe_events() will always set ret = 0, different
> > >> from previous del_perf_probe_events(). After this, it return errno
> > >> again, eg,
> > >>
> > >> -bash-4.3# ./perf probe -d xxx || echo $?
> > >> Error: Failed to delete events.
> > >> 254
> > >>
> > >> And it is more appropriate to return -ENOENT instead of -EPERM.
> > >>
> > >> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> > >> ---
> > >> tools/perf/builtin-probe.c | 3 ++-
> > >> 1 file changed, 2 insertions(+), 1 deletion(-)
> > >>
> > >> diff --git a/tools/perf/builtin-probe.c b/tools/perf/builtin-probe.c
> > >> index 1fcebc3..c46b41c 100644
> > >> --- a/tools/perf/builtin-probe.c
> > >> +++ b/tools/perf/builtin-probe.c
> > >> @@ -444,7 +444,8 @@ static int perf_del_probe_events(struct strfilter *filter)
> > >> if (ret == -ENOENT && ret2 == -ENOENT)
> > >> pr_debug("\"%s\" does not hit any event.\n", str);
> > >> /* Note that this is silently ignored */
> > >> - ret = 0;
> > >> + else
> > >> + ret = 0;
> > >>
> > >> error:
> > >> if (kfd >= 0)
> > >>
> > >
> > >
> > > .
> > >
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2017-03-16 9:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 9:34 Kefeng Wang
2017-03-07 7:33 ` Kefeng Wang
2017-03-14 13:19 ` Kefeng Wang
2017-03-14 13:30 ` Arnaldo Carvalho de Melo
2017-03-16 9:39 ` Masami Hiramatsu [this message]
2017-03-16 12:07 ` Kefeng Wang
2017-03-17 1:57 ` Masami Hiramatsu
2017-03-17 8:16 ` [PATCH v2] " Kefeng Wang
2017-03-17 23:23 ` Masami Hiramatsu
2017-03-21 13:46 ` Arnaldo Carvalho de Melo
2017-03-24 18:43 ` [tip:perf/core] perf probe: Return errno when not hitting " tip-bot for Kefeng Wang
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=20170316183903.559f13536a3e94198ad972be@kernel.org \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=guohanjun@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wangkefeng.wang@huawei.com \
--cc=wangnan0@huawei.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
all inboxes | Powered by JetHome®