From nobody Tue Oct 28 14:23:55 2025 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 1514439381723944.8615341328194; Wed, 27 Dec 2017 21:36:21 -0800 (PST) Received: from localhost ([::1]:36021 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eUQrU-00038y-Ob for importer@patchew.org; Thu, 28 Dec 2017 00:36:12 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42530) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eUQjc-0004p3-Qg for qemu-devel@nongnu.org; Thu, 28 Dec 2017 00:28:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eUQja-0000RS-Oz for qemu-devel@nongnu.org; Thu, 28 Dec 2017 00:28:04 -0500 Received: from szxga04-in.huawei.com ([45.249.212.190]:2125 helo=huawei.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eUQjV-0000I9-6a; Thu, 28 Dec 2017 00:27:57 -0500 Received: from DGGEMS401-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 3E2B083F97D76; Thu, 28 Dec 2017 13:27:38 +0800 (CST) Received: from linux.huawei.com (10.67.187.203) by DGGEMS401-HUB.china.huawei.com (10.3.19.201) with Microsoft SMTP Server id 14.3.361.1; Thu, 28 Dec 2017 13:27:30 +0800 From: Dongjiu Geng To: , , , , , , , , , , , , , Date: Thu, 28 Dec 2017 13:54:12 +0800 Message-ID: <1514440458-10515-4-git-send-email-gengdongjiu@huawei.com> X-Mailer: git-send-email 1.7.7 In-Reply-To: <1514440458-10515-1-git-send-email-gengdongjiu@huawei.com> References: <1514440458-10515-1-git-send-email-gengdongjiu@huawei.com> MIME-Version: 1.0 X-Originating-IP: [10.67.187.203] X-CFilter-Loop: Reflected X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 45.249.212.190 Subject: [Qemu-devel] [PATCH v14 3/9] docs: APEI GHES generation and CPER record 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: zhengqiang10@huawei.com, huangshaoyu@huawei.com, xuwei5@hisilicon.com, 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 detailed design document Signed-off-by: Dongjiu Geng --- Address Igor's comments to add a doc --- docs/specs/acpi_hest_ghes.txt | 97 +++++++++++++++++++++++++++++++++++++++= ++++ 1 file changed, 97 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..fbfc787 --- /dev/null +++ b/docs/specs/acpi_hest_ghes.txt @@ -0,0 +1,97 @@ +APEI tables generating and CPER record +=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 | +| +--------------------------+ +--------->| |error_block_address1 |-------= ---->| +------------+ +| | ................. | | | +---------------------+ = | | CPER | +| | error_status_address-----+-+ +------->| |error_block_address2 |-------= -+ | | CPER | +| | ................. | | | +---------------------+ = | | | .... | +| | read_ack_register--------+-+ | | | .............. | = | | | CPER | +| | read_ack_preserve | | | +-----------------------+ = | | +------------+ +| | read_ack_write | | | +----->| |error_block_addressN |------+= | | Error Status | ++ +--------------------------+ | | | | +---------------------+ |= | | Data Block 2 | +| | GHES2 | +-+-+----->| |read_ack_register1 | |= +-->| +------------+ ++ +--------------------------+ | | | +---------------------+ |= | | CPER | +| | ................. | | | +--->| |read_ack_register2 | |= | | CPER | +| | error_status_address-----+---+ | | | +---------------------+ |= | | .... | +| | ................. | | | | | ............. | |= | | CPER | +| | read_ack_register--------+-----+-+ | +---------------------+ |= +-+------------+ +| | read_ack_preserve | | +->| |read_ack_registerN | |= | |.......... | +| | 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 Block 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 + entries, the size for each entry is 4096(0x1000) 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", the firmware already + allocates the memory for it, 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_erro= rs" + blob. + +(6) QEMU generates N ADD_POINTER commands, which patch address in the + "read_ack_register" fields of the HEST table with a pointer to the + corresponding "address registers" in the downloaded "etc/hardware_erro= rs" blob. + +(7) QEMU generates N ADD_POINTER commands for the firmware, which patch + address in the " error_block_address" fields with a pointer to the + respective "Error Status Data Block" in the downloaded "etc/hardware_e= rrors" + blob. + +(8) QEMU Defines a third and write-only fw_cfg blob which is called + "etc/hardware_errors_addr". Through that blob, the firmware can send b= ack + the guest-side allocation addresses to QEMU. The "etc/hardware_errors_= addr" + blob contains a 8-byte entry. QEMU generates a single WRITE_POINTER co= mmands + for the firmware, the firmware will write back the start address of + "etc/hardware_errors" blob to fw_cfg file "etc/hardware_errors_addr". = Then + Qemu will know the Error Status Data Block for every error source. Eac= h of + Error Status Data Block has fixed size which is 4096(0x1000). + +(9) When QEMU gets SIGBUS from the kernel, QEMU formats the CPER right into + guest memory, and then injects whatever interrupt (or assert whatever = GPIO line) + as a notification which is necessary for notifying the guest. + +(10) This notification (in virtual hardware) will be handled by guest kern= el, + guest APEI driver will read the CPER which is recorded by QEMU and do = the + recovery. --=20 1.8.3.1