mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 5/7] perf, tools, stat: Implement --metric-only mode
Date: Wed, 2 Mar 2016 12:57:50 +0100	[thread overview]
Message-ID: <20160302115750.GA28054@krava.redhat.com> (raw)
In-Reply-To: <1456858672-21594-6-git-send-email-andi@firstfloor.org>

On Tue, Mar 01, 2016 at 10:57:50AM -0800, Andi Kleen wrote:

SNIP

>  static void print_interval(char *prefix, struct timespec *ts)
>  {
>  	FILE *output = stat_config.output;
> @@ -1130,7 +1287,7 @@ static void print_interval(char *prefix, struct timespec *ts)
>  
>  	sprintf(prefix, "%6lu.%09lu%s", ts->tv_sec, ts->tv_nsec, csv_sep);
>  
> -	if (num_print_interval == 0 && !csv_output) {
> +	if (num_print_interval == 0 && !csv_output && !metric_only) {
>  		switch (stat_config.aggr_mode) {
>  		case AGGR_SOCKET:
>  			fprintf(output, "#           time socket cpus             counts %*s events\n", unit_width, "unit");
> @@ -1217,6 +1374,17 @@ static void print_counters(struct timespec *ts, int argc, const char **argv)
>  	else
>  		print_header(argc, argv);
>  
> +	if (metric_only) {
> +		static int num_print_iv;
> +
> +		if (num_print_iv == 0)
> +			print_metric_headers(prefix);
> +		if (num_print_iv++ == 25)
> +			num_print_iv = 0;
> +		if (stat_config.aggr_mode == AGGR_GLOBAL && prefix)
> +			fprintf(stat_config.output, "%s", prefix);
> +	}
> +
>  	switch (stat_config.aggr_mode) {
>  	case AGGR_CORE:
>  	case AGGR_SOCKET:
> @@ -1229,6 +1397,8 @@ static void print_counters(struct timespec *ts, int argc, const char **argv)
>  	case AGGR_GLOBAL:
>  		evlist__for_each(evsel_list, counter)
>  			print_counter_aggr(counter, prefix);
> +		if (metric_only)
> +			fputc('\n', stat_config.output);

this new line printing based on metric_only is all over the place..
could we sorted out new lines in the print callbacks?  this makes
my head hurt ;-)

also some comments would be great

thanks,
jirka

  reply	other threads:[~2016-03-02 11:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 18:57 perf, tools: Refactor and support interval and CSV metrics Andi Kleen
2016-03-01 18:57 ` [PATCH 1/7] perf, tools, stat: Check existence of frontend/backed stalled cycles Andi Kleen
2016-03-01 18:57 ` [PATCH 2/7] perf, tools, stat: Implement CSV metrics output Andi Kleen
2016-03-01 18:57 ` [PATCH 3/7] perf, tools, stat: Support metrics in --per-core/socket mode Andi Kleen
2016-03-01 18:57 ` [PATCH 4/7] perf, tools, stat: Document CSV format in manpage Andi Kleen
2016-03-02 11:23   ` Jiri Olsa
2016-03-01 18:57 ` [PATCH 5/7] perf, tools, stat: Implement --metric-only mode Andi Kleen
2016-03-02 11:57   ` Jiri Olsa [this message]
2016-03-02 15:35     ` Andi Kleen
2016-03-01 18:57 ` [PATCH 6/7] perf, tools, stat: Add --metric-only support for -A Andi Kleen
2016-03-01 18:57 ` [PATCH 7/7] perf, tools, stat: Check for frontend stalled for metrics Andi Kleen
2016-03-02 12:04   ` Jiri Olsa
2016-03-05  8:21   ` [tip:perf/core] perf " tip-bot for Andi Kleen
2016-03-01 19:05 ` perf, tools: Refactor and support interval and CSV metrics Arnaldo Carvalho de Melo
  -- strict thread matches above, loose matches on Subject: below --
2016-03-03 23:57 Andi Kleen
2016-03-03 23:57 ` [PATCH 5/7] perf, tools, stat: Implement --metric-only mode Andi Kleen
2016-03-10 11:28   ` Jiri Olsa
2016-03-03  0:24 perf, tools: Refactor and support interval and CSV metrics Andi Kleen
2016-03-03  0:24 ` [PATCH 5/7] perf, tools, stat: Implement --metric-only mode Andi Kleen
2016-02-29 22:36 perf, tools: Refactor and support interval and CSV metrics Andi Kleen
2016-02-29 22:36 ` [PATCH 5/7] perf, tools, stat: Implement --metric-only mode Andi Kleen
2016-03-01 12:32   ` Jiri Olsa
2016-03-01 14:53     ` Andi Kleen
2016-03-01 12:32   ` Jiri Olsa
2016-03-01 18:51     ` Andi Kleen
2016-03-02 11:28     ` Jiri Olsa
2016-03-02 15:38       ` Andi Kleen
2016-03-02 15:46         ` Jiri Olsa

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=20160302115750.GA28054@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.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

Powered by JetHome