From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2FD71C35679 for ; Mon, 24 Feb 2020 08:39:04 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 050BC20661 for ; Mon, 24 Feb 2020 08:39:04 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 050BC20661 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:33090 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j69GZ-0003Jb-5l for qemu-devel@archiver.kernel.org; Mon, 24 Feb 2020 03:39:03 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:57454) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j69Ft-0002RT-P5 for qemu-devel@nongnu.org; Mon, 24 Feb 2020 03:38:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j69Fs-0001CY-PD for qemu-devel@nongnu.org; Mon, 24 Feb 2020 03:38:21 -0500 Received: from szxga06-in.huawei.com ([45.249.212.32]:48640 helo=huawei.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j69Fq-00014d-8l; Mon, 24 Feb 2020 03:38:18 -0500 Received: from DGGEMS406-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id 2F8C1EA6E341EB8B89D9; Mon, 24 Feb 2020 16:38:09 +0800 (CST) Received: from [127.0.0.1] (10.142.68.147) by DGGEMS406-HUB.china.huawei.com (10.3.19.206) with Microsoft SMTP Server id 14.3.439.0; Mon, 24 Feb 2020 16:38:02 +0800 Subject: Re: [PATCH v24 00/10] Add ARMv8 RAS virtualization support in QEMU To: Peter Maydell References: <20200217131248.28273-1-gengdongjiu@huawei.com> From: gengdongjiu Message-ID: Date: Mon, 24 Feb 2020 16:37:44 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.142.68.147] X-CFilter-Loop: Reflected X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 45.249.212.32 X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Fam Zheng , Xiao Guangrong , kvm-devel , "Michael S. Tsirkin" , Marcelo Tosatti , QEMU Developers , Shameerali Kolothum Thodi , Shannon Zhao , Zheng Xiang , qemu-arm , James Morse , Jonathan Cameron , Paolo Bonzini , Richard Henderson , Laszlo Ersek , Igor Mammedov , Eduardo Habkost Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On 2020/2/21 22:09, Peter Maydell wrote: > On Mon, 17 Feb 2020 at 13:10, Dongjiu Geng wrote: >> >> In the ARMv8 platform, the CPU error types includes synchronous external abort(SEA) and SError Interrupt (SEI). If exception happens in guest, host does not know the detailed information of guest, so it is expected that guest can do the recovery. >> For example, if an exception happens in a guest user-space application, host does >> not know which application encounters errors, only guest knows it. >> >> For the ARMv8 SEA/SEI, KVM or host kernel delivers SIGBUS to notify userspace. >> After user space gets the notification, it will record the CPER into guest GHES >> buffer and inject an exception or IRQ to guest. >> >> In the current implementation, if the type of SIGBUS is BUS_MCEERR_AR, we will >> treat it as a synchronous exception, and notify guest with ARMv8 SEA >> notification type after recording CPER into guest. > > Hi; I have reviewed the remaining arm bit of this series (patch 9), > and made some comments on patch 1. Still to be reviewed are > patches 4, 5, 6, 8: I'm going to assume that Michael or Igor > will look at those. Thanks very much for Peter's review. Michael/Igor, hope you can review patches 4, 5, 6, 8, thank you very much in advance. > > thanks > -- PMM > > . >