Intel CONTROLLERS 413808 - Manual (Page 273)

Intel ® 413808 and 413812 I/O Controllers in TPER Mode
October 2007 Developer’s Manual
Order Number: 317805-001US 273
Address Translation Unit (PCI Express)—Intel
®
413808 and 413812
3.9.1.4 Unsupported Request
Unsupported Requests are detected by the address decode and translation logic. A TLP
is treated as unsupported in the following cases:
• the TLP fails to match any of the active Memory or I/O windows.
• a configuration TLP that targets an invalid function number
• receipt of a Vendor_Defined Type 0 message and
— the inbound vendor message received interrupt mask is set (ATUIMR[25])
— the inbound vendor_defined type 0 UR response bit is set (PEMCSR[14])
• a message request with an undefined or unsupported Message Code
• a poisoned I/O or Configuration request
• receipt of a Memory or I/O transaction while in a non-D0 power state
• receipt of a Memory Read Lock (MRdLk)
No checks are made to for address + length crossing a window boundary.
For posted transactions, this is
not an Advisory Error and an ERR_NONFATAL is sent to
the root complex.
For non-posted transactions, this is considered and Advisory Error. An ERR_COR is sent
to the root complex and a completion with UR status is returned to the requestor.
Note: When the severity setting in “PCI Express Uncorrectable Error Severity - ERRUNC_SEV”
register is fatal this is not an Advisory Error and an ERR_FATAL is sent to the root
complex.
3.9.1.5 Completer Abort
Requests that target abort or master abort on the Internal Bus are treated as a
Completer Abort.
These requests must have passed the Malformed TLP checks as well as the
Unsupported Request checks before they are issued on the internal bus.
For posted transactions, an ERR_NONFATAL is sent to the root complex.
For non-posted transactions, an ERR_COR is sent to the root complex and a completion
with CA status is returned to the requestor.
Note: When the severity setting in “PCI Express Uncorrectable Error Severity - ERRUNC_SEV”
register is fatal this is not an Advisory Error and an ERR_FATAL is sent to the root
complex.
3.9.1.6 Unexpected Completions
Unexpected completions occur when a completion transaction ID does not match a
outstanding request. When the Requestor ID of the completion matches a valid
function, the error gets logged in that function. Otherwise the error gets logged against
all functions.
This an Advisory Non-Fatal Error and an ERR_COR is sent to the root complex.
Note: When the severity setting in “PCI Express Uncorrectable Error Severity - ERRUNC_SEV”
register is fatal this is not an Advisory Error and an ERR_FATAL is sent to the root
complex.