[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1510343650-23659-1-git-send-email-gengdongjiu@huawei.com>
Date: Sat, 11 Nov 2017 03:54:03 +0800
From: Dongjiu Geng <gengdongjiu@...wei.com>
To: <christoffer.dall@...aro.org>, <marc.zyngier@....com>,
<linux@...linux.org.uk>, <bp@...en8.de>, <rjw@...ysocki.net>,
<james.morse@....com>, <pbonzini@...hat.com>, <rkrcmar@...hat.com>,
<corbet@....net>, <catalin.marinas@....com>, <kvm@...r.kernel.org>,
<linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<kvmarm@...ts.cs.columbia.edu>, <linux-acpi@...r.kernel.org>,
<devel@...ica.org>, <gengdongjiu@...wei.com>,
<huangshaoyu@...wei.com>, <wuquanming@...wei.com>,
<linuxarm@...wei.com>
Subject: [PATCH v8 0/7] Support RAS virtualization in KVM
This series patches mainly do below things:
1. Trap RAS ERR* registers Accesses to EL2 from Non-secure EL1,
KVM will will do a minimum simulation, there registers are simulated
to RAZ/WI in KVM.
2. Route synchronous External Abort exceptions from Non-secure EL0
and EL1 to EL2. When exception EL3 routing is enabled by firmware,
system will trap to EL3 firmware instead of EL2 KVM, then firmware
judges whether El2 routing is enabled, if enabled, jump to EL2 KVM,
otherwise jump to EL1 host kernel.
3. Enable APEI ARv8 SEI notification to parse the CPER records for SError
in the ACPI GHES driver, KVM will call handle_guest_sei() to let ACPI
driver to parse the CPER record for SError which happened in the guest
4. Although we can use APEI driver to handle the guest SError, but not all
system support SEI notification, such as kernel-first. So here KVM will
also classify the Error through Exception Syndrome Register and do different
approaches according to Asynchronous Error Type
5. If the guest SError error is not propagated and not consumed, then KVM return
recoverable error status to user-space, user-space will specify the guest ESR
and inject a virtual SError. For other Asynchronous Error Type, KVM directly
injects virtual SError with IMPLEMENTATION DEFINED ESR or KVM is panic if the
error is fatal. In the RAS extension, guest virtual ESR must be set, because
all-zero means 'RAS error: Uncategorized' instead of 'no valid ISS', so set
this ESR to IMPLEMENTATION DEFINED by default if user space does not specify it.
Dongjiu Geng (5):
acpi: apei: Add SEI notification type support for ARMv8
KVM: arm64: Trap RAS error registers and set HCR_EL2's TERR & TEA
arm64: kvm: Introduce KVM_ARM_SET_SERROR_ESR ioctl
arm64: kvm: Set Virtual SError Exception Syndrome for guest
arm64: kvm: handle SError Interrupt by categorization
James Morse (1):
KVM: arm64: Save ESR_EL2 on guest SError
Xie XiuQi (1):
arm64: cpufeature: Detect CPU RAS Extentions
Documentation/virtual/kvm/api.txt | 11 ++++++
arch/arm/include/asm/kvm_host.h | 1 +
arch/arm/kvm/guest.c | 9 +++++
arch/arm64/Kconfig | 16 +++++++++
arch/arm64/include/asm/barrier.h | 1 +
arch/arm64/include/asm/cpucaps.h | 3 +-
arch/arm64/include/asm/esr.h | 15 ++++++++
arch/arm64/include/asm/kvm_arm.h | 2 ++
arch/arm64/include/asm/kvm_asm.h | 3 ++
arch/arm64/include/asm/kvm_emulate.h | 17 +++++++++
arch/arm64/include/asm/kvm_host.h | 2 ++
arch/arm64/include/asm/sysreg.h | 15 ++++++++
arch/arm64/include/asm/system_misc.h | 1 +
arch/arm64/kernel/cpufeature.c | 13 +++++++
arch/arm64/kernel/process.c | 3 ++
arch/arm64/kvm/guest.c | 14 ++++++++
arch/arm64/kvm/handle_exit.c | 67 +++++++++++++++++++++++++++++++++---
arch/arm64/kvm/hyp/switch.c | 31 +++++++++++++++--
arch/arm64/kvm/inject_fault.c | 13 ++++++-
arch/arm64/kvm/reset.c | 3 ++
arch/arm64/kvm/sys_regs.c | 10 ++++++
arch/arm64/mm/fault.c | 16 +++++++++
drivers/acpi/apei/Kconfig | 15 ++++++++
drivers/acpi/apei/ghes.c | 53 ++++++++++++++++++++++++++++
include/acpi/ghes.h | 1 +
include/uapi/linux/kvm.h | 3 ++
virt/kvm/arm/arm.c | 7 ++++
27 files changed, 336 insertions(+), 9 deletions(-)
--
1.9.1
Powered by blists - more mailing lists