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

[Julien Grall <julien.grall@xxxxxxx>]

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 SErrors. For example, a host
> that is running with trusted guests. The administrator can confirm that
> all guests that are running on the host will not trigger such SErrors. In
> this user-case, we should provide some options to administrators to avoid
s/user-case/use-case/

> +### serrors (ARM)
> +> `= diverse | forward | panic`
> +
> +> Default: `diverse`
> +
> +This parameter is provided to administrators to determine how the
> +hypervisors handle SErrors.
> +
> +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
s/entries/entries and exits/ I think because none of the options you 
provide will effectively only do dsb/isb on entries.
Cheers,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel