Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp214179pxb; Sat, 10 Apr 2021 00:11:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxmQDb5kUd+fkkc7azUOtBlr3UdWO7XJxwyH/T4fy0WK2Nr/4t+BmPNdf+UmeVo6RVKQEA6 X-Received: by 2002:a17:906:4cc6:: with SMTP id q6mr18900162ejt.131.1618038677989; Sat, 10 Apr 2021 00:11:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618038677; cv=none; d=google.com; s=arc-20160816; b=t5tD7IBi+wOwggrYtnCw9DbdtyA9XcOEcE20hJHItzaLKDLCwuQCKS7MIaWgS1MOZV wvQfJ8K/3Z4kPSts9OLxJMrnnASQx5xK9cE4ml6b829CtMBdOlOTChS50pFe0bcee6Yi 4yrNHFVs3+A1ukdxAcYD04wPy70rb91mSMyLUiDdeFG/Ma7ISsm7x8bF861uQjuL+Qld 917mfyJ6BsdVqIzFuUXcj8e6CX3Vczak/nbPD7aCnzT1tYzkm/exZ9XYAQpNGlsQ2pd3 gIAnVQZApIcdqDLVJRf99puU+8WlqCpqX0HnrbLaRHKAuIypflTYQTffAicZjPWghVDr zyyw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject; bh=xHwP7CBvKVOUoxc+iC5EPEDezorH6jniV/1fkuVBDX8=; b=kDeV4WyG4Rbi4dSEbRYm7yh14seUVuhs47Zk8JcZiNIdmsjsdZ2WGQxCy4hDSoYq9B fjn/EWLzLWmregf+Cjix0kM9F+z4GUNUektVnZvAP9+yBHuGjgusYvwZkZi8lEr5njOk enGfYwjeGn1+SbAwcv4DGjcjL8VGZOT77Lbrdw+y6E8uvCgyZyuZp+bmq+yAs34/KTmv 4h2LWZZYz9x1tUjleS0TL5ilDTq42wEUWbWY3iKzQRzBdqt6fuGaYlNdOGgeryYTZwVC oeKwty/QflFcqAfG5rIly2Wa6HHD3y1EsuxN0zqlAxb1fV/0vGF3nhwtzFoemT0RFJUj sSJw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n25si3699319edv.559.2021.04.10.00.10.53; Sat, 10 Apr 2021 00:11:17 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234169AbhDJHKS (ORCPT + 99 others); Sat, 10 Apr 2021 03:10:18 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:16560 "EHLO szxga04-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229537AbhDJHKQ (ORCPT ); Sat, 10 Apr 2021 03:10:16 -0400 Received: from DGGEMS402-HUB.china.huawei.com (unknown [172.30.72.59]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4FHR0H5L6qz17Qw7; Sat, 10 Apr 2021 15:07:43 +0800 (CST) Received: from [127.0.0.1] (10.40.192.162) by DGGEMS402-HUB.china.huawei.com (10.3.19.202) with Microsoft SMTP Server id 14.3.498.0; Sat, 10 Apr 2021 15:09:48 +0800 Subject: Re: [PATCH v5] ACPI / APEI: fix the regression of synchronous external aborts occur in user-mode To: James Morse , Borislav Petkov References: <1607602177-1507-1-git-send-email-tanxiaofei@huawei.com> <94a38a33-a949-3cce-d617-e1476912596e@huawei.com> CC: "Rafael J. Wysocki" , Len Brown , "Rafael J. Wysocki" , Tony Luck , Andrew Morton , Joerg Roedel , Peter Zijlstra , ACPI Devel Maling List , Linux Kernel Mailing List , Linuxarm From: Xiaofei Tan Message-ID: <3648791f-f9c5-858f-cf6e-e5954fad8019@huawei.com> Date: Sat, 10 Apr 2021 15:09:47 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.40.192.162] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi James, Boris a friendly ping.. any comments for this ? On 2021/2/5 20:55, Rafael J. Wysocki wrote: > On Tue, Jan 26, 2021 at 2:32 PM tanxiaofei wrote: >> >> @James >> Hi James, please help to review this patch. Thank you very much. :) > > James, Boris, any comments? > >> On 2020/12/10 20:09, Xiaofei Tan wrote: >>> After the commit 8fcc4ae6faf8 ("arm64: acpi: Make apei_claim_sea() >>> synchronise with APEI's irq work") applied, do_sea() return directly >>> for user-mode if apei_claim_sea() handled any error record. Therefore, >>> each error record reported by the user-mode SEA must be effectively >>> processed in APEI GHES driver. >>> >>> Currently, GHES driver only processes Memory Error Section.(Ignore PCIe >>> Error Section, as it has nothing to do with SEA). It is not enough. >>> Because ARM Processor Error could also be used for SEA in some hardware >>> platforms, such as Kunpeng9xx series. We can't ask them to switch to >>> use Memory Error Section for two reasons: >>> 1)The server was delivered to customers, and it will introduce >>> compatibility issue. >>> 2)It make sense to use ARM Processor Error Section. Because either >>> cache or memory errors could generate SEA when consumed by a processor. >>> >>> Do memory failure handling for ARM Processor Error Section just like >>> for Memory Error Section. >>> >>> Signed-off-by: Xiaofei Tan >>> --- >>> Changes since v4: >>> - 1. Change the patch name from " ACPI / APEI: do memory failure on the >>> physical address reported by ARM processor error section" to this >>> more proper one. >>> - 2. Add a comment in the code to tell why not filter out corrected >>> error in an uncorrected section. >>> >>> Changes since v3: >>> - Print unhandled error following James Morse's advice. >>> >>> Changes since v2: >>> - Updated commit log >>> --- >>> drivers/acpi/apei/ghes.c | 76 +++++++++++++++++++++++++++++++++++++----------- >>> 1 file changed, 59 insertions(+), 17 deletions(-) >>> >>> diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c >>> index fce7ade..0893968 100644 >>> --- a/drivers/acpi/apei/ghes.c >>> +++ b/drivers/acpi/apei/ghes.c >>> @@ -441,28 +441,35 @@ static void ghes_kick_task_work(struct callback_head *head) >>> gen_pool_free(ghes_estatus_pool, (unsigned long)estatus_node, node_len); >>> } >>> >>> -static bool ghes_handle_memory_failure(struct acpi_hest_generic_data *gdata, >>> - int sev) >>> +static bool ghes_do_memory_failure(u64 physical_addr, int flags) >>> { >>> unsigned long pfn; >>> - int flags = -1; >>> - int sec_sev = ghes_severity(gdata->error_severity); >>> - struct cper_sec_mem_err *mem_err = acpi_hest_get_payload(gdata); >>> >>> if (!IS_ENABLED(CONFIG_ACPI_APEI_MEMORY_FAILURE)) >>> return false; >>> >>> - if (!(mem_err->validation_bits & CPER_MEM_VALID_PA)) >>> - return false; >>> - >>> - pfn = mem_err->physical_addr >> PAGE_SHIFT; >>> + pfn = PHYS_PFN(physical_addr); >>> if (!pfn_valid(pfn)) { >>> pr_warn_ratelimited(FW_WARN GHES_PFX >>> "Invalid address in generic error data: %#llx\n", >>> - mem_err->physical_addr); >>> + physical_addr); >>> return false; >>> } >>> >>> + memory_failure_queue(pfn, flags); >>> + return true; >>> +} >>> + >>> +static bool ghes_handle_memory_failure(struct acpi_hest_generic_data *gdata, >>> + int sev) >>> +{ >>> + int flags = -1; >>> + int sec_sev = ghes_severity(gdata->error_severity); >>> + struct cper_sec_mem_err *mem_err = acpi_hest_get_payload(gdata); >>> + >>> + if (!(mem_err->validation_bits & CPER_MEM_VALID_PA)) >>> + return false; >>> + >>> /* iff following two events can be handled properly by now */ >>> if (sec_sev == GHES_SEV_CORRECTED && >>> (gdata->flags & CPER_SEC_ERROR_THRESHOLD_EXCEEDED)) >>> @@ -470,14 +477,51 @@ static bool ghes_handle_memory_failure(struct acpi_hest_generic_data *gdata, >>> if (sev == GHES_SEV_RECOVERABLE && sec_sev == GHES_SEV_RECOVERABLE) >>> flags = 0; >>> >>> - if (flags != -1) { >>> - memory_failure_queue(pfn, flags); >>> - return true; >>> - } >>> + if (flags != -1) >>> + return ghes_do_memory_failure(mem_err->physical_addr, flags); >>> >>> return false; >>> } >>> >>> +static bool ghes_handle_arm_hw_error(struct acpi_hest_generic_data *gdata, int sev) >>> +{ >>> + struct cper_sec_proc_arm *err = acpi_hest_get_payload(gdata); >>> + struct cper_arm_err_info *err_info; >>> + bool queued = false; >>> + int sec_sev, i; >>> + >>> + log_arm_hw_error(err); >>> + >>> + sec_sev = ghes_severity(gdata->error_severity); >>> + if (sev != GHES_SEV_RECOVERABLE || sec_sev != GHES_SEV_RECOVERABLE) >>> + return false; >>> + >>> + err_info = (struct cper_arm_err_info *) (err + 1); >>> + for (i = 0; i < err->err_info_num; i++, err_info++) { >>> + bool is_cache = (err_info->type == CPER_ARM_CACHE_ERROR); >>> + bool has_pa = (err_info->validation_bits & CPER_ARM_INFO_VALID_PHYSICAL_ADDR); >>> + >>> + /* >>> + * The field (err_info->error_info & BIT(26)) is fixed to set to >>> + * 1 in some old firmware of HiSilicon Kunpeng920. We assume that >>> + * firmware won't mix corrected errors in an uncorrected section, >>> + * and don't filter out 'corrected' error here. >>> + */ >>> + if (!is_cache || !has_pa) { >>> + pr_warn_ratelimited(FW_WARN GHES_PFX >>> + "Unhandled processor error type %s\n", >>> + err_info->type < ARRAY_SIZE(cper_proc_error_type_strs) ? >>> + cper_proc_error_type_strs[err_info->type] : "unknown error"); >>> + continue; >>> + } >>> + >>> + if (ghes_do_memory_failure(err_info->physical_fault_addr, 0)) >>> + queued = true; >>> + } >>> + >>> + return queued; >>> +} >>> + >>> /* >>> * PCIe AER errors need to be sent to the AER driver for reporting and >>> * recovery. The GHES severities map to the following AER severities and >>> @@ -605,9 +649,7 @@ static bool ghes_do_proc(struct ghes *ghes, >>> ghes_handle_aer(gdata); >>> } >>> else if (guid_equal(sec_type, &CPER_SEC_PROC_ARM)) { >>> - struct cper_sec_proc_arm *err = acpi_hest_get_payload(gdata); >>> - >>> - log_arm_hw_error(err); >>> + queued = ghes_handle_arm_hw_error(gdata, sev); >>> } else { >>> void *err = acpi_hest_get_payload(gdata); >>> >>> >> > > . >