Hi Marc,
On 31/10/17 05:47, Marc Zyngier wrote:
> On Tue, Oct 31 2017 at 4:26:01 am GMT, Marc Zyngier
> wrote:
>> On Thu, Oct 19 2017 at 4:58:03 pm BST, James Morse
>> wrote:
>>> When we exit a guest due to an SError the vcpu fault info isn't updated
>>> with the ESR. Today this is only done
On Tue, Oct 31 2017 at 4:26:01 am GMT, Marc Zyngier
wrote:
> On Thu, Oct 19 2017 at 4:58:03 pm BST, James Morse
> wrote:
>> When we exit a guest due to an SError the vcpu fault info isn't updated
>> with the ESR. Today this is only done for traps.
>>
>> The v8.2 RAS Extensions define ISS valu
On Thu, Oct 19 2017 at 4:58:03 pm BST, James Morse wrote:
> When we exit a guest due to an SError the vcpu fault info isn't updated
> with the ESR. Today this is only done for traps.
>
> The v8.2 RAS Extensions define ISS values for SError. Update the vcpu's
> fault_info with the ESR on SError so
When we exit a guest due to an SError the vcpu fault info isn't updated
with the ESR. Today this is only done for traps.
The v8.2 RAS Extensions define ISS values for SError. Update the vcpu's
fault_info with the ESR on SError so that handle_exit() can determine
if this was a RAS SError and decode
