public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [RFC] Performance Events 'Samples' report
@ 2011-02-25  0:15 Cliff Wickman
  2011-02-25  2:40 ` Arnaldo Carvalho de Melo
  0 siblings, 1 reply; 3+ messages in thread
From: Cliff Wickman @ 2011-02-25  0:15 UTC (permalink / raw)
  To: linux-kernel; +Cc: a.p.zijlstra, paulus, mingo, acme

From: Cliff Wickman <cpw@sgi.com>

The perf command's report prints clock periods under the heading of 'Samples'.
Our applications people have been confused by this "Samples" heading.

perf report -n

# Overhead  Samples            Command         Shared Object                            Symbol
# ........ ..........  ...............  ....................  ................................
#
    99.41%1522136216246         pthreads  pthreads              [.] work_function
     0.33% 4980298302             perf  [kernel.kallsyms]     [k] clear_page_c
     ....

It would be more compact to print the number of samples.  And that would
be consistent with the heading.

Below is the code that displays the periods.  I don't see that the number
of samples is available here, but probably easily could be.
I presume that clock periods are derived from #samples * sample period.

perf/util/hist.c

 640 
 641         if (symbol_conf.show_nr_samples) {
 642                 if (sep)
 643                         ret += snprintf(s + ret, size - ret, "%c%" PRIu64,      *sep, period);
 644                 else
 645                         ret += snprintf(s + ret, size - ret, "%11" PRIu64,      period);
 646         }
 647 

Signed-off-by: Cliff Wickman <cpw@sgi.com>


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-02-25 10:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-02-25  0:15 [RFC] Performance Events 'Samples' report Cliff Wickman
2011-02-25  2:40 ` Arnaldo Carvalho de Melo
2011-02-25 10:26   ` Ingo Molnar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox