From: Andi Kleen <andi@firstfloor.org>
To: Chris Freehill <cfreehill@utexas.edu>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf uncore behavior
Date: Fri, 01 May 2015 18:40:52 -0700 [thread overview]
Message-ID: <87618blpsr.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <CANFySvewjJTo7Cezq3e1SPAFFmRRRWADTJ50T5rubvcLrAV2xA@mail.gmail.com> (Chris Freehill's message of "Fri, 1 May 2015 15:55:35 -0500")
Chris Freehill <cfreehill@utexas.edu> writes:
>
> 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?
It's non sensical. Uncore does not support per process measurements.
> 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?
1. will sum up events from all sockets/nodes.
3. will only print from the socket/node associated with CPU 0.
-andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2015-05-02 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 20:55 perf uncore behavior Chris Freehill
2015-05-02 1:40 ` Andi Kleen [this message]
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=87618blpsr.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=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 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.