From: Julien Grall <julien.grall@arm.com>
To: Dirk Behme <dirk.behme@de.bosch.com>, xen-devel@lists.xen.org
Cc: Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH 1/2] xen: arm64: doc: Add the requirement that SCR_EL3.HCE is enabled
Date: Fri, 22 Apr 2016 10:16:34 +0100 [thread overview]
Message-ID: <5719EBF2.2070004@arm.com> (raw)
In-Reply-To: <5719C36D.5060105@de.bosch.com>
Hi Dirk,
On 22/04/2016 07:23, Dirk Behme wrote:
> On 20.04.2016 15:21, Julien Grall wrote:
>> 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
Thank you, I will look at it soon.
>
>> 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?
Oh yes. sorry I would have thought the register would be exposed RO to EL2.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-22 9:16 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
2016-04-22 9:16 ` Julien Grall [this message]
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=5719EBF2.2070004@arm.com \
--to=julien.grall@arm.com \
--cc=dirk.behme@de.bosch.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.