From: Arun Sharma <asharma@fb.com>
To: Vince Weaver <vweaver1@eecs.utk.edu>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf_event validation tests
Date: Fri, 27 May 2011 15:45:44 -0700 [thread overview]
Message-ID: <20110527224544.GA847@dev1756.snc6.facebook.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1105271752090.5485@cl320.eecs.utk.edu>
On Fri, May 27, 2011 at 05:53:41PM -0400, Vince Weaver wrote:
> Hello
>
> a while back it was mentioned it would be nice to have some perf_event
> validation tests.
>
> I've posted some here:
> http://web.eecs.utk.edu/~vweaver1/projects/perf-events/validation.html
>
cache-references.c:
pe.config=PERF_COUNT_HW_CACHE_REFERENCES;
...
for(i=0; i<ARRAYSIZE; i++) {
array[i]=(double)i;
}
...
if (!quiet) printf("\tL1 D accesseses: %lld %lf\n",count,aSumm);
PERF_COUNT_HW_CACHE_REFERENCES is counting LLC references on many
platforms. Did you mean to use PERF_COUNT_HW_CACHE_L1D here?
-Arun
next prev parent reply other threads:[~2011-05-27 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 21:53 perf_event validation tests Vince Weaver
2011-05-27 22:45 ` Arun Sharma [this message]
2011-05-28 2:03 ` Vince Weaver
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=20110527224544.GA847@dev1756.snc6.facebook.com \
--to=asharma@fb.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=vweaver1@eecs.utk.edu \
/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).