From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ashay Rane <ashay.r@gmail.com>
Cc: David Ahern <dsahern@gmail.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-perf-users@vger.kernel.org,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Ashay Rane <ashay.rane@tacc.utexas.edu>
Subject: Re: [PATCH 1/1] Fix number of events displayed in header
Date: Tue, 20 Mar 2012 20:59:57 +0100 [thread overview]
Message-ID: <1332273597.18960.454.camel@twins> (raw)
In-Reply-To: <CANn2t1n3fiVGqMKm=a7k3bKgKRzVdo3zu54ZKiCMqtDFbS4MeA@mail.gmail.com>
On Tue, 2012-03-20 at 14:51 -0500, Ashay Rane wrote:
> The problem I am seeing is that the `perf record' output does not
> comform with the output of `perf stat'. For example, for `hackbench 10
> process 1000', I see 19 x 10^9 cycles reported by `perf stat'.
> However, `perf report -n' prints "Events: 2K cycles" and `perf report
> -n --dso hackbench' prints "Events: 47 cycles".
Ah, read it as if perf report is saying: Samples: 47 of event: cycles.
That is, its telling you the cycles event had 47 overflows causing 47
samples to be taken (IP, etc..) and written out.
The point of reporting this number is that it puts the accuracy of the
percentages into perspective. The more samples, the greater the coverage
and more accurate the actual percentage of time spend in the various
functions.
next prev parent reply other threads:[~2012-03-20 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 19:23 [PATCH 1/1] Fix number of events displayed in header Ashay Rane
2012-03-20 19:42 ` Arnaldo Carvalho de Melo
2012-03-20 19:46 ` David Ahern
2012-03-20 19:47 ` Peter Zijlstra
2012-03-20 19:51 ` Ashay Rane
2012-03-20 19:59 ` Peter Zijlstra [this message]
2012-03-20 20:04 ` Ashay Rane
2012-03-20 20:09 ` Peter Zijlstra
2012-03-20 20:27 ` Ashay Rane
-- strict thread matches above, loose matches on Subject: below --
2012-03-13 22:24 Ashay Rane
2012-03-13 22:24 ` Ashay Rane
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=1332273597.18960.454.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=ashay.r@gmail.com \
--cc=ashay.rane@tacc.utexas.edu \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.