Re: [PATCH] KVM: arm64: handle the translation table walk RAS error

2017-11-30 Thread gengdongjiu
On 2017/11/29 21:22, Christoffer Dall wrote: >> table, but it already unmap by host APEI driver, then >> generate stage2 data abort again, so this will lead to dead >> loop. > Why does it lead to a loop? If the host has marked a page as unusable, > shouldn't the guest stage 1 page table be backed

Re: [PATCH] KVM: arm64: handle the translation table walk RAS error

2017-11-29 Thread Christoffer Dall
On Thu, Nov 30, 2017 at 04:48:44AM +0800, Dongjiu Geng wrote: > For the RAS Synchronous External Abort, there are two types. > One is memory access, it will be handled by host APEI driver. > Another is translation table walk, in essence, it is hardware > memory error on stage1 or stage2 page table.

[PATCH] KVM: arm64: handle the translation table walk RAS error

2017-11-29 Thread Dongjiu Geng
For the RAS Synchronous External Abort, there are two types. One is memory access, it will be handled by host APEI driver. Another is translation table walk, in essence, it is hardware memory error on stage1 or stage2 page table. For the guest stage1 translation table error, if host APEI driver ha