Re: [Xen-devel] [PATCH v2 08/19] xen/arm: Introduce a command line parameter for SErrors/Aborts

2017-03-30 Thread Wei Chen
Hi Julien, On 2017/3/31 1:39, Julien Grall wrote: > Hi Wei, > > On 30/03/17 10:13, 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. >> That will cause overhead on entries due to

Re: [Xen-devel] [PATCH v2 08/19] xen/arm: Introduce a command line parameter for SErrors/Aborts

2017-03-30 Thread Julien Grall
Hi Wei, On 30/03/17 10:13, 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. That will cause overhead on entries due to dsb/isb. However, not all platforms want to categorize

[Xen-devel] [PATCH v2 08/19] xen/arm: Introduce a command line parameter for SErrors/Aborts

2017-03-30 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 cause overhead on entries due to dsb/isb. However, not all platforms want to categorize SErrors. For example, a host that is running with