mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: perf stat output
Date: Sun, 15 Nov 2009 12:05:08 -0200	[thread overview]
Message-ID: <20091115140507.GB21561@skywalker.lan> (raw)
In-Reply-To: <20091115091343.GA17358@elte.hu>

Ingo, following the tested patch you asked. It's a bit different of what you
sent because branch-misses is counted in another struct.


Lucas De Marchi

--
commit 70e98c814153f0026a683c5d19674ed8185d02fa
Author: Lucas De Marchi <lucas.de.marchi@gmail.com>
Date:   Sun Nov 15 11:20:56 2009 -0200

    Do not print ratio when task-clock event is not counted
    
    The ratio between the number of events and the time elapsed makes sense only
    if task-clock event is counted. Otherwise it will be simply a (confusing)
    
    	#      0.000 M/sec
    
    This patch outputs the ratio only if task-clock event is counted. Some test
    examples of before and after:
    
    Before:
    
    	[lucas@skywalker linux.trees.git]$ sudo perf stat -e branch-misses -a -- sleep 1
    
    	 Performance counter stats for 'sleep 1':
    
    		1367818  branch-misses            #      0.000 M/sec
    
    	    1.001494325  seconds time elapsed
    
    After (without task-clock):
    
    	[lucas@skywalker perf]$ sudo ./perf stat -e branch-misses -a -- sleep 1
    
    	 Performance counter stats for 'sleep 1':
    
    		1135044  branch-misses
    
    	    1.001370775  seconds time elapsed
    
    After (with task-clock):
    
    	[lucas@skywalker perf]$ sudo ./perf stat -e branch-misses -e task-clock -a -- sleep 1
    
    	 Performance counter stats for 'sleep 1':
    
    		1070111  branch-misses            #      0.534 M/sec
    	    2002.730893  task-clock-msecs         #      1.999 CPUs
    
    	    1.001640292  seconds time elapsed
    
    Signed-off-by: Lucas De Marchi <lucas.de.marchi@gmail.com>

diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
index c6df377..c70d720 100644
--- a/tools/perf/builtin-stat.c
+++ b/tools/perf/builtin-stat.c
@@ -357,7 +357,8 @@ static void abs_printout(int counter, double avg)
 			ratio = avg / total;
 
 		fprintf(stderr, " # %10.3f IPC  ", ratio);
-	} else if (MATCH_EVENT(HARDWARE, HW_BRANCH_MISSES, counter)) {
+	} else if (MATCH_EVENT(HARDWARE, HW_BRANCH_MISSES, counter) &&
+			runtime_branches_stats.n != 0) {
 		total = avg_stats(&runtime_branches_stats);
 
 		if (total)
@@ -365,7 +366,7 @@ static void abs_printout(int counter, double avg)
 
 		fprintf(stderr, " # %10.3f %%    ", ratio);
 
-	} else {
+	} else if (runtime_nsecs_stats.n != 0) {
 		total = avg_stats(&runtime_nsecs_stats);
 
 		if (total)


  reply	other threads:[~2009-11-15 14:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 22:03 Lucas De Marchi
2009-11-13  8:07 ` Peter Zijlstra
2009-11-13 14:46   ` Lucas De Marchi
2009-11-15  9:13 ` Ingo Molnar
2009-11-15 14:05   ` Lucas De Marchi [this message]
2009-11-15 14:27     ` Ingo Molnar
2009-11-15 14:30     ` [tip:perf/core] perf stat: Do not print ratio when task-clock event is not counted tip-bot for Lucas De Marchi

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=20091115140507.GB21561@skywalker.lan \
    --to=lucas.de.marchi@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

all inboxes | Powered by JetHome®