1LIBPFM(3)                  Linux Programmer's Manual                 LIBPFM(3)
2
3
4

NAME

6       libpfm_intel_ivbep_unc_cbo  -  support  for  Intel  Ivy Bridge-EP C-Box
7       uncore PMU
8

SYNOPSIS

10       #include <perfmon/pfmlib.h>
11
12       PMU name: ivbep_unc_cbo[0-7]
13       PMU desc: Intel Ivy Bridge-EP C-Box uncore PMU
14
15

DESCRIPTION

17       The library supports the Intel  Ivy  Bridge  C-Box  (coherency  engine)
18       uncore  PMU.   This PMU model only exists on Ivy Bridge model 62. There
19       is one C-box PMU per physical core. Therefore there are up  to  fifteen
20       identical  C-Box  PMU  instances  numbered from 0 to 14. On dual-socket
21       systems, the number refers to the C-Box PMU on  the  socket  where  the
22       program  runs.  For  instance, if running on CPU15, then ivbep_unc_cbo0
23       refers to the C-Box for physical core 0 on  socket  1.  Conversely,  if
24       running  on  CPU0, then the same ivbep_unc_cbo0 refers to the C-Box for
25       physical core 0 but on socket 0.
26
27       Each C-Box PMU implements 4 generic counters and two  filter  registers
28       used only with certain events and umasks.
29
30

MODIFIERS

32       The  following modifiers are supported on Intel Ivy Bridge C-Box uncore
33       PMU:
34
35       e      Enable edge detection, i.e., count only when there  is  a  state
36              transition  from  no  occurrence  of  the  event to at least one
37              occurrence. This modifier must be combined with a threshold mod‐
38              ifier (t) with a value greater or equal to one.  This is a bool‐
39              ean modifier.
40
41       t      Set the threshold value. When  set  to  a  non-zero  value,  the
42              counter counts the number of C-Box cycles in which the number of
43              occurrences of the event is greater or equal to  the  threshold.
44              This is an integer modifier with values in the range [0:255].
45
46       nf     Node   filter.   Certain   events,   such  as  UNC_C_LLC_LOOKUP,
47              UNC_C_LLC_VICTIMS, provide a NID umask.  Sometimes  the  NID  is
48              combined  with  other  filtering  capabilities, such as opcodes.
49              The node filter is an 8-bit max bitmask. A node corresponds to a
50              processor  socket.  The  legal  values  therefore  depend on the
51              underlying hardware configuration. For dual-socket systems,  the
52              bitmask has two valid bits [0:1].
53
54       cf     Core  Filter.  This  is  a  3-bit filter which is used to filter
55              based on physical core origin of  the  C-Box  request.  Possible
56              values  are 0-7. If the filter is not specified, then no filter‐
57              ing takes place.
58
59       tf     Thread Filter. This is a 1-bit filter which is used to filter C-
60              Box requests based on logical processor (hyper-thread) identifi‐
61              cation. Possibles values are 0-1. If the filter  is  not  speci‐
62              fied, then no filtering takes place.
63
64       nc     Non-Coherent.  This is a 1-bit filter which is used to filter C-
65              Box requests only for the TOR_INSERTS and  TOR_OCCUPANCY  umasks
66              using  the  OPCODE matcher. If the filter is not specified, then
67              no filtering takes place.
68
69       isoc   Isochronous. This is a 1-bit filter which is used to  filter  C-
70              Box  requests  only for the TOR_INSERTS and TOR_OCCUPANCY umasks
71              using the OPCODE matcher. If the filter is not  specified,  then
72              no filtering takes place.
73
74

Opcode filtering

76       Certain  events,  such as UNC_C_TOR_INSERTS supports opcode matching on
77       the C-BOX transaction type. To use this feature, first an opcode match‐
78       ing  umask  must be selected, e.g., MISS_OPCODE.  Second, the opcode to
79       match on must be selected via a second umask among  the  OPC_*  umasks.
80       For  instance,  UNC_C_TOR_INSERTS:OPCODE:OPC_RFO,  counts the number of
81       TOR insertions for RFO transactions.
82
83       Opcode matching may  be  combined  with  node  filtering  with  certain
84       umasks.  In  general,  the  filtering support is encoded into the umask
85       name, e.g., NID_OPCODE supports both node  and  opcode  filtering.  For
86       instance, UNC_C_TOR_INSERTS:NID_OPCODE:OPC_RFO:nf=1.
87
88

AUTHORS

90       Stephane Eranian <eranian@gmail.com>
91
92
93
94                                February, 2014                       LIBPFM(3)
Impressum