mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Namhyung Kim <namhyung.kim@lge.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH v2 2/2] perf: Add error message for EMFILE
Date: Mon, 30 Jan 2012 23:30:54 -0200	[thread overview]
Message-ID: <20120131013054.GB25293@infradead.org> (raw)
In-Reply-To: <1327972517-5055-2-git-send-email-namhyung.kim@lge.com>

Em Tue, Jan 31, 2012 at 10:15:16AM +0900, Namhyung Kim escreveu:
> When a user tries to open so many event on multiple tasks/cpus,
> perf_event_open syscall may fail with EMFILE. Provide an advice
> for that case.

I'll apply this one, but can you investigate a way to share this error
handling accross the tools?

A helper routine that doesn't call exit, but returns failure that will
then cause the tool to decide if it exits or what (TUI ones could
continue and the user could then select some other operation that would
work, etc).

It should standardize on ui__warning(), that already takes into account
if the UI is --stdio or --tui (in the future a GUI too), etc.

Thanks a lot!

- Arnaldo
 
> Signed-off-by: Namhyung Kim <namhyung.kim@lge.com>
> Cc: David Ahern <dsahern@gmail.com>
> ---
>  tools/perf/builtin-record.c |    5 +++++
>  tools/perf/builtin-stat.c   |    4 ++++
>  tools/perf/builtin-top.c    |    3 ++-
>  3 files changed, 11 insertions(+), 1 deletions(-)
> 
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 32870eef952f..a334008a1853 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -249,6 +249,11 @@ try_again:
>  				ui__warning("The %s event is not supported.\n",
>  					    event_name(pos));
>  				exit(EXIT_FAILURE);
> +			} else if (err == EMFILE) {
> +				ui__warning("Too many events are opened.\n"
> +					    "Try again after reducing the number of events,\n"
> +					    "tasks and/or cpus.\n");
> +				exit(EXIT_FAILURE);
>  			}
>  
>  			printf("\n");
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index 459b8620a5d9..7c5421c7af06 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -477,6 +477,10 @@ static int run_perf_stat(int argc __used, const char **argv)
>  				      "\t Consider tweaking"
>  				      " /proc/sys/kernel/perf_event_paranoid or running as root.",
>  				      system_wide ? "system-wide " : "");
> +			} else if (errno == EMFILE) {
> +				error("Too many events are opened.\n"
> +				      "\t Try again after reducing the number of events,\n"
> +				      "\t tasks and/or cpus.");
>  			} else {
>  				error("open_counter returned with %d (%s). "
>  				      "/bin/dmesg may provide additional information.\n",
> diff --git a/tools/perf/builtin-top.c b/tools/perf/builtin-top.c
> index e8b033c074f9..987af3695218 100644
> --- a/tools/perf/builtin-top.c
> +++ b/tools/perf/builtin-top.c
> @@ -899,7 +899,8 @@ try_again:
>  				goto out_err;
>  			} else if (err == EMFILE) {
>  				ui__warning("Too many events are opened.\n"
> -					    "Try again after reducing the number of events\n");
> +					    "Try again after reducing the number of events,\n"
> +					    "tasks and/or cpus.\n");
>  				goto out_err;
>  			}
>  
> -- 
> 1.7.9.rc1.dirty

  reply	other threads:[~2012-01-31  1:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31  1:15 [PATCH v2 1/2] perf tools: Return first evsel for non-sample event on old kernel Namhyung Kim
2012-01-31  1:15 ` [PATCH v2 2/2] perf: Add error message for EMFILE Namhyung Kim
2012-01-31  1:30   ` Arnaldo Carvalho de Melo [this message]
2012-01-31  1:40     ` Namhyung Kim

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=20120131013054.GB25293@infradead.org \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung.kim@lge.com \
    --cc=paulus@samba.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

all inboxes | Powered by JetHome®