Reference Number: 327043-001
15
Introduction
• 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
) / (SAMPLE_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
• SAMPLE_INTERVAL = TSC end time - TSC start time.
§
