From: Wei Chen <Wei.Chen@arm.com>
To: Julien Grall <Julien.Grall@arm.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Kaly Xin <Kaly.Xin@arm.com>, nd <nd@arm.com>,
"sstabellini@kernel.org" <sstabellini@kernel.org>,
Steve Capper <Steve.Capper@arm.com>
Subject: Re: [PATCH v2 08/19] xen/arm: Introduce a command line parameter for SErrors/Aborts
Date: Fri, 31 Mar 2017 05:28:37 +0000 [thread overview]
Message-ID: <HE1PR08MB058757AABDEC7214FEFFDE4A9E370@HE1PR08MB0587.eurprd08.prod.outlook.com> (raw)
In-Reply-To: 26812beb-a7a8-6746-bc94-43beaa46b326@arm.com
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 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.
>
Yes, the options will affect both entries and exits. I would update the
commit message and doc.
> Cheers,
>
--
Regards,
Wei Chen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-31 5:28 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 9:13 [PATCH v2 00/19] Provide a command line option to choose how to handle SErrors Wei Chen
2017-03-30 9:13 ` [PATCH v2 01/19] xen/arm: Save ESR_EL2 to avoid using mismatched value in syndrome check Wei Chen
2017-03-30 13:31 ` Julien Grall
2017-03-31 3:26 ` Wei Chen
2017-03-30 9:13 ` [PATCH v2 02/19] xen/arm: Remove vwfi while setting HCR_EL2 in init_traps Wei Chen
2017-03-30 17:05 ` Julien Grall
2017-03-30 22:29 ` Stefano Stabellini
2017-03-31 5:58 ` Wei Chen
2017-03-31 8:34 ` Julien Grall
2017-03-30 9:13 ` [PATCH v2 03/19] xen/arm: Move parse_vwfi from trap.c to domain.c Wei Chen
2017-03-30 9:13 ` [PATCH v2 04/19] xen/arm: Restore HCR_EL2 register Wei Chen
2017-03-30 17:07 ` Julien Grall
2017-03-30 22:03 ` Stefano Stabellini
2017-03-31 2:10 ` Wei Chen
2017-03-31 8:39 ` Julien Grall
2017-03-31 8:59 ` Wei Chen
2017-03-30 9:13 ` [PATCH v2 05/19] xen/arm: Avoid setting/clearing HCR_RW at every context switch Wei Chen
2017-03-30 17:12 ` Julien Grall
2017-03-30 21:21 ` Stefano Stabellini
2017-03-30 9:13 ` [PATCH v2 06/19] xen/arm: Save HCR_EL2 when a guest took the SError Wei Chen
2017-03-30 9:13 ` [PATCH v2 07/19] xen/arm: Introduce a virtual abort injection helper Wei Chen
2017-03-30 17:20 ` Julien Grall
2017-03-30 21:24 ` Stefano Stabellini
2017-03-31 5:25 ` Wei Chen
2017-03-30 9:13 ` [PATCH v2 08/19] xen/arm: Introduce a command line parameter for SErrors/Aborts Wei Chen
2017-03-30 17:39 ` Julien Grall
2017-03-31 5:28 ` Wei Chen [this message]
2017-03-30 9:13 ` [PATCH v2 09/19] xen/arm: Introduce a initcall to update cpu_hwcaps by serror_op Wei Chen
2017-03-30 17:51 ` Julien Grall
2017-03-30 18:02 ` Julien Grall
2017-03-30 21:28 ` Stefano Stabellini
2017-03-31 8:50 ` Julien Grall
2017-03-30 9:13 ` [PATCH v2 10/19] xen/arm64: Use alternative to skip the check of pending serrors Wei Chen
2017-03-30 9:13 ` [PATCH v2 11/19] xen/arm32: " Wei Chen
2017-03-30 18:06 ` Julien Grall
2017-03-30 21:29 ` Stefano Stabellini
2017-03-31 5:33 ` Wei Chen
2017-03-30 9:13 ` [PATCH v2 12/19] xen/arm: Move macro VABORT_GEN_BY_GUEST to common header Wei Chen
2017-03-30 21:36 ` Stefano Stabellini
2017-03-31 5:35 ` Wei Chen
2017-03-30 9:13 ` [PATCH v2 13/19] xen/arm: Introduce new helpers to handle guest/hyp SErrors Wei Chen
2017-03-30 9:13 ` [PATCH v2 14/19] xen/arm: Replace do_trap_guest_serror with new helpers Wei Chen
2017-03-30 9:13 ` [PATCH v2 15/19] xen/arm: Unmask the Abort/SError bit in the exception entries Wei Chen
2017-03-30 9:13 ` [PATCH v2 16/19] xen/arm: Introduce a helper to synchronize SError Wei Chen
2017-03-30 18:28 ` Julien Grall
2017-03-30 18:32 ` Julien Grall
2017-03-30 18:37 ` Julien Grall
2017-03-31 5:51 ` Wei Chen
2017-03-31 10:55 ` Wei Chen
2017-03-31 11:06 ` Julien Grall
2017-03-31 11:09 ` Wei Chen
2017-03-30 9:13 ` [PATCH v2 17/19] xen/arm: Isolate the SError between the context switch of 2 vCPUs Wei Chen
2017-03-30 21:49 ` Stefano Stabellini
2017-03-30 22:00 ` Julien Grall
2017-03-31 5:52 ` Wei Chen
2017-03-30 9:13 ` [PATCH v2 18/19] xen/arm: Prevent slipping hypervisor SError to guest Wei Chen
2017-03-30 9:13 ` [PATCH v2 19/19] xen/arm: Handle guest external abort as guest SError Wei Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=HE1PR08MB058757AABDEC7214FEFFDE4A9E370@HE1PR08MB0587.eurprd08.prod.outlook.com \
--to=wei.chen@arm.com \
--cc=Julien.Grall@arm.com \
--cc=Kaly.Xin@arm.com \
--cc=Steve.Capper@arm.com \
--cc=nd@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.