From patchwork Tue Nov 12 16:52:20 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Jonathan Cameron X-Patchwork-Id: 179234 Delivered-To: patch@linaro.org Received: by 2002:ac9:3c86:0:0:0:0:0 with SMTP id w6csp8004448ocf; Tue, 12 Nov 2019 08:55:37 -0800 (PST) X-Google-Smtp-Source: APXvYqzck6pnkcV8KDQ5ibcOzE4EngPguvjA9wySMGLUWMQNI6tbAjppaMaTb0gm4hmKeyGTrFk6 X-Received: by 2002:a50:da4b:: with SMTP id a11mr33603671edk.17.1573577737625; Tue, 12 Nov 2019 08:55:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573577737; cv=none; d=google.com; s=arc-20160816; b=LmusjnU6i/F1L1mL7aPog5Zzybw3r8Lemi8+i6KIfcnMChAxDcBgLq2cgQJIUbXfFE p82cfxXjidHcP8cptsEsOfs3MJT0WxgBIRneAuMsFplS4KiUXFjEpFbWlYRxdUABHsY4 c+DjJMIhmz+JzkLW9PVQ/cYMuk+ZqZDqpAyorOD4bae8hCKNPCSVisPArSiK0SkaW1bI gDAaUTiyDuDhlLB2ytb18/UdB2NDNt2OXQ8qtQ5vf4zZzwqlKLTZk3yQSwGeCp7KTC/F WpmUbFwrmgm6bG1egmF8aHwz7XoycEd7iMxkyoBoppanYUabTV+clFWdAD9jmCyGHQyB SPRQ== 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=uep7aIGvg2vo5Njh4ZAvq+XsseN48ZBkWsdRtoKmGvA=; b=ng4mbS6qwbeVZ+s7RpG3D9mXpmN+9OL+ilQrMrw87NguuFj2V5NM19YZbIxwsSDB0J BZYjpsHYtnFHEky53OH61B4k+59XZEkX66jHaXqT58llxYBpPPmSiTXoNdsoYZTmUpZT UTaaNZZmExbJ/u2oOXCYRF/4ingTZlnorQhGf2IUAiPeDQHxk67xIYiBrIwczdZyRnZP ichp7orIyNkDhadXqGcsUcCnFhQRrcXmJvDgXHwcqsHz3bdaajJyiECu2eseFtWl4rKK Srq59E64ZhAD/IMG4fPGsfOH7ar3Bo+WS8N91+6ogkYzJRlJTg8RR9+2EdB3w5a62z8J KcGA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-efi-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-efi-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id gq14si335679ejb.190.2019.11.12.08.55.37; Tue, 12 Nov 2019 08:55:37 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-efi-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-efi-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-efi-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726008AbfKLQzh (ORCPT + 3 others); Tue, 12 Nov 2019 11:55:37 -0500 Received: from szxga04-in.huawei.com ([45.249.212.190]:6644 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727338AbfKLQxa (ORCPT ); Tue, 12 Nov 2019 11:53:30 -0500 Received: from DGGEMS411-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 5A0FB9FBD9FFCB61864F; Wed, 13 Nov 2019 00:53:23 +0800 (CST) Received: from lhrphicprd00229.huawei.com (10.123.41.22) by DGGEMS411-HUB.china.huawei.com (10.3.19.211) with Microsoft SMTP Server id 14.3.439.0; Wed, 13 Nov 2019 00:53:14 +0800 From: Jonathan Cameron To: , , , Borislav Petkov , "Mauro Carvalho Chehab" , CC: , , , , , Thanu Rangarajan , Jonathan Cameron Subject: [PATCH v3 0/6] CCIX Protocol error reporting. Date: Wed, 13 Nov 2019 00:52:20 +0800 Message-ID: <20191112165226.106107-1-Jonathan.Cameron@huawei.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 X-Originating-IP: [10.123.41.22] X-CFilter-Loop: Reflected Sender: linux-efi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-efi@vger.kernel.org Changes since V2: Dropped the legal boiler plate from the cover letter. The CCIX consortium have agreed that a simple tradmark statement is sufficient which I have put in the cper-ccix.c file and here. The CCIX® trademark and CCIX trade name are owned solely by CCIX CONSORTIUM, INC. and all rights are reserved therein. Changes since V1: Addressed comments from James Morse - Dropped kernel logging of vendor data. We just push it to the tracepoints. - Tidied up this cover letter and added information to address questions raised. Includes removing questions where James and I agreed ;) Note, this initial series attempts no 'handling' of errors. That will follow later. EFI 2.8 defines a new CPER record Appendix N for CCIX Protocol Error Records (PER). www.uefi.org These include Protocol Error Record logs which are defined in the CCIX 1.0 Base Specification www.ccixconsortium.com. A public evaluation version is now available. Handling of coherency protocol errors is complex and how Linux does this will take some time to evolve. For now, fatal errors are handled via the usual means and everything else is reported. There are 6 types of error defined, covering: * Memory errors * Cache errors * Address translation unit errors * CCIX port errors * CCIX link errors * Agent internal errors. These errors are concerned (mostly) wth things happening in the CCIX protocol layer. They are parallel to AER errors which should be only concerned with the PCIe layer (which is underneath CCIX). The ATS errors break this rule slightly. You may get an error occurring that results in problems at both layers of the protocol stack and hence have to handle AER and PER errors simultaneously. Some of these errors can 'almost' be mapped onto standard existing error types but only at the loss of information specific to CCIX such as where in the topology they occurred. The set includes tracepoints to report the errors to RAS Daemon and a patch set for RAS Daemon will follow shortly. Several design decisions that people may disagree with. 1. Reporting of vendor data. We have little choice but to do this via a dynamic array as these blocks can take arbitrary size. I had hoped no one would actually use these given the odd mismatch between a standard error structure and non standard element, but there are already designs out there that do use it. James suggested that it made sense to put these in the tracepoints, but we shouldn't spam the kernel log with them (done in V2). 2. The trade off between explicit tracepoint fields, on which we might want to filter in kernel, and the simplicity of a blob. I have gone for having the whole of the block specific to the PER error type in an opaque blob. The key elements that may be filtered on are the physical address and the source and component fields which allow you to identify faulty devices. Note that you have to know how the devices were enumerated to be able to do so. 3. Defined 6 new tracepoints rather than cramming everything into one. * They are all defined by the CCIX specification as independent error classes. * Many of them can only be generated by particular types of agent. * The handling required will vary widely depending on types. In the kernel some map cleanly onto existing handling. Keeping the whole flow separate will aide this. They vary by a similar amount in scope to the RAS errors found on an existing system which have independent tracepoints. * Separating them out allows for filtering on the tracepoints by elements that are not shared between them. * Muxing the lot into one record type can lead to ugly code both in kernel and in userspace. Rasdaemon patches posted. https://patchwork.kernel.org/cover/11116735/ Jonathan Cameron (6): efi / ras: CCIX Memory error reporting efi / ras: CCIX Cache error reporting efi / ras: CCIX Address Translation Cache error reporting efi / ras: CCIX Port error reporting efi / ras: CCIX Link error reporting efi / ras: CCIX Agent internal error reporting drivers/acpi/apei/Kconfig | 8 + drivers/acpi/apei/ghes.c | 59 ++ drivers/firmware/efi/Kconfig | 5 + drivers/firmware/efi/Makefile | 1 + drivers/firmware/efi/cper-ccix.c | 919 +++++++++++++++++++++++++++++++ drivers/firmware/efi/cper.c | 6 + include/linux/cper.h | 333 +++++++++++ include/ras/ras_event.h | 405 ++++++++++++++ 8 files changed, 1736 insertions(+) create mode 100644 drivers/firmware/efi/cper-ccix.c -- 2.20.1