From nobody Tue Feb 10 20:48:23 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zoho.com: domain of gnu.org designates 208.118.235.17 as permitted sender) client-ip=208.118.235.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Authentication-Results: mx.zohomail.com; spf=pass (zoho.com: domain of gnu.org designates 208.118.235.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org Return-Path: Received: from lists.gnu.org (208.118.235.17 [208.118.235.17]) by mx.zohomail.com with SMTPS id 1511260472586443.629058746469; Tue, 21 Nov 2017 02:34:32 -0800 (PST) Received: from localhost ([::1]:33527 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eH5sl-0002K5-10 for importer@patchew.org; Tue, 21 Nov 2017 05:34:23 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59887) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eH5qg-0001Cq-Ae for qemu-devel@nongnu.org; Tue, 21 Nov 2017 05:32:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eH5qf-0005eG-3c for qemu-devel@nongnu.org; Tue, 21 Nov 2017 05:32:14 -0500 Received: from szxga04-in.huawei.com ([45.249.212.190]:2799) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1eH5qb-0005dF-JJ; Tue, 21 Nov 2017 05:32:10 -0500 Received: from 172.30.72.58 (EHLO DGGEMS402-HUB.china.huawei.com) ([172.30.72.58]) by dggrg04-dlp.huawei.com (MOS 4.4.6-GA FastPath queued) with ESMTP id DLG39780; Tue, 21 Nov 2017 18:31:41 +0800 (CST) Received: from localhost.localdomain (10.143.28.90) by DGGEMS402-HUB.china.huawei.com (10.3.19.202) with Microsoft SMTP Server id 14.3.361.1; Tue, 21 Nov 2017 18:31:32 +0800 From: Dongjiu Geng To: , , , , , , , , , , , , , , , , , , , , , , Date: Wed, 22 Nov 2017 02:37:05 +0800 Message-ID: <1511289434-1551-4-git-send-email-gengdongjiu@huawei.com> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1511289434-1551-1-git-send-email-gengdongjiu@huawei.com> References: <1511289434-1551-1-git-send-email-gengdongjiu@huawei.com> MIME-Version: 1.0 X-Originating-IP: [10.143.28.90] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.5A14008E.0119, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2014-11-16 11:51:01, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 06cbcd1f3a8248c462940eb722398f91 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] [fuzzy] X-Received-From: 45.249.212.190 Subject: [Qemu-devel] [PATCH RESEND v12 03/12] docs: APEI GHES generation description X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: gengdongjiu@huawei.com Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: "Qemu-devel" X-ZohoMail: RSF_0 Z_629925259 SPT_0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Add APEI/GHES description document Signed-off-by: Dongjiu Geng --- Address Igor's comments to add a doc --- docs/specs/acpi_hest_ghes.txt | 98 +++++++++++++++++++++++++++++++++++++++= ++++ 1 file changed, 98 insertions(+) create mode 100644 docs/specs/acpi_hest_ghes.txt diff --git a/docs/specs/acpi_hest_ghes.txt b/docs/specs/acpi_hest_ghes.txt new file mode 100644 index 0000000..816d7b9 --- /dev/null +++ b/docs/specs/acpi_hest_ghes.txt @@ -0,0 +1,98 @@ +Generating APEI tables and record CPER +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D + +Copyright (C) 2017 HuaWei Corporation. + +Design Details: +------------------- + + etc/acpi/tables etc/hardware_errors + =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ++ +--------------------------+ +------------------+ +| | HEST | | address | = +--------------+ +| +--------------------------+ | registers | = | Error Status | +| | GHES1 | | +----------------+ = | Data Block 1 | +| +--------------------------+ +--------->| |status_address1 |------------= ->| +------------+ +| | ................. | | | +----------------+ = | | CPER | +| | error_status_address-----+-+ +------->| |status_address2 |----------+ = | | CPER | +| | ................. | | | +----------------+ | = | | .... | +| | read_ack_register--------+-+ | | ............. | | = | | CPER | +| | read_ack_preserve | | | +------------------+ | = | +------------+ +| | read_ack_write | | | +----->| |status_addressN |--------+ | = | Error Status | ++ +--------------------------+ | | | | +----------------+ | | = | Data Block 2 | +| | GHES2 | +-+-+----->| | ack_value1 | | +-= ->| +------------+ ++ +--------------------------+ | | | +----------------+ | = | | CPER | +| | ................. | | | +--->| | ack_value2 | | = | | CPER | +| | error_status_address-----+---+ | | | +----------------+ | = | | .... | +| | ................. | | | | | ............. | | = | | CPER | +| | read_ack_register--------+-----+-+ | +----------------+ | = +-+------------+ +| | read_ack_preserve | | +->| | ack_valueN | | = | |.......... | +| | read_ack_write | | | | +----------------+ | = | +------------+ ++ +--------------------------| | | | = | Error Status | +| | ............... | | | | = | Data Block N | ++ +--------------------------+ | | +---= ->| +------------+ +| | GHESN | | | = | | CPER | ++ +--------------------------+ | | = | | CPER | +| | ................. | | | = | | .... | +| | error_status_address-----+-----+ | = | | CPER | +| | ................. | | = +-+------------+ +| | read_ack_register--------+---------+ +| | read_ack_preserve | +| | read_ack_write | ++ +--------------------------+ + +(1) QEMU generates the ACPI HEST table. This table goes in the current + "etc/acpi/tables" fw_cfg blob. Each error source has different + notification type. + +(2) A new fw_cfg blob called "etc/hardware_errors" is introduced. QEMU + also need to populate this blob. The "etc/hardwre_errors" fw_cfg blob = contains + one address registers table and one Error Status Data Block table, all + of which are pre-allocated. + +(3) The address registers table contains N Error Status Address entries + and N Read Ack Address entries, the size for each entry is 8-byte. The + Error Status Data Block table contains N Error Status Data Block entry, + the size for each entry is 0x1000(4096) bytes. The total size for + "etc/hardware_errors" fw_cfg blob is (N * 8 * 2 + N * 4096) bytes + +(4) QEMU generates the ACPI linker/loader script for the firmware + +(4a) The HEST table is part of "etc/acpi/tables", which the firmware + already allocates memory for it and downloads, because QEMU already + generates an ALLOCATE linker/loader command for it. + +(4b) QEMU creates another ALLOCATE command for the "etc/hardware_errors" + blob. The firmware allocates memory for this blob, + and downloads it. + +(5) QEMU generates, N ADD_POINTER commands, which patch address in the + "Error Status Address" fields of the HEST table with a pointer to the + corresponding address registers in the downloaded "etc/hardware_errors= " blob. + +(6) QEMU generates N ADD_POINTER commands for the firmware, pointing the + address registers (located in guest memory, in the downloaded + "etc/hardware_errors" blob) to the respective Error Status Data Blocks. + +(7) QEMU Defines a third, write-only fw_cfg blob, called "etc/hardware_err= ors_addr". + Through that blob, the firmware can send back the guest-side allocatio= n addresses + to QEMU. The "etc/hardware_errors_addr" blob contains a 8-byte entry. = QEMU generates + a single WRITE_POINTER commands for the firmware, the firmware will wr= ite the start + address of Error Status Data Block0 back to fw_cfg file "etc/hardware_= errors_addr". + Then Qemu will know the start address of Error Status Data Block0. For= error source K + (0 <=3D K < 2), its address offset is K * 0x1000, because each of Erro= r Status Data Block + has fixed size which is 0x1000. Using this way, QEMU will know the add= ress of each + Error Status Data Block. + +(8) When QEMU gets SIGBUS from the kernel, QEMU format the CPER right into= guest + memory, and then inject whatever interrupt (or assert whatever GPIO li= ne) which is + necessary for notifying the guest. + +(9) This notification (in virtual hardware) can either be handled by the + guest kernel stand-alone, or else the guest kernel can invoke an ACPI + event handler method with it. The ACPI event handler method could + invoke the specific guest kernel driver for error handling via a + Notify() operation. + +For the above design, it would leave the firmware alone after OS boot and = firmware no need +to care about HEST, GHES, CPER. --=20 1.8.3.1