Uncore Manual

Uncore Performance Monitoring
Home Agent (HA) Performance Monitoring
58 Reference Number: 329468-002
In addition to generic event counting, each HA provides a pair of Address Match registers and an
Opcode Match register that allow a user to filter incoming packet traffic according to the packet Opcode,
Message Class and Physical Address. The ADDR_OPC_MATCH.FILT event is provided to capture the
filter match as an event. The fields are laid out as follows:
NOTE
Refer to Table 2-216, “Intel® QuickPath Interconnect Packet Message Classes” and
Table 2-218, “Opcodes (Alphabetical Listing)” to determine the encodings of the HA
OpcodeMatch Register field.
Table 2-42. HA_PCI_PMON_BOX_OPCODEMATCH Register – Field Definitions
Table 2-43. HA_PCI_PMON_BOX_ADDRMATCH1 Register – Field Definitions
NOTEHA_PCI_PMON_BOX_ADDRMATCH0 Register – Field Definitions
2.4.3 HA Performance Monitoring Events
The performance monitoring events within the HA include all events internal to the HA as well as events
which track ring related activity at the HA ring stops. Internal events include the ability to track Direc-
tory Activity, Direct2Core Activity, iMC Read/Write Traffic, time spent dealing with Conflicts, etc.
Field Bits Attr
HW
Reset
Val
Description
ig 31:6 RV 0 Ignored
opc 5:0 RWS 0 Match to incoming opcode
[5:4] are a 2b version of the Message Class representing
AD Ring traffic
00 - HOM0
01 - HOM1
10 - NDR
11 - SNP
[3:0] QPI Opcode - See Opcode Match by Message Class
referred to in NOTE
Field Bits Attr
HW
Reset
Val
Description
ig 31:14 RV 0 Ignored
hi_addr 13:0 RWS 0 Match to this System Address - Most Significant 14b of
cache aligned address [45:32]
Field Bits
HW
Reset
Val
HW
Reset
Val
Description
lo_addr 31:6 RWS 0 Match to this System Address - Least Significant 26b of
cache aligned address [31:6]
ig 5:0 RV 0 Ignored