Uncore Manual

Introduction
14 Reference Number: 329468-002
•e.g. with:Cn_MSR_PMON_BOX_FILTER.{opc,nid}={0x182,my_node}
Requires reading a fixed data register
• For the case where the metric requires the information contained in a fixed data register, the
mnemonic for the register will be included in the equation. Software will be responsible for
configuring the data register and setting it to start counting with the other events used by the
metric.
•e.g. POWER_THROTTLE_CYCLES.RANKx / MC_Chy_PCI_PMON_CTR_FIXED
Requires more input to software to determine the specific event/subevent
• In some cases, there may be multiple events/subevents that cover the same information across
multiple like hardware units. Rather than manufacturing a derived event for each combination,
the derived event will use a lower case variable in the event name.
•e.g. POWER_CKE_CYCLES.RANKx / MC_Chy_PCI_PMON_CTR_FIXED where ‘x’ is a variable to cover
events POWER_CKE_CYCLES.RANK0 through POWER_CKE_CYCLES.RANK7
Requires setting extra control bits in the register the event has been programmed in:
• event_name[.subevent_name]{ctrl_bit[=value],}
•e.g.
COUNTER0_OCCUPANCY{edge_det,thresh=0x1}
NOTE: If there is no [=value] specified it is assumed that the bit must be set to 1.
Requires gathering of extra information outside the box (often for common terms):
• See following section for a breakdown of common terms found in Derived Events.
1.6.1 On Common Terms found in Derived Events
To convert a Latency term from a count of clocks to a count of nanoseconds:
•(Latency Metric) - {Box}_CLOCKTICKS * (1000 / UNCORE_FREQUENCY)
To convert a Bandwidth term from a count of raw bytes at the operating clock to GB/sec:
•((Traffic Metric in Bytes) / (TOTAL_INTERVAL / (TSC_SPEED * 1000000))) / GB_CONVERSION
• e.g. For READ_MEM_BW, an event derived from iMC:CAS_COUNT.RD * 64, which is the amount of
memory bandwidth consumed by read requests, put ‘READ_MEM_BW’ into the bandwidth term to
convert the measurement from raw bytes to GB/sec.
Following are some other terms that may be found within Metrics and how they should be interpreted.
• GB_CONVERSION: 1024^3
• TSC_SPEED: Time Stamp Counter frequency in MHz
• TOTAL_INTERVAL: Overall sample interval (TSC) for the instructions retired event. Typically used
to compute a per send metric. Dividing the TOTAL_INTERVAL by CPU_SPEED * 1,000,000 is the
number of seconds in the sample interval.
• TOTAL_PROC_CYC: Total number of CPU cycles for a processor event value. Used with processor
event data to determine time or work per time as in MB/sec. QPI_LINKS: 2-3 for Intel Xeon
Processor E5-2600 v2 Product Family.
• IMC_CHANNELS: Up to 8 for Ivy Bridge-EP microarchitecture.
§