From: Bjorn Helgaas <helgaas@kernel.org>
To: Shiju Jose <shiju.jose@huawei.com>
Cc: linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, rjw@rjwysocki.net, lenb@kernel.org,
bp@alien8.de, james.morse@arm.com, tony.luck@intel.com,
gregkh@linuxfoundation.org, zhangliguang@linux.alibaba.com,
tglx@linutronix.de, linuxarm@huawei.com,
jonathan.cameron@huawei.com, tanxiaofei@huawei.com,
yangyicong@hisilicon.com
Subject: Re: [PATCH v5 0/2] ACPI: APEI: Add support to notify the vendor specific HW errors
Date: Wed, 25 Mar 2020 10:22:20 -0500 [thread overview]
Message-ID: <20200325152220.GA261586@google.com> (raw)
In-Reply-To: <8aa40a48-39c9-ba6b-ea70-bcb60907a733@huawei.com>
1) If you can post things as a series, i.e., with patch 1/2 and patch
2/2 being responses to the 0/2 cover letter, that makes things easier.
It looks like you did this for the previous postings.
2) When applying these, "git am" complained (but they did apply
cleanly):
warning: Patch sent with format=flowed; space at the end of lines might be lost.
Applying: APEI: Add support to notify the vendor specific HW errors
warning: Patch sent with format=flowed; space at the end of lines might be lost.
Applying: PCI: HIP: Add handling of HiSilicon HIP PCIe controller errors
3) drivers/pci/controller/pcie-hisi-error.c should be next to
drivers/pci/controller/dwc/pcie-hisi.c, shouldn't it?
4) Your subject lines don't match the convention. "git log --oneline
drivers/acpi/apei" says:
011077d8fbfe ("APEI: Add support to notify the vendor specific HW errors")
cea79e7e2f24 ("apei/ghes: Do not delay GHES polling")
933ca4e323de ("acpi: Use pr_warn instead of pr_warning")
6abc7622271d ("ACPI / APEI: Release resources if gen_pool_add() fails")
bb100b64763c ("ACPI / APEI: Get rid of NULL_UUID_LE constant")
371b86897d01 ("ACPI / APEI: Remove needless __ghes_check_estatus() calls")
and "git log --oneline --follow drivers/pci/controller/dwc/pcie-hisi*"
says:
6e0832fa432e ("PCI: Collect all native drivers under drivers/pci/controller/")
8cfab3cf63cf ("PCI: Add SPDX GPL-2.0 to replace GPL v2 boilerplate")
5a4751680189 ("PCI: hisi: Constify dw_pcie_host_ops structure")
b379d385bbaa ("PCI: hisi: Remove unused variable driver")
a5f40e8098fe ("PCI: Don't allow unbinding host controllers that aren't prepared")
e313a447e735 ("PCI: hisi: Update PCI config space remap function")
b9c1153f7a9c ("PCI: hisi: Fix DT binding (hisi-pcie-almost-ecam)")
So your subject lines should be:
ACPI / APEI: ...
PCI: hisi: ...
On Wed, Mar 25, 2020 at 01:55:03PM +0000, Shiju Jose wrote:
> 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 prev parent reply other threads:[~2020-03-25 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 13:55 [PATCH v5 0/2] ACPI: APEI: Add support to notify the vendor specific HW errors Shiju Jose
2020-03-25 15:22 ` Bjorn Helgaas [this message]
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=20200325152220.GA261586@google.com \
--to=helgaas@kernel.org \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.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=shiju.jose@huawei.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.