From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751693AbbK1BtY (ORCPT <rfc822;w@1wt.eu>);
	Fri, 27 Nov 2015 20:49:24 -0500
Received: from mail-pa0-f51.google.com ([209.85.220.51]:35201 "EHLO
	mail-pa0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750716AbbK1BtW (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 27 Nov 2015 20:49:22 -0500
Date: Sat, 28 Nov 2015 10:48:51 +0900
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@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
Message-ID: <20151128014851.GA2191@danjae>
References: <1448645559-31167-1-git-send-email-namhyung@kernel.org>
 <20151127195627.GI5934@kernel.org>
 <20151127195721.GJ5934@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20151127195721.GJ5934@kernel.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Arnaldo,

On Fri, Nov 27, 2015 at 04:57:21PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Nov 27, 2015 at 04:56:27PM -0300, Arnaldo Carvalho de Melo escreveu:
> > 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>
> 
> Ah, I added a :
> 
> Reported-by: Ingo Molnar <mingo@kernel.org>
> 
> As this was due to those messages from Ingo, right?

Right.


> 
> > > ---
> > >  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.

Yes, but at least the last error/warning will be shown in the bottom.

Thanks,
Namhyung