Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp729205ybm; Fri, 29 May 2020 10:43:13 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz6gGxhj+ejt7qlHt4HFqzgirwkPVIaqzwuDdjBtudDZ9HFJRIY/lacDq5TsxVB1w7QMnHG X-Received: by 2002:a17:906:4bc1:: with SMTP id x1mr8301400ejv.13.1590774193690; Fri, 29 May 2020 10:43:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590774193; cv=none; d=google.com; s=arc-20160816; b=LngLlcOkYMcgd1ndqLbpFqeCPXyV0R96J88at+/T7nsB6SGFT56AVv9GPNJ6SAMsLV 25Z5mgxJyeLt5giZkEZi0kFrf9RWzUGRaKIdiP1K1taWC+WetKf1QbAy2x5qk3xC63Gl XUIkBsTn736nxd+Ec/H/1mohWUSnRtJFWdLunA7xBQgyC+AXaXpT81KQwVmPEu6mhhN6 HOaiDticolVYsPI9tdHtrs7q+9+9vdVydJ+BSkDALhzHTXzIpQSDOgp5yXBS2ie7Thtu 5X6W7Pu8ik++raTr6aOyaOD+1wCjaKmVoSWkgkA3U4SP0owLX8kwK+sBEy3yn8oPbzlZ nZcw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=8p9n4PC6JikvGkTaTed4LTlK8V6ktj8/NjBxR8fXnNM=; b=aXOXvgKvUbxH9wJjDARg4JasZ9cZefnKjJ5FGFCeXgNw5INtmbt22FtSx3PLOJr5t8 QlqLkwcPpCdRR88NH1BWUZ+RyMjDPZDW1qA2o0JrGsWcrLXDiSw/3Z05NOKG5nmir3Vg iukT3q/oj21cScHL8xaUq9SCokqodoqAc/vmQpdRH+Fw6H0GRFbDGCVWUwTSs3hX3tNB jxfTGRvSSJpk0NDP+X+9BtCCSlFKoHVSLqjSmrFXsGmdfcJv/Wt21vh3v9yBnPP1caB4 6WYhHwDMjieYEjejCsjKejuXT+5wwjJPzAiKTDqRExd9RoOiGDoLZaZsH96Z3qpsDLMJ 0PFQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t10si1448055eji.323.2020.05.29.10.42.49; Fri, 29 May 2020 10:43:13 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725601AbgE2RlF (ORCPT + 99 others); Fri, 29 May 2020 13:41:05 -0400 Received: from szxga07-in.huawei.com ([45.249.212.35]:59336 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726549AbgE2RlC (ORCPT ); Fri, 29 May 2020 13:41:02 -0400 Received: from DGGEMS402-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 3F377F1FABD7EF8DA97A; Sat, 30 May 2020 01:40:59 +0800 (CST) Received: from DESKTOP-6T4S3DQ.china.huawei.com (10.47.92.215) by DGGEMS402-HUB.china.huawei.com (10.3.19.202) with Microsoft SMTP Server id 14.3.487.0; Sat, 30 May 2020 01:40:48 +0800 From: Shiju Jose To: , , , , , , , , , , , , CC: Shiju Jose , , Subject: [PATCH v8 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors Date: Fri, 29 May 2020 18:38:52 +0100 Message-ID: <20200529173854.2521-1-shiju.jose@huawei.com> X-Mailer: git-send-email 2.26.0.windows.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-Originating-IP: [10.47.92.215] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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