From: Manuel Selva <selva.manuel@gmail.com>
To: Andreas Hollmann <hollmann@in.tum.de>
Cc: Manuel Selva <manuel.selva@insa-lyon.fr>,
Andi Kleen <andi@firstfloor.org>,
linux-perf-users@vger.kernel.org
Subject: Re: Link between Intel documentation events and perf list events
Date: Tue, 02 Jul 2013 15:33:18 +0200 [thread overview]
Message-ID: <51D2D69E.9020207@gmail.com> (raw)
In-Reply-To: <CAGz0_-3uWqVqPLwKvpiuveBJo1DT3B5TynK9ebdBZuw5ZGe3nQ@mail.gmail.com>
Thanks again for the help.Your answer suggests that events listed as
Hardware event by perf listare what is called Architecural Events for
Intel processors, isn't it ?
On my Sandy Bridge core i5-2520M, perf list reports 10 hardware events,
where as they are only 7 entriesin the table 18-1 of Intel documentation
you mentioned. So I am wondering what are these 3 additional events;
event=0x00,umask=0x03 (ref-cycles)
event=0xb1,umask=0x01,inv,cmask=0x01 (stalled-cycles-backend)
event=0x0e,umask=0x01,inv,cmask=0x01 (stalled-cycles-frontend)
Looking at table 19-7 in the same Intel document, I can see non
architectural events for my core i5-2xxx. In this table I can see that:
ref-cycles ==> Can't find it
stalled-cycles-backend ==> Counts total number of uops to be dispatched
per- thread each cycle. Set Cmask = 1, INV =1 to count stall cycles.
stalled-cycles-frontend ==> Increments each cycle the # of Uops issued
by the RAT to RS.Set Cmask = 1, Inv = 1, Any= 1to count stalled cycles
of this core.
So my question is what is ref-cycles andwhat is the common property of
event displayed as Hardware Event by perf ?
Manu
On 07/02/2013 02:39 PM, Andreas Hollmann wrote:
> Hi,
>
> since Kernel version 3.7 you can lookup the used raw event in
> /sys/device/cpu/events and compare it
> to Table 18-1 SDM Volume 3B: System Programming Guide, Part 2.
>
> $ cd /sys/devices/cpu/events/
> $ echo *; cat *
> branch-instructions branch-misses cache-misses cache-references
> cpu-cycles instructions
> event=0xc4
> event=0xc5
> event=0x2e,umask=0x41
> event=0x2e,umask=0x4f
> event=0x3c
> event=0xc0
>
> Here is commit from Jiri Olsa that makes it possible.
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a47473939db20e3961b200eb00acf5fcf084d755
>
> Regards,
> Andreas
>
>
>
> 2013/7/2 Manuel Selva <manuel.selva@insa-lyon.fr>:
>> Thanks for the answer Andi.
>>
>> On a more general sense, how one can link perf events (as reported by perf
>> list) to hardware documentation ? Is there some document explaining that or
>> should I dig into the perf code source code in the Linux kernel ?
>>
>> Manu
>>
>>
>> On 07/02/2013 05:55 AM, Andi Kleen wrote:
>>> Manuel Selva<manuel.selva@insa-lyon.fr> writes:
>>>
>>>> My question is about the link between events reported in Intel
>>>> documentation and events listed by perf list. Is the perf list
>>>> cache-misses event the same than the one mentioned as Last-level cache
>>>> missesin Intel documentation ?
>>> Yes it is
>>>
>>> (at least currently, perf events are not particularly well defined
>>> and have changed in the past. However this one is proably not likely
>>> to change)
>>>
>>> -Andi
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-perf-users"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-07-02 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 16:10 Link between Intel documentation events and perf list events Manuel Selva
2013-07-02 3:55 ` Andi Kleen
2013-07-02 7:53 ` Manuel Selva
2013-07-02 12:39 ` Andreas Hollmann
2013-07-02 13:33 ` Manuel Selva [this message]
2013-07-02 14:49 ` Andi Kleen
2013-07-03 9:06 ` Manuel Selva
2013-07-03 13:28 ` Andi Kleen
2013-07-03 14:02 ` Manuel Selva
[not found] ` <51D28568.8070904@insa-lyon.fr>
2013-07-02 14:41 ` 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=51D2D69E.9020207@gmail.com \
--to=selva.manuel@gmail.com \
--cc=andi@firstfloor.org \
--cc=hollmann@in.tum.de \
--cc=linux-perf-users@vger.kernel.org \
--cc=manuel.selva@insa-lyon.fr \
/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).