public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@Kernel.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf, tools: Print stddev in CSV mode with -a
Date: Fri, 10 Apr 2015 10:40:55 +0200	[thread overview]
Message-ID: <20150410084055.GB27593@krava> (raw)
In-Reply-To: <1428504501-9102-1-git-send-email-andi@firstfloor.org>

On Wed, Apr 08, 2015 at 07:48:21AM -0700, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
> 
> Currently with -r.. -a -A ,x or other aggregation we don't print the
> stddev into the CSV output. Just drop the checks preventing this.
> 
> Signed-off-by: Andi Kleen <ak@linux.intel.com>

we already print this print_counter_aggr so I think we can consider
this as bugfix even though it changes current csv format

Acked-by: Jiri Olsa <jolsa@kernel.org>

thanks,
jirka

> ---
>  tools/perf/builtin-stat.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index d4d1b77..3de0ea5 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -1282,8 +1282,7 @@ static void print_aggr(char *prefix)
>  			else
>  				abs_printout(id, nr, counter, uval);
>  
> -			if (!csv_output)
> -				print_noise(counter, 1.0);
> +			print_noise(counter, 1.0);
>  
>  			print_running(run, ena);
>  			fputc('\n', output);
> @@ -1392,8 +1391,7 @@ static void print_counter(struct perf_evsel *counter, char *prefix)
>  		else
>  			abs_printout(cpu, 0, counter, uval);
>  
> -		if (!csv_output)
> -			print_noise(counter, 1.0);
> +		print_noise(counter, 1.0);
>  		print_running(run, ena);
>  
>  		fputc('\n', output);
> -- 
> 2.3.3
> 

      reply	other threads:[~2015-04-10  8:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 14:48 [PATCH] perf, tools: Print stddev in CSV mode with -a Andi Kleen
2015-04-10  8:40 ` Jiri Olsa [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=20150410084055.GB27593@krava \
    --to=jolsa@redhat.com \
    --cc=acme@Kernel.org \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.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