From: Sinan Kaya <okaya@codeaurora.org>
To: Borislav Petkov <bp@suse.de>,
"Baicar, Tyler" <tbaicar@codeaurora.org>,
Tony Luck <tony.luck@intel.com>
Cc: rjw@rjwysocki.net, lenb@kernel.org, will.deacon@arm.com,
james.morse@arm.com, prarit@redhat.com, punit.agrawal@arm.com,
shiju.jose@huawei.com, andriy.shevchenko@linux.intel.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] acpi: apei: call into AER handling regardless of severity
Date: Tue, 29 Aug 2017 18:34:49 -0400 [thread overview]
Message-ID: <0fb1fe1b-207a-93fe-4ac6-b886451e488e@codeaurora.org> (raw)
In-Reply-To: <20170829221932.ojkvr4y6s76hcpkj@pd.tnic>
+linux-pci
On 8/29/2017 6:19 PM, Borislav Petkov wrote:
> if (entry.severity == AER_NONFATAL)
> do_recovery(pdev, entry.severity);
Providing input from PCI perspective only:
PCIe defines the the following error categories:
1. Correctable error
2. Uncorrectable non-fatal errors
3. Uncorrectable fatal errors
The do_recovery function needs to be called for both uncorrectable error
categories. (#2 and #3 above)
How these map to GHES error categories is out of know-how.
Below are references to some of the PCIe error docs:
https://www.kernel.org/doc/Documentation/PCI/pcieaer-howto.txt
https://www.kernel.org/doc/Documentation/PCI/pci-error-recovery.txt
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next parent reply other threads:[~2017-08-29 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1503940314-29526-1-git-send-email-tbaicar@codeaurora.org>
[not found] ` <20170829082055.u3qpwtgyzxjxfvup@pd.tnic>
[not found] ` <9abb2e99-44be-3315-47d9-2689b6c76d79@codeaurora.org>
[not found] ` <20170829221932.ojkvr4y6s76hcpkj@pd.tnic>
2017-08-29 22:34 ` Sinan Kaya [this message]
2017-08-30 10:16 ` [PATCH] acpi: apei: call into AER handling regardless of severity Borislav Petkov
2017-08-30 14:05 ` Sinan Kaya
2017-08-30 15:16 ` Borislav Petkov
2017-08-30 15:31 ` Sinan Kaya
2017-08-30 15:42 ` Baicar, Tyler
2017-08-30 17:14 ` Borislav Petkov
2017-08-30 18:09 ` Baicar, Tyler
2017-08-30 17:02 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0fb1fe1b-207a-93fe-4ac6-b886451e488e@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@suse.de \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=punit.agrawal@arm.com \
--cc=rjw@rjwysocki.net \
--cc=shiju.jose@huawei.com \
--cc=tbaicar@codeaurora.org \
--cc=tony.luck@intel.com \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).