From: Shiju Jose <shiju.jose@huawei.com>
To: <linux-acpi@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <rjw@rjwysocki.net>,
<helgaas@kernel.org>, <lenb@kernel.org>, <bp@alien8.de>,
<james.morse@arm.com>, <tony.luck@intel.com>,
<gregkh@linuxfoundation.org>, <zhangliguang@linux.alibaba.com>,
<tglx@linutronix.de>
Cc: <linuxarm@huawei.com>, <jonathan.cameron@huawei.com>,
<tanxiaofei@huawei.com>, <yangyicong@hisilicon.com>
Subject: [PATCH v5 0/2] ACPI: APEI: Add support to notify the vendor specific HW errors
Date: Wed, 25 Mar 2020 13:55:03 +0000 [thread overview]
Message-ID: <8aa40a48-39c9-ba6b-ea70-bcb60907a733@huawei.com> (raw)
Presently the vendor drivers are unable to do the recovery for the
vendor specific recoverable HW errors, reported to the APEI driver
in the vendor defined sections, because APEI driver does not support
reporting the same to the vendor drivers.
This patch set
1. add an interface to the APEI driver to enable the vendor
drivers to register the event handling functions for the corresponding
vendor specific HW errors and report the error to the vendor driver.
2. add driver to handle HiSilicon hip08 PCIe controller's errors
which is an example application of the above APEI interface.
Changes:
V5:
1. Fix comments from James Morse.
1.1 Changed the notification method to use the atomic_notifier_chain.
1.2 Add the error handled status for the user space.
V4:
1. Fix for the smatch warning in the PCIe error driver:
warn: should '((((1))) << (9 + i))' be a 64 bit type?
if (err->val_bits & BIT(HISI_PCIE_LOCAL_VALID_ERR_MISC + i))
^^^ This should be BIT_ULL() because it goes up to 9 + 32.
V3:
1. Fix the comments from Bjorn Helgaas.
V2:
1. Changes in the HiSilicon PCIe controller's error handling driver
for the comments from Bjorn Helgaas.
2. Changes in the APEI interface to support reporting the vendor error
for module with multiple devices, but use the same section type.
In the error handler will use socket id/sub module id etc to distinguish
the device.
V1:
1. Fix comments from James Morse.
2. add driver to handle HiSilicon hip08 PCIe controller's errors,
which is an application of the above interface.
Shiju Jose (1):
APEI: Add support to notify the vendor specific HW errors
Yicong Yang (1):
PCI: HIP: Add handling of HiSilicon HIP PCIe controller errors
drivers/acpi/apei/ghes.c | 35 ++-
drivers/pci/controller/Kconfig | 8 +
drivers/pci/controller/Makefile | 1 +
drivers/pci/controller/pcie-hisi-error.c | 357 +++++++++++++++++++++++
drivers/ras/ras.c | 5 +-
include/acpi/ghes.h | 28 ++
include/linux/ras.h | 6 +-
include/ras/ras_event.h | 7 +-
8 files changed, 440 insertions(+), 7 deletions(-)
create mode 100644 drivers/pci/controller/pcie-hisi-error.c
--
2.17.1
next reply other threads:[~2020-03-25 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 13:55 Shiju Jose [this message]
2020-03-25 15:22 ` [PATCH v5 0/2] ACPI: APEI: Add support to notify the vendor specific HW errors Bjorn Helgaas
2020-03-25 16:27 ` Shiju Jose
2020-03-25 18:31 ` Bjorn Helgaas
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=8aa40a48-39c9-ba6b-ea70-bcb60907a733@huawei.com \
--to=shiju.jose@huawei.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=james.morse@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rjw@rjwysocki.net \
--cc=tanxiaofei@huawei.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=yangyicong@hisilicon.com \
--cc=zhangliguang@linux.alibaba.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).