Error Detection And Handling; Table 9.5 Prioritization Of Acs Checks For Completion Tlps; Table 9.6 Tlp Types Affected By Acs Checks - Renesas IDT 89HPES48H12G2 User Manual

IDT Theory of Operation
Notes
PES48H12G2 User Manual
ACS Check
ACS Upstream For-
warding
ACS Peer-to-Peer
Completion Redirect

Table 9.5 Prioritization of ACS Checks for Completion TLPs

ACS checks are only applicable to certain TLP types. Table 9.6 list the ACS checks supported by the
PES48H12G2 and the TLP types on which they are applied.
ACS Check
ACS Source Validation
ACS Translation Blocking
ACS P2P Request Re-direct
ACS P2P Completion Re-direct
ACS Upstream Forwarding
ACS P2P Egress Control
ACS Direct Translated P2P
ACS violations associated with transparent operation are handled as described in section Error Detec-
tion and Handling on page 9-6.

Error Detection and Handling

This section describes error conditions associated with the switch. This includes physical, data-link, and
transaction layer errors detected by the switch ports, as well as routing errors associated with the PCI-
to_PCI bridge function in each switch port. Internal switch errors (i.e., parity errors, switch time-out, and
internal memory errors) are not described here. Refer to section Internal Errors on page 3-13 for details on
port operational modes.
Error detection and handling in the PES48H12G2 follows the requirements in the PCI Express 2.0 spec-
ification. The error checking and handling described here is performed by each PES48H12G2 port. In
cases where the error condition propagates among ports (e.g., a poisoned TLP flowing from the upstream
port to a downstream port), each port performs error checking and handling independently.
The errors described below are associated with specific actions to log and report the error. The terms
'uncorrectable error processing' and 'correctable error processing' refer to the processing described in
Section 6.2.5 of the PCI Express 2.0 specification.
Some of the errors described below are marked as function-specific when the 'function claims the TLP'.
Priority
2 (Highest) Applicable to request or completion TLPs
received by the downstream port on its ingress
link that target the port's egress link. This is not
considered a peer-to-peer transfer.
1 (Lowest) Applicable to non-relaxed-ordered peer-to-peer
completion TLPs only
Applicable to this TLP type(s)
Request TLPs
Memory Request TLPs
Peer-to-Peer Request TLPs
Peer-to-Peer Completion TLPs
Request or Completion TLPs that target the port's own
egress link
Peer-to-Peer Request TLPs
Peer-to-Peer Memory Request TLPs

Table 9.6 TLP Types Affected by ACS Checks

9 - 6
Comment
April 5, 2013