linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH 1/3] perf report: Show error message when processing sample fails
Date: Fri, 27 Nov 2015 16:56:27 -0300	[thread overview]
Message-ID: <20151127195627.GI5934@kernel.org> (raw)
In-Reply-To: <1448645559-31167-1-git-send-email-namhyung@kernel.org>

Em Sat, Nov 28, 2015 at 02:32:37AM +0900, Namhyung Kim escreveu:
> Currently when perf fails to process samples for some reason, it doesn't
> show any message about the failure.  This is very inconvenient for users
> especially on TUI as screen is reset after the failure.
> 
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
>  tools/perf/builtin-report.c | 12 +++++++++---
>  1 file changed, 9 insertions(+), 3 deletions(-)
> 
> diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
> index 8a9c6908f54e..af5db885ea9c 100644
> --- a/tools/perf/builtin-report.c
> +++ b/tools/perf/builtin-report.c
> @@ -513,20 +513,26 @@ static int __cmd_report(struct report *rep)
>  	if (rep->cpu_list) {
>  		ret = perf_session__cpu_bitmap(session, rep->cpu_list,
>  					       rep->cpu_bitmap);
> -		if (ret)
> +		if (ret) {
> +			ui__error("failed to set cpu bitmap\n");

Why? See below.

>  			return ret;
> +		}
>  	}
>  
>  	if (rep->show_threads)
>  		perf_read_values_init(&rep->show_threads_values);
>  
>  	ret = report__setup_sample_type(rep);
> -	if (ret)
> +	if (ret) {
> +		/* report__setup_sample_type() already showed error message */
>  		return ret;
> +	}
>  
>  	ret = perf_session__process_events(session);
> -	if (ret)
> +	if (ret) {
> +		ui__error("failed to process sample\n");
>  		return ret;
> +	}

I'm applying this because it removes the potential flash, but would be
good to have the reason for this failure shown to the user.

- Arnaldo

  parent reply	other threads:[~2015-11-27 19:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 17:32 [PATCH 1/3] perf report: Show error message when processing sample fails Namhyung Kim
2015-11-27 17:32 ` [PATCH 2/3] perf hist: Do not skip elided fields when processing samples Namhyung Kim
2015-11-28  0:51   ` Arnaldo Carvalho de Melo
2015-11-29  7:56   ` [tip:perf/core] perf hists: " tip-bot for Namhyung Kim
2015-11-27 17:32 ` [PATCH 3/3] perf hists browser: Update nr entries regardless of min percent Namhyung Kim
2015-11-28  0:53   ` Arnaldo Carvalho de Melo
2015-11-29  7:56   ` [tip:perf/core] " tip-bot for Namhyung Kim
2015-11-27 19:56 ` Arnaldo Carvalho de Melo [this message]
2015-11-27 19:57   ` [PATCH 1/3] perf report: Show error message when processing sample fails Arnaldo Carvalho de Melo
2015-11-28  1:48     ` Namhyung Kim
2015-11-29  7:56 ` [tip:perf/core] " tip-bot for 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=20151127195627.GI5934@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.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;
as well as URLs for NNTP newsgroup(s).