From: Dirk Behme <dirk.behme@de.bosch.com>
To: Julien Grall <julien.grall@arm.com>, xen-devel@lists.xen.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 1/2] xen: arm64: doc: Add the requirement that SCR_EL3.HCE is enabled
Date: Fri, 22 Apr 2016 08:23:41 +0200 [thread overview]
Message-ID: <5719C36D.5060105@de.bosch.com> (raw)
In-Reply-To: <5717826A.1040702@arm.com>
On 20.04.2016 15:21, Julien Grall wrote:
> (CC REST maintainers)
>
> Hello Dirk,
>
> Please CC the relevant maintainers for this patch. You can use
> scripts/get_maintainers.pl for this purpose.
>
> On 19/04/16 06:59, Dirk Behme wrote:
>> On ARM64 Linux the HVC instruction is used to trap into Xen. As this
>> can be set only at EL3, i.e. outside from Xen, document this boot
>> requirement.
>>
>> Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
>> ---
>> docs/misc/arm/booting.txt | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/docs/misc/arm/booting.txt b/docs/misc/arm/booting.txt
>> index 9802e5e..ffc9029 100644
>> --- a/docs/misc/arm/booting.txt
>> +++ b/docs/misc/arm/booting.txt
>> @@ -23,6 +23,10 @@ The exceptions to this on 32-bit ARM are as follows:
>>
>> There are no exception on 64-bit ARM.
>>
>> +On ARM64 Linux it has to be ensured that the Secure Configuration
>> +Register has the HVC instructions enabled at EL1 and above
>> +(SCR_EL3.HCE == 1).
>
> The requirement is the same for ARM32 (SCR.HCE == 1).
>
> I would create a specific section in this documentation to list what the
> firmware should do in EL3 before starting Xen.
Done:
http://lists.xen.org/archives/html/xen-devel/2016-04/msg02687.html
> In addition to this patch, I would add a check in Xen to make sure the
> Hyp calls have been enabled by the firmware.
Hmm, I have to re-read the documentation how to do this in EL2. We can't
read SCR_EL3 in EL2?
Best regards
Dirk
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-22 6:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 5:59 [PATCH 1/2] xen: arm64: doc: Add the requirement that SCR_EL3.HCE is enabled Dirk Behme
2016-04-19 5:59 ` [PATCH 2/2] xen: arm64: doc: Add some details about interrupt handling Dirk Behme
2016-04-20 13:26 ` Julien Grall
2016-04-25 8:56 ` Dirk Behme
2016-04-25 11:06 ` Julien Grall
2016-04-20 13:21 ` [PATCH 1/2] xen: arm64: doc: Add the requirement that SCR_EL3.HCE is enabled Julien Grall
2016-04-22 6:23 ` Dirk Behme [this message]
2016-04-22 9:16 ` Julien Grall
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=5719C36D.5060105@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@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.