From patchwork Mon Nov 27 18:49:46 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Dongjiu Geng X-Patchwork-Id: 10076473 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id E1BAA605BD for ; Mon, 27 Nov 2017 10:49:26 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id C2A7428DC8 for ; Mon, 27 Nov 2017 10:49:26 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id B767628DD1; Mon, 27 Nov 2017 10:49:26 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.0 required=2.0 tests=BAYES_00, DATE_IN_FUTURE_06_12, RCVD_IN_DNSWL_HI autolearn=unavailable version=3.3.1 Received: from lists.gnu.org (lists.gnu.org [208.118.235.17]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id 3EA4028DCC for ; Mon, 27 Nov 2017 10:49:26 +0000 (UTC) Received: from localhost ([::1]:60115 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eJGyb-0006UN-Fp for patchwork-qemu-devel@patchwork.kernel.org; Mon, 27 Nov 2017 05:49:25 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58622) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eJGu1-00027e-71 for qemu-devel@nongnu.org; Mon, 27 Nov 2017 05:44:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eJGu0-0007gt-4b for qemu-devel@nongnu.org; Mon, 27 Nov 2017 05:44:41 -0500 Received: from szxga04-in.huawei.com ([45.249.212.190]:2112 helo=huawei.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eJGtt-0007cu-Bn; Mon, 27 Nov 2017 05:44:33 -0500 Received: from DGGEMS411-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 661929F606B19; Mon, 27 Nov 2017 18:44:25 +0800 (CST) Received: from localhost.localdomain (10.143.28.90) by DGGEMS411-HUB.china.huawei.com (10.3.19.211) with Microsoft SMTP Server id 14.3.361.1; Mon, 27 Nov 2017 18:44:17 +0800 From: Dongjiu Geng To: , , , , , , , , , , , , , , , , , , , , Date: Tue, 28 Nov 2017 02:49:46 +0800 Message-ID: <1511808595-24158-4-git-send-email-gengdongjiu@huawei.com> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1511808595-24158-1-git-send-email-gengdongjiu@huawei.com> References: <1511808595-24158-1-git-send-email-gengdongjiu@huawei.com> MIME-Version: 1.0 X-Originating-IP: [10.143.28.90] 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 v13 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: , Errors-To: qemu-devel-bounces+patchwork-qemu-devel=patchwork.kernel.org@nongnu.org Sender: "Qemu-devel" X-Virus-Scanned: ClamAV using ClamSMTP Add APEI/GHES description document Signed-off-by: Dongjiu Geng --- Address Igor's comments to add a doc --- docs/specs/acpi_hest_ghes.txt | 96 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 96 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..df28757 --- /dev/null +++ b/docs/specs/acpi_hest_ghes.txt @@ -0,0 +1,96 @@ +Generating APEI tables and record CPER +============================= + +Copyright (C) 2017 HuaWei Corporation. + +Design Details: +------------------- + + etc/acpi/tables etc/hardware_errors + ==================== ========================================== ++ +--------------------------+ +------------------+ +| | 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_errors_addr". + Through that blob, the firmware can send back the guest-side allocation 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 write the start + address of status address register back to fw_cfg file "etc/hardware_errors_addr". + Then Qemu will know the Error Status Data Block for every error source. Each of Error + Status Data Block has fixed size which is 0x1000. + +(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 line) 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.