From: Chris Freehill <cfreehill@utexas.edu>
To: linux-perf-users@vger.kernel.org
Subject: perf uncore behavior
Date: Fri, 1 May 2015 15:55:35 -0500 [thread overview]
Message-ID: <CANFySvewjJTo7Cezq3e1SPAFFmRRRWADTJ50T5rubvcLrAV2xA@mail.gmail.com> (raw)
Hi,
I'm trying to get clarification on the meaning of the results perf
gives for uncore events, depending on the options.
Here are some examples:
1. $ perf stat -a -e "uncore_cbox_0/clockticks/" sleep 1
2. $ perf stat -e "uncore_cbox_0/clockticks/" sleep 1
3. $ perf stat -a -C0 -e "uncore_cbox_0/clockticks/" sleep 1
It appears #2 is not supported. If it was supported, I would take it
to mean the number of uncore events counted while the process was
active, regardless of which processor it was running on. Right? Is
there any reason it's not implemented (for example it's nonsensical)
or it just has been tackled yet?
Are 1 and 3 effectively the same, since uncore events are not specific
to a core? I would think they would be the same. If not, what is the
difference?
thanks,
Chris
next reply other threads:[~2015-05-01 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 20:55 Chris Freehill [this message]
2015-05-02 1:40 ` perf uncore behavior Andi Kleen
2015-05-02 2:31 ` Chris Freehill
2015-05-02 12:16 ` Andi Kleen
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=CANFySvewjJTo7Cezq3e1SPAFFmRRRWADTJ50T5rubvcLrAV2xA@mail.gmail.com \
--to=cfreehill@utexas.edu \
--cc=linux-perf-users@vger.kernel.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).