From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Dongjiu Geng <gengdongjiu@huawei.com>
Cc: <christoffer.dall@linaro.org>, <marc.zyngier@arm.com>,
<rkrcmar@redhat.com>, <linux@armlinux.org.uk>,
<catalin.marinas@arm.com>, <will.deacon@arm.com>,
<lenb@kernel.org>, <robert.moore@intel.com>, <lv.zheng@intel.com>,
<mark.rutland@arm.com>, <james.morse@arm.com>,
<xiexiuqi@huawei.com>, <cov@codeaurora.org>,
<david.daney@cavium.com>, <suzuki.poulose@arm.com>,
<stefan@hello-penguin.com>, <Dave.Martin@arm.com>,
<kristina.martsenko@arm.com>, <wangkefeng.wang@huawei.com>,
<tbaicar@codeaurora.org>, <ard.biesheuvel@linaro.org>,
<mingo@kernel.org>, <bp@suse.de>, <shiju.jose@huawei.com>,
<zjzhang@codeaurora.org>, <linux-arm-kernel@lists.infradead.org>,
<kvmarm@lists.cs.columbia.edu>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<devel@acpica
Subject: Re: [PATCH v5 0/7] Add RAS virtualization support to SEA/SEI notification type
Date: Tue, 22 Aug 2017 08:54:06 +0100 [thread overview]
Message-ID: <20170822085406.00006e74@huawei.com> (raw)
In-Reply-To: <1503065517-7920-1-git-send-email-gengdongjiu@huawei.com>
On Fri, 18 Aug 2017 22:11:50 +0800
Dongjiu Geng <gengdongjiu@huawei.com> 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(-)
>
next prev parent reply other threads:[~2017-08-22 7:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 14:11 [PATCH v5 0/7] Add RAS virtualization support to SEA/SEI notification type Dongjiu Geng
2017-08-18 14:11 ` [PATCH v5 1/7] arm64: cpufeature: Detect CPU RAS Extentions Dongjiu Geng
2017-08-22 7:54 ` Jonathan Cameron
2017-08-18 14:11 ` [PATCH v5 2/7] KVM: arm64: Save ESR_EL2 on guest SError Dongjiu Geng
2017-08-18 14:11 ` [PATCH v5 3/7] acpi: apei: Add SEI notification type support for ARMv8 Dongjiu Geng
2017-08-22 7:56 ` Jonathan Cameron
2017-08-18 14:11 ` [PATCH v5 4/7] support user space to query RAS extension feature Dongjiu Geng
2017-08-21 21:08 ` Christoffer Dall
2017-08-22 1:20 ` gengdongjiu
2017-08-22 7:56 ` Jonathan Cameron
2017-08-18 14:11 ` [PATCH v5 5/7] arm64: kvm: route synchronous external abort exceptions to el2 Dongjiu Geng
2017-08-18 14:11 ` [PATCH v5 6/7] KVM: arm64: Allow get exception information from userspace Dongjiu Geng
2017-08-22 7:57 ` Jonathan Cameron
2017-08-18 14:11 ` [PATCH v5 7/7] arm64: kvm: handle SEI notification and inject virtual SError Dongjiu Geng
2017-08-22 7:57 ` Jonathan Cameron
2017-08-22 7:54 ` Jonathan Cameron [this message]
2017-08-23 2:01 ` [PATCH v5 0/7] Add RAS virtualization support to SEA/SEI notification type gengdongjiu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170822085406.00006e74@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Dave.Martin@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@suse.de \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=cov@codeaurora.org \
--cc=david.daney@cavium.com \
--cc=devel@acpica \
--cc=gengdongjiu@huawei.com \
--cc=james.morse@arm.com \
--cc=kristina.martsenko@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lv.zheng@intel.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=rkrcmar@redhat.com \
--cc=robert.moore@intel.com \
--cc=shiju.jose@huawei.com \
--cc=stefan@hello-penguin.com \
--cc=suzuki.poulose@arm.com \
--cc=tbaicar@codeaurora.org \
--cc=wangkefeng.wang@huawei.com \
--cc=will.deacon@arm.com \
--cc=xiexiuqi@huawei.com \
--cc=zjzhang@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox