From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, Ard Biesheuvel <ardb@kernel.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
mark.rutland@arm.com, Mark Brown <broonie@kernel.org>,
Andre Przywara <andre.przywara@arm.com>,
jason@zx2c4.com
Subject: Re: [PATCH] arm64: random: implement arch_get_random_int/_long based on RNDR
Date: Tue, 15 Feb 2022 23:18:23 +0000 [thread overview]
Message-ID: <164493759988.3934502.9551696025967062638.b4-ty@kernel.org> (raw)
In-Reply-To: <20220113131239.1610455-1-ardb@kernel.org>
On Thu, 13 Jan 2022 14:12:39 +0100, Ard Biesheuvel wrote:
> When support for RNDR/RNDRRS was introduced, we elected to only
> implement arch_get_random_seed_int/_long(), and back them by RNDR
> instead of RNDRRS. This was needed to prevent potential performance
> and/or starvation issues resulting from the fact that the /dev/random
> driver used to invoke these routines on various hot paths.
>
> These issues have all been addressed now [0] [1], and so we can wire up
> this API more straight-forwardly:
>
> [...]
Applied to arm64 (for-next/rng), thanks!
[1/1] arm64: random: implement arch_get_random_int/_long based on RNDR
https://git.kernel.org/arm64/c/35bde68bba54
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-02-15 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 13:12 [PATCH] arm64: random: implement arch_get_random_int/_long based on RNDR Ard Biesheuvel
2022-01-13 13:39 ` Mark Brown
2022-01-13 13:41 ` Jason A. Donenfeld
2022-01-13 13:49 ` Ard Biesheuvel
2022-01-13 13:52 ` Jason A. Donenfeld
2022-01-14 15:04 ` Andre Przywara
2022-01-14 15:07 ` Andre Przywara
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=164493759988.3934502.9551696025967062638.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=andre.przywara@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jason@zx2c4.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
/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.