Re: [Xen-devel] [PATCH 07/18] xen/arm: Introduce a command line parameter for SErrors/Aborts

2017-03-15 Thread Wei Chen
Hi Stefano, On 2017/3/15 8:45, Stefano Stabellini wrote: > On Mon, 13 Mar 2017, Wei Chen wrote: >> In order to distinguish guest-generated SErrors from hypervisor-generated >> SErrors. We have to place SError checking code in every EL1 -> EL2 paths. > ^ remove . > Ok. >> That will be

Re: [Xen-devel] [PATCH 07/18] xen/arm: Introduce a command line parameter for SErrors/Aborts

2017-03-14 Thread Stefano Stabellini
On Mon, 13 Mar 2017, Wei Chen wrote: > In order to distinguish guest-generated SErrors from hypervisor-generated > SErrors. We have to place SError checking code in every EL1 -> EL2 paths. ^ remove . > That will be an overhead on entries caused by dsb/isb. > > But not all platforms want

[Xen-devel] [PATCH 07/18] xen/arm: Introduce a command line parameter for SErrors/Aborts

2017-03-13 Thread Wei Chen
In order to distinguish guest-generated SErrors from hypervisor-generated SErrors. We have to place SError checking code in every EL1 -> EL2 paths. That will be an overhead on entries caused by dsb/isb. But not all platforms want to categorize the SErrors. For example, a host that is running with