From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 35FC0C433E0 for ; Fri, 29 May 2020 20:05:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1A3002074D for ; Fri, 29 May 2020 20:05:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727106AbgE2UFO convert rfc822-to-8bit (ORCPT ); Fri, 29 May 2020 16:05:14 -0400 Received: from lhrrgout.huawei.com ([185.176.76.210]:2258 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726926AbgE2UFN (ORCPT ); Fri, 29 May 2020 16:05:13 -0400 Received: from lhreml715-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 9206CE851D406A4F47D9; Fri, 29 May 2020 21:05:11 +0100 (IST) Received: from lhreml715-chm.china.huawei.com (10.201.108.66) by lhreml715-chm.china.huawei.com (10.201.108.66) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 29 May 2020 21:05:11 +0100 Received: from lhreml715-chm.china.huawei.com ([10.201.108.66]) by lhreml715-chm.china.huawei.com ([10.201.108.66]) with mapi id 15.01.1913.007; Fri, 29 May 2020 21:05:11 +0100 From: Shiju Jose To: "linux-acpi@vger.kernel.org" , "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "rjw@rjwysocki.net" , "bp@alien8.de" , "james.morse@arm.com" , "helgaas@kernel.org" , "lenb@kernel.org" , "tony.luck@intel.com" , "dan.carpenter@oracle.com" , "gregkh@linuxfoundation.org" , "zhangliguang@linux.alibaba.com" , "tglx@linutronix.de" CC: Linuxarm , yangyicong Subject: RE: [PATCH v8 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors Thread-Topic: [PATCH v8 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors Thread-Index: AQHWNeBR/m4tj2cJW0qFvUY6/34P2qi/fFmg Date: Fri, 29 May 2020 20:05:10 +0000 Message-ID: <78a6dfbe246b4dbbbdd9534f87638f86@huawei.com> References: <20200529173854.2521-1-shiju.jose@huawei.com> In-Reply-To: <20200529173854.2521-1-shiju.jose@huawei.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.47.91.30] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-CFilter-Loop: Reflected Sender: linux-acpi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org Please ignore this patch set. Resending soon. Thanks, Shiju >-----Original Message----- >From: Shiju Jose >Sent: 29 May 2020 18:39 >To: linux-acpi@vger.kernel.org; linux-pci@vger.kernel.org; linux- >kernel@vger.kernel.org; rjw@rjwysocki.net; bp@alien8.de; >james.morse@arm.com; helgaas@kernel.org; lenb@kernel.org; >tony.luck@intel.com; dan.carpenter@oracle.com; >gregkh@linuxfoundation.org; zhangliguang@linux.alibaba.com; >tglx@linutronix.de >Cc: Shiju Jose ; Linuxarm ; >yangyicong >Subject: [PATCH v8 0/2] ACPI / APEI: Add support to notify the vendor >specific HW errors > >Presently the vendor drivers are unable to do the recovery for the vendor >specific recoverable HW errors because APEI driver does not support >reporting the error to the vendor drivers. > >patch set >1. add new interface to the APEI driver for reporting the > vendor specific non-fatal HW errors to the drivers. > >2. add driver to handle HiSilicon hip PCIe controller's errors. > >V8: >1. Removed reporting the standard errors through the interface > because of the conflict with the changes in the > memory error handling path. >2. Fix comments by Dan Carpenter. > >V7: >1. Add changes in the APEI driver suggested by Borislav Petkov, for > queuing up all the non-fatal HW errors to the work queue and > notify the registered kernel drivers from the bottom half using > blocking notifier, common interface for both standard and > vendor-spcific errors. >2. Fix for further feedbacks in v5 HIP PCIe error handler driver > by Bjorn Helgaas. > >V6: >1. Fix few changes in the patch subject line suggested by Bjorn Helgaas. > >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 following smatch warning in the PCIe error driver, > reported by kbuild test robot: > 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): > ACPI / 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 | 126 ++++++++- > drivers/pci/controller/Kconfig | 8 + > drivers/pci/controller/Makefile | 1 + > drivers/pci/controller/pcie-hisi-error.c | 321 +++++++++++++++++++++++ > include/acpi/ghes.h | 28 ++ > 5 files changed, 483 insertions(+), 1 deletion(-) create mode 100644 >drivers/pci/controller/pcie-hisi-error.c > >-- >2.17.1 >