All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Namhyung Kim <namhyung.kim@lge.com>,
	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: Tue, 31 Jan 2012 10:40:09 +0900	[thread overview]
Message-ID: <4F274679.4010402@gmail.com> (raw)
In-Reply-To: <20120131013054.GB25293@infradead.org>

2012-01-31 10:30 AM, Arnaldo Carvalho de Melo wrote:
> 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
>

Yep, I'll take a look at it.

Thanks,
Namhyung


      reply	other threads:[~2012-01-31  1:40 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
2012-01-31  1:40     ` Namhyung Kim [this message]

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=4F274679.4010402@gmail.com \
    --to=namhyung@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --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 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.