From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: AB8JxZq4XvlTZ286KY+kqCPrrcDmU785/TME72v6wHJXC5xaY8+cU0km3rSgMCCf6fXVkLX66xMm ARC-Seal: i=1; a=rsa-sha256; t=1525323846; cv=none; d=google.com; s=arc-20160816; b=Mm3bwmv17ro1Gk2iEF2+HB6bfgQVdAS7zFo1Z7Pz4IdJK6Vq70XSIvh5TQVtn3T93O rCQdsgTuejDYwVzFa6pDhDwFHR2JiFqagoeSBty1eyBtEcYmti0gl2hG+a+MwQKAdGVQ 0pVemRloKhImRZOy7at0iaZA87xfjOtq7T1LVY2iN/xSzFBVOd7wKNIF7NAOP2KW+deb XeTmTdQOPUjrWaMD+AxC/ARWgexv80UAT+M9NlA7YPccZxrFPCNbG5wWwAwy3pqQfOvg l/fEpAkh7Z2z/RkajhHdR0Objy7t68lSn/9P6X4TJctZ9g5BDC37A7j2Yk9LDOlaVWIc LcDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=references:in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=0RMJqL3Uz9nuAK6QtHNgOVgYQ8l8aRRhaV+xXnIIR6g=; b=D7VlJWzyjn2lhPV8o0C9Xp7BZS86BKqoM31Ml9Thb6kAOsIUWORBRlC3bo6JfTtKYV NFQK5woC0J/NI8Hj6kTpqtF+BQIuDb3mWLYttHmaXwBClzVq088qlQQoZg3gpE1vVvBV WV+4pB5hkehhu9egC12Fi0ItImoes1k8gJjKxdj96TVL5nkxnfGJZq0yv5S9avNCbBl6 sJcNKUZRHL1a94jMbf08tckEtpjsrOF6ttWzY1MP8s9mSFd83/cIWRYgYFdjD0jP8L7/ dxP3PJa4OWeHKCbEXD0ZKoOERpBm7h0gctOlAMliI7kxQiGaXhy8LfUuvd+2Rkj9pFGb +I+Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of poza@qualcomm.com designates 65.197.215.72 as permitted sender) smtp.mailfrom=poza@qualcomm.com Authentication-Results: mx.google.com; spf=pass (google.com: domain of poza@qualcomm.com designates 65.197.215.72 as permitted sender) smtp.mailfrom=poza@qualcomm.com X-IronPort-AV: E=Sophos;i="5.49,356,1520924400"; d="scan'208";a="126361295" X-IronPort-AV: E=McAfee;i="5900,7806,8881"; a="152473227" From: Oza Pawandeep To: Bjorn Helgaas , Philippe Ombredanne , Thomas Gleixner , Greg Kroah-Hartman , Kate Stewart , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Dongdong Liu , Keith Busch , Wei Zhang , Sinan Kaya , Timur Tabi Cc: Oza Pawandeep Subject: [PATCH v15 2/9] pci-error-recovery: Add AER_FATAL handling Date: Thu, 3 May 2018 01:03:51 -0400 Message-Id: <1525323838-1735-3-git-send-email-poza@codeaurora.org> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1525323838-1735-1-git-send-email-poza@codeaurora.org> References: <1525323838-1735-1-git-send-email-poza@codeaurora.org> X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: =?utf-8?q?1599417977816685243?= X-GMAIL-MSGID: =?utf-8?q?1599417977816685243?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: It adds description on AER_FATAL error handling. Signed-off-by: Oza Pawandeep diff --git a/Documentation/PCI/pci-error-recovery.txt b/Documentation/PCI/pci-error-recovery.txt index 0b6bb3e..688b691 100644 --- a/Documentation/PCI/pci-error-recovery.txt +++ b/Documentation/PCI/pci-error-recovery.txt @@ -110,7 +110,7 @@ The actual steps taken by a platform to recover from a PCI error event will be platform-dependent, but will follow the general sequence described below. -STEP 0: Error Event +STEP 0: Error Event: ERR_NONFATAL ------------------- A PCI bus error is detected by the PCI hardware. On powerpc, the slot is isolated, in that all I/O is blocked: all reads return 0xffffffff, @@ -228,13 +228,7 @@ proceeds to either STEP3 (Link Reset) or to STEP 5 (Resume Operations). If any driver returned PCI_ERS_RESULT_NEED_RESET, then the platform proceeds to STEP 4 (Slot Reset) -STEP 3: Link Reset ------------------- -The platform resets the link. This is a PCI-Express specific step -and is done whenever a fatal error has been detected that can be -"solved" by resetting the link. - -STEP 4: Slot Reset +STEP 3: Slot Reset ------------------ In response to a return value of PCI_ERS_RESULT_NEED_RESET, the @@ -320,7 +314,7 @@ Failure). >>> However, it probably should. -STEP 5: Resume Operations +STEP 4: Resume Operations ------------------------- The platform will call the resume() callback on all affected device drivers if all drivers on the segment have returned @@ -332,7 +326,7 @@ a result code. At this point, if a new error happens, the platform will restart a new error recovery sequence. -STEP 6: Permanent Failure +STEP 5: Permanent Failure ------------------------- A "permanent failure" has occurred, and the platform cannot recover the device. The platform will call error_detected() with a @@ -355,6 +349,27 @@ errors. See the discussion in powerpc/eeh-pci-error-recovery.txt for additional detail on real-life experience of the causes of software errors. +STEP 0: Error Event: ERR_FATAL +------------------- +PCI bus error is detected by the PCI hardware. On powerpc, the slot is +isolated, in that all I/O is blocked: all reads return 0xffffffff, all +writes are ignored. + +STEP 1: Remove devices +-------------------- +Platform removes the devices depending on the error agent, it could be +this port for all subordinates or upstream component (likely downstream +port) + +STEP 2: Reset link +-------------------- +The platform resets the link. This is a PCI-Express specific step and is +done whenever a fatal error has been detected that can be "solved" by +resetting the link. + +STEP 3: Re-enumerate the devices +-------------------- +Initiates the re-enumeration. Conclusion; General Remarks --------------------------- -- 2.7.4