From: Mark Brown <broonie@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm64: Document requirements for fine grained traps at boot
Date: Mon, 29 Mar 2021 13:25:36 +0100 [thread overview]
Message-ID: <20210329122536.GA5166@sirena.org.uk> (raw)
In-Reply-To: <20210329103126.GE3207@willie-the-truck>
[-- Attachment #1.1: Type: text/plain, Size: 873 bytes --]
On Mon, Mar 29, 2021 at 11:31:27AM +0100, Will Deacon wrote:
> One thing I don't understand about the registers listed here is that we're
> requiring firmware to initialise them when the kernel is entered at EL2. But
> they're *_EL2 registers, so why can't the kernel initialise them itself? The
> fewer dependencies on firmware, the better.
Well, there's nothing stopping us doing both - that's the most robust
thing. Relying on the kernel alone to do this has the old kernels on
new systems issue, and there's always going to be some section of code
running before we manage to go through and enumerate features then reset
the system registers even if we run that code very early. With
something like traps it seems especially relevant, it's more of a "could
affect anything" kind of thing than something where we can initialize
the feature before we start using it.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-29 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 15:49 [PATCH] arm64: Document requirements for fine grained traps at boot Mark Brown
2021-03-26 11:55 ` Catalin Marinas
2021-03-29 10:31 ` Will Deacon
2021-03-29 12:16 ` Catalin Marinas
2021-03-29 12:25 ` Mark Brown [this message]
2021-03-29 17:06 ` Mark Brown
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=20210329122536.GA5166@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=will@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).