Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754723AbdHVHzP (ORCPT ); Tue, 22 Aug 2017 03:55:15 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:4979 "EHLO szxga04-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754591AbdHVHzN (ORCPT ); Tue, 22 Aug 2017 03:55:13 -0400 Date: Tue, 22 Aug 2017 08:54:06 +0100 From: Jonathan Cameron To: Dongjiu Geng CC: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH v5 0/7] Add RAS virtualization support to SEA/SEI notification type Message-ID: <20170822085406.00006e74@huawei.com> In-Reply-To: <1503065517-7920-1-git-send-email-gengdongjiu@huawei.com> References: <1503065517-7920-1-git-send-email-gengdongjiu@huawei.com> Organization: Huawei X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; x86_64-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.206.48.115] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0207.599BE33D.0196,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: ba0f352b3af014d10d1d6fd0d81e0016 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2931 Lines: 74 On Fri, 18 Aug 2017 22:11:50 +0800 Dongjiu Geng wrote: > In the firmware-first RAS solution, corrupt data is detected in a > memory location when guest OS application software executing at EL0 > or guest OS kernel El1 software are reading from the memory. The > memory node records errors in an error record accessible using > system registers. > > Because SCR_EL3.EA is 1, then CPU will trap to El3 firmware, EL3 > firmware records the error to APEI table through reading system > register. > > Because the error was taken from a lower Exception leve, if the leve -> level > exception is SEA/SEI and HCR_EL2.TEA/HCR_EL2.AMO is 1, firmware > sets ESR_EL2/FAR_El to fake a exception trap to EL2, then > transfers to hypervisor. > > Hypervisor calls the momory failure to deal with this error, momory momory -> memory memory failure -> memory failure function? Or callback perhaps? > failure read the APEI table and decide whether it needs to deliver > SIGBUS signal to user space, the advantage of using SIGBUS signal > to notify user space is that it can be compatible Non-Kvm users. Seems like a good description to me. Thanks. Jonathan > > Dongjiu Geng (5): > acpi: apei: Add SEI notification type support for ARMv8 > support user space to query RAS extension feature > arm64: kvm: route synchronous external abort exceptions to el2 > KVM: arm/arm64: Allow get exception syndrome and > arm64: kvm: handle SEI notification and inject virtual SError > > James Morse (1): > KVM: arm64: Save ESR_EL2 on guest SError > > Xie XiuQi (1): > arm64: cpufeature: Detect CPU RAS Extentions > > arch/arm/include/asm/kvm_host.h | 2 ++ > arch/arm/kvm/guest.c | 5 +++ > arch/arm64/Kconfig | 16 ++++++++++ > arch/arm64/include/asm/barrier.h | 1 + > arch/arm64/include/asm/cpucaps.h | 3 +- > arch/arm64/include/asm/kvm_arm.h | 2 ++ > arch/arm64/include/asm/kvm_emulate.h | 17 ++++++++++ > arch/arm64/include/asm/kvm_host.h | 2 ++ > arch/arm64/include/asm/sysreg.h | 5 +++ > arch/arm64/include/asm/system_misc.h | 1 + > arch/arm64/include/uapi/asm/kvm.h | 5 +++ > arch/arm64/kernel/cpufeature.c | 13 ++++++++ > arch/arm64/kernel/process.c | 3 ++ > arch/arm64/kvm/guest.c | 48 +++++++++++++++++++++++++++++ > arch/arm64/kvm/handle_exit.c | 21 +++++++++++-- > arch/arm64/kvm/hyp/switch.c | 29 +++++++++++++++-- > arch/arm64/kvm/reset.c | 3 ++ > arch/arm64/mm/fault.c | 21 +++++++++++-- > drivers/acpi/apei/Kconfig | 15 +++++++++ > drivers/acpi/apei/ghes.c | 60 +++++++++++++++++++++++------------- > include/acpi/ghes.h | 2 +- > include/uapi/linux/kvm.h | 3 ++ > virt/kvm/arm/arm.c | 7 +++++ > 23 files changed, 254 insertions(+), 30 deletions(-) >