All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: Marc Zyngier <maz@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Dave Martin <dave.martin@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	Mark Brown <broonie@kernel.org>
Subject: [PATCH v1 0/3] arm64: Boot requirements clarifications
Date: Mon, 12 Apr 2021 16:19:52 +0100	[thread overview]
Message-ID: <20210412151955.16078-1-broonie@kernel.org> (raw)

This series makes explicit our booting requirements in a number of
areas, mainly the initialisation of optional floating point features.
While no issues have been encountered it seems better to be explict,
particularly given that new extensions frequently require setup from
higher exception levels to be functional so our list of explicit
requirement is tending to become more and more exhaustive creating some
expecation that requirements will be stated clearly.

Due to a collision with my recent FGT series this series is based on top
of arm64/for-next/fgt-boot-init.

Mark Brown (3):
  arm64: Relax booting requirements for configuration of traps
  arm64: Explicitly require that FPSIMD instructions do not trap
  arm64: Explicitly document boot requirements for SVE

 Documentation/arm64/booting.rst | 33 ++++++++++++++++++++++++++++++++-
 1 file changed, 32 insertions(+), 1 deletion(-)


base-commit: 230800cd315cd5e2093e603cf7ee150b7591ce1a
-- 
2.20.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-04-12 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 15:19 Mark Brown [this message]
2021-04-12 15:19 ` [PATCH v1 1/3] arm64: Relax booting requirements for configuration of traps Mark Brown
2021-04-12 15:19 ` [PATCH v1 2/3] arm64: Explicitly require that FPSIMD instructions do not trap Mark Brown
2021-04-12 15:19 ` [PATCH v1 3/3] arm64: Explicitly document boot requirements for SVE Mark Brown
2021-04-30 17:55 ` [PATCH v1 0/3] arm64: Boot requirements clarifications Catalin Marinas

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=20210412151955.16078-1-broonie@kernel.org \
    --to=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=dave.martin@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --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 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.