Lines Matching refs:complex

267  * A faulty PCI Express hostbridge (root complex) may cause:
901  * handling of fatal and nonfatal error messages propagated up to root complex
903  * Use these for errors reported by root-complex on behalf of another device.
980  *   poisoning (be it root complex or downstream port of a switch) also raises
985  * root complex will see and report an ma. Use flt-ur-u to represent this.
1046  *   the root complex identifying the leaf device, we won't actually be informed
1096  *   though we should still see a nonfatal error reported from the root complex
1101  * eventually get a cto at the root complex - so use an nr-u at the pciex
1106  * reported from the root complex identifying the leaf device. The combination
1107  * of a nonfatal error reported from the root complex and a cto from the root
1108  * complex is sufficient to positively identify this case.
1142  *   complex identifying the leaf device, we won't actually be informed that
1177  *   ereport generated from the root complex.
1178  * - poisreq-u propagates up to the root complex and any switch ports on
1181  *   complex should also report a ptlp.
1183  * Additionally, as the root complex may treat the request as a ur, which the
1188  * sec-mdpe) at the root complex. Recognizing which originating devices may be
1259  *   ereport generated from the root complex.
1260  * - poiscomp-u propagates up to the root complex and any switches on
1261  *   route will raise ptlp and sec-mdpe ereports. The root complex will also
1265  * the root complex. Recognizing which originating devices may be implicated
1330  *   ereport generated from the root complex.
1331  * - ecrcreq-u propagates up to the root complex which must report it with an
1334  * Additionally, as the root complex will just throw away the packet, we may
1339  * cto) at the root complex. Recognizing which leaf device may be implicated
1374  *   ereport generated from the root complex.
1375  * - ecrccomp-u propagates up to the root complex, which should report it with
1379  * Additionally, as the root complex will just throw away the packet, we'll
1384  * root complex. Recognizing which leaf device may be implicated can be done
1417  *   is always at the root complex. For a hardened leaf device driver, we will
1420  *   should still see a nonfatal error reported from the root complex
1449  * - flt-nr-u will effectively cascade upstream to the root complex which will
1474  * still see a fatal error reported from the root complex identifying the leaf
1515  * This could be the fault of the root complex or a switch reporting an internal
1523  * The fault can always be recognized by the ca ereport from the root complex
1560  * reporting an internal error, or of the root complex sending an invalid
1567  * The fault can always be recognized from the sec-rta bit at the root complex.
1574  * message ereport from the root complex or from the target-rta ereport.
1611  * complex or downstream switch port. The originator of the request can be
1652  * complex identifying the leaf device). The reporter then sends the appropriate
1686  * Stub unused legacy pci ereports at root complex.
1690  * Stub messages that the root complex sends to itself.