From: Mark Rutland <mark.rutland@arm.com>
To: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: broonie@kernel.org, catalin.marinas@arm.com,
mark.rutland@arm.com, richard.henderson@linaro.org,
tytso@mit.edu, will@kernel.org
Subject: [PATCH 0/4] random/arm64: enable RANDOM_TRUST_CPU for arm64
Date: Mon, 10 Feb 2020 13:00:11 +0000 [thread overview]
Message-ID: <20200210130015.17664-1-mark.rutland@arm.com> (raw)
On arm64 systems some CPUs may have RNG instructions while others do
not, and consequently we cannot generally enable the use of RNG
instructions until all CPUs have been booted (as otherwise we'd have
problems with preemption, etc). This prevents us from seeding the
primary CRNG using the RNG, as this occurs before secondary CPUs are
onlined.
These patches rework the core CRNG intialization code so that the arch
code can (optionally) distinguish boot-time usage from runtime usage of
the arch_get_random_*() functions. This allows arm64 to use the boot
CPU's RNG to seed the primary CRNG, regardless of whether secondary CPUs
support the RNG instructions. Other architectures should see no
functional change as a result of this patches.
Thanks,
Mark.
Mark Rutland (3):
random: split primary/secondary crng init paths
random: add arch_get_random_*long_early()
arm64: add credited/trusted RNG support
Richard Henderson (1):
random: Make RANDOM_TRUST_CPU depend on ARCH_RANDOM
arch/arm64/include/asm/archrandom.h | 14 ++++++++++
drivers/char/Kconfig | 2 +-
drivers/char/random.c | 52 ++++++++++++++++++++++++++++---------
include/linux/random.h | 22 ++++++++++++++++
4 files changed, 77 insertions(+), 13 deletions(-)
--
2.11.0
next reply other threads:[~2020-02-10 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 13:00 Mark Rutland [this message]
2020-02-10 13:00 ` [PATCH 1/4] random: split primary/secondary crng init paths Mark Rutland
2020-02-10 13:00 ` [PATCH 2/4] random: add arch_get_random_*long_early() Mark Rutland
2020-02-10 13:00 ` [PATCH 3/4] arm64: add credited/trusted RNG support Mark Rutland
2020-02-10 13:00 ` [PATCH 4/4] random: Make RANDOM_TRUST_CPU depend on ARCH_RANDOM Mark Rutland
2020-02-26 10:24 ` [PATCH 0/4] random/arm64: enable RANDOM_TRUST_CPU for arm64 Mark Rutland
2020-02-28 4:22 ` Theodore Y. Ts'o
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=20200210130015.17664-1-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.henderson@linaro.org \
--cc=tytso@mit.edu \
--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
all inboxes | Powered by JetHome®