From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Ahern <daahern@cisco.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, peterz@infradead.org, fweisbec@gmail.com,
paulus@samba.org, tglx@linutronix.de
Subject: Re: [PATCH] perf tools: Emit clearer message for sys_perf_event_open ENOENT return
Date: Fri, 25 Mar 2011 15:08:40 -0300 [thread overview]
Message-ID: <20110325180840.GE13180@ghostprotocols.net> (raw)
In-Reply-To: <1301076350-19593-1-git-send-email-daahern@cisco.com>
Em Fri, Mar 25, 2011 at 12:05:50PM -0600, David Ahern escreveu:
> Resend of patch sent back in January 2011 in light of recent confusion around
> unsupported events for a given platform.
>
> Improve sys_perf_event_open ENOENT return handling in top and record, just
> like 5a3446b does for stat.
>
> Retry of Arnaldo's patch using error instead of die which allows the fallback
> from hardware cycles to software clock.
Please use ui__warning(""...) as it will work in the TUI too.
> Signed-off-by: David Ahern <daahern@cisco.com>
> ---
> tools/perf/builtin-record.c | 6 ++++++
> tools/perf/builtin-top.c | 7 +++++++
> 2 files changed, 13 insertions(+), 0 deletions(-)
>
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 6febcc1..73fa8b7 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -282,6 +282,8 @@ try_again:
> else if (err == ENODEV && cpu_list) {
> die("No such device - did you specify"
> " an out-of-range profile CPU?\n");
> + } else if (err == ENOENT) {
> + error("%s event is not supported.", event_name(pos));
> } else if (err == EINVAL && sample_id_all_avail) {
> /*
> * Old kernel, no attr->sample_id_type_all field
> @@ -307,6 +309,10 @@ try_again:
> attr->config = PERF_COUNT_SW_CPU_CLOCK;
> goto try_again;
> }
> +
> + if (err == ENOENT)
> + exit(1);
> +
> printf("\n");
> error("sys_perf_event_open() syscall returned with %d (%s). /bin/dmesg may provide additional information.\n",
> err, strerror(err));
> diff --git a/tools/perf/builtin-top.c b/tools/perf/builtin-top.c
> index 80c9e06..ab27693 100644
> --- a/tools/perf/builtin-top.c
> +++ b/tools/perf/builtin-top.c
> @@ -852,6 +852,9 @@ try_again:
> die("Permission error - are you root?\n"
> "\t Consider tweaking"
> " /proc/sys/kernel/perf_event_paranoid.\n");
> + else if (err == ENOENT)
> + error("%s event is not supported.", event_name(counter));
> +
> /*
> * If it's cycles then fall back to hrtimer
> * based cpu-clock-tick sw counter, which
> @@ -867,6 +870,10 @@ try_again:
> attr->config = PERF_COUNT_SW_CPU_CLOCK;
> goto try_again;
> }
> +
> + if (err == ENOENT)
> + exit(1);
> +
> printf("\n");
> error("sys_perf_event_open() syscall returned with %d "
> "(%s). /bin/dmesg may provide additional information.\n",
> --
> 1.7.4
next prev parent reply other threads:[~2011-03-25 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 18:05 [PATCH] perf tools: Emit clearer message for sys_perf_event_open ENOENT return David Ahern
2011-03-25 18:08 ` Arnaldo Carvalho de Melo [this message]
2011-03-25 18:26 ` David Ahern
2011-03-25 18:37 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2011-03-25 19:11 David Ahern
2011-01-13 18:16 David Ahern
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=20110325180840.GE13180@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=daahern@cisco.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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