R-Box Output Port; R-Box Link Layer Resources; R-Box Performance Monitoring Overview; Choosing An Event To Monitor - Example - Intel BX80571E7500 - Core 2 Duo 2.93 GHz Processor Programming Manual

I ® X ® P 7500 S
NTEL EON ROCESSOR
2.6.1.3

R-Box Output Port

The R-Box output port acts as a virtual wire that is responsible for de-coupling the crossbar from further
downstream paths to on-chip or off-chip ports while carrying out the Link layer functions.
2.6.1.4

R-Box Link Layer Resources

Each R-Box port supports up to three virtual networks (VN0, VN1, and VNA) as defined by the Intel
QuickPath Interconnect Specification. The following table specifies the port resources.
Home
Snoop
Non-Data Response
Data Response
Non-Coherent Standard
Non-Coherent Bypass
2.6.2

R-Box Performance Monitoring Overview

The R-Box supports performance event monitoring through its Performance Monitoring Unit (PMU). At a
high level, the R-Box PMU supports features comparable to other uncore PMUs. R-Box PMUs support
both Global and Local PMU freeze/unfreeze. R-Box PMUs are accessible through Machine Specific
Registers (MSRs). R-Box PMU consists of 16 48b-wide performance monitoring data counters and a
collection of other peripheral control registers.
For information on how to setup a monitoring session, refer to
.
Session"
The counters, along with the control register paired with each one, are split. Half of the counters (0-7)
can monitor events occurring on the 'left' side of the R-Box (ports 0-3) and the other half (8-15)
monitor ports 4-7 on the 'right' side.
Since the R-Box consists of 12 almost identical ports, R-Box perfmon events consist of an identical set
of events for each port. The R-Box perfmon usage model allows monitoring of multiple ports at the
same time. R-Box PMUs do not provide any global performance monitoring events.
However, unlike many other uncore boxes, event programming in the R-Box is hierarchical. It is
necessary to program multiple MSRs to select the event to be monitored. In order to program an event,
each of the control registers for its accompanying counter must be redirected to a subcontrol register
attached to a specific port. Each control register can be redirected to one of 2 IPERF control registers
(for RIX events), one of 2 fields in a QLX control register or one of 2 mask/match registers. Therefore,
it is possible to monitor up to two of any event per port.
The R-Box also includes a pair of mask/match registers on each port that allow a user to match packets
serviced (packet is transferred from input to output port) by the R-Box according to various standard
packet fields such as message class, opcode, etc.
2.6.2.1

Choosing An Event To Monitor - Example

1) Pick an event to monitor (e.g. FLITS_SENT)
2) Pick a port to monitor on (e.g. QPI0)
U P
ERIES NCORE ROGRAMMING
Table 2-38. Input Buffering Per Port
Message Class
HOM
SNP
NDR
DRS
NCS
NCB
G
UIDE
VNA
Abbr
Pkts Flits
96
Section 2.1.2, "Setting up a Monitoring
UNCORE PERFORMANCE MONITORING
VN0 VN1
Pkts Flits Pkts
1 1 1
1 1 1
1 1 1
1 up to 11 1
1 up to 3 1
1 up to 11 1
®
Flits
1
1
1
up to 11
up to 3
up to 11
2-73