Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1732221
| From | gengdongjiu <gengdongjiu@huawei.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v6 5/7] arm64: kvm: route synchronous external abort exceptions to el2 |
| Date | 2017-09-14 13:20 +0200 |
| Message-ID | <upAlA-4iQ-13@gated-at.bofh.it> (permalink) |
| References | <ujpjb-4lO-3@gated-at.bofh.it> <ujpsS-4p8-11@gated-at.bofh.it> <un80q-2yJ-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
James, On 2017/9/8 0:31, James Morse wrote: > KVM already handles external aborts from lower exception levels, no more work > needs doing for TEA. If it is firmware first solution, that is SCR_EL3.EA=1, all SError interrupt and synchronous External Abort exceptions are taken to EL3, so EL3 firmware will handle it, KVM no needs to handle it. HCR_EL3.TEA is only for EL3 to check its value to decide to jump to hypervisor or kernel. > > What happens when a guest access the RAS-Error-Record registers? > > Before we can set HCR_EL2.TERR I think we need to add some minimal emulation for > the registers it traps. Most of them should be RAZ/WI, so it should be > straightforward. (I think KVMs default is to emulate an undef for unknown traps). Today I added the support to do some minimal emulation for RAS-Error-Record registers, thanks for the good suggestion. > > Eventually we will want to back this with a page of memory that lets > Qemu/kvmtool configure what the guest can see. (i.e. the emulated machine's > errors for kernel-first handling.)
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH v6 5/7] arm64: kvm: route synchronous external abort exceptions to el2 gengdongjiu <gengdongjiu@huawei.com> - 2017-09-14 13:20 +0200 Re: [PATCH v6 5/7] arm64: kvm: route synchronous external abort exceptions to el2 James Morse <james.morse@arm.com> - 2017-09-14 14:40 +0200
csiph-web