From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Andre Przywara <andre.przywara@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: booting.rst: Clarify EL2 and cover v8-R64
Date: Tue, 15 Feb 2022 23:18:20 +0000 [thread overview]
Message-ID: <164493738020.3934087.8555074967425195921.b4-ty@kernel.org> (raw)
In-Reply-To: <20220107160056.322141-1-andre.przywara@arm.com>
On Fri, 7 Jan 2022 16:00:54 +0000, Andre Przywara wrote:
> clarify the wording of the ARM64 boot protocol requirements, to both
> cater for the introduction of secure EL2 in Armv8.4, but also for the
> addition of the Armv8-R64 architecture branch.
> There is an ARM ARM supplement for v8-R64[1], and also a free model[2].
>
> On top of those clarifications, there are at least two other issues to
> consider for v8-R64 on Linux, I wonder if those should be documented
> somewhere, although I doubt that booting.rst is the right place:
> - Linux clears the NS/NSTable bit in the PTEs. In non-secure world those
> bits are ignored, but when in secure world this means "secure PA".
> That luckily matches the design here (secure-only), but we should avoid
> re-purposing those bits in the future (which would be technically
> possible when running only non-secure).
> - The GIC needs to be implemented using a "single Security state" for
> the Linux GIC driver to work. The model mentioned above defaults to
> a security aware GIC, so needs to be told off using the command line.
> I wonder if this is should be explicitly mentioned somewhere, to avoid
> disappointment by implementors later.
>
> [...]
Applied first patch to arm64 (for-next/docs), thanks!
[1/2] arm64: booting.rst: Clarify on requiring non-secure EL2
https://git.kernel.org/arm64/c/b8ac4ee08d48
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2022-02-15 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 16:00 [PATCH 0/2] arm64: booting.rst: Clarify EL2 and cover v8-R64 Andre Przywara
2022-01-07 16:00 ` [PATCH 1/2] arm64: booting.rst: Clarify on requiring non-secure EL2 Andre Przywara
2022-01-07 16:20 ` Mark Rutland
2022-01-07 16:00 ` [PATCH 2/2] arm64: booting.rst: Cover Armv8-R64 Andre Przywara
2022-01-07 16:27 ` Mark Rutland
2022-02-15 23:18 ` Will Deacon [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=164493738020.3934087.8555074967425195921.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).