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 21:09:51 +0100 [thread overview]
Message-ID: <1332274191.18960.459.camel@twins> (raw)
In-Reply-To: <CANn2t1=A8Gz4+YL2+fyBW3fzWzh4FN5Ktx_pBZidAEE5KbkiZQ@mail.gmail.com>
On Tue, 2012-03-20 at 15:04 -0500, Ashay Rane wrote:
> Oh, okay. Thanks for the clarification!
>
> However, my reasoning behind including the actual count of the events
> was that (as far as I can tell) it is not displayed in any of the perf
> report outputs. I understand that the count is not precise (because of
> sampling errors) but the sampling frequency (-F) can always be
> adjusted to get a more accurate number.
>
> With the inclusion of the count, it then becomes possible to compare
> multiple different versions of a program. Hence the patch.
I'm okay if you change the wording of the existing message to be
clearer. I'm also okay if you add this extra information if you find
this useful.
In that case, also have a look at the data generated by perf record -s,
this dumps a PERF_RECORD_READ of the actual counter value at the exit of
every task [doesn't work with per-cpu counters].
next prev parent reply other threads:[~2012-03-20 20:09 UTC|newest]
Thread overview: 10+ 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
2012-03-20 20:04 ` Ashay Rane
2012-03-20 20:09 ` Peter Zijlstra [this message]
2012-03-20 20:27 ` Ashay Rane
-- strict thread matches above, loose matches on Subject: below --
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=1332274191.18960.459.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).