From: Richard Henderson <richard.henderson@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-arch@vger.kernel.org, mark.rutland@arm.com,
ard.biesheuvel@linaro.org, catalin.marinas@arm.com,
will@kernel.org, Dave.Martin@arm.com
Subject: Re: [PATCH v2 1/1] arm64: Implement archrandom.h for ARMv8.5-RNG
Date: Tue, 29 Oct 2019 14:24:27 +0100 [thread overview]
Message-ID: <bfda9074-a866-d5d6-7f2a-3d91258a7113@linaro.org> (raw)
In-Reply-To: <20191028203254.7152-2-richard.henderson@linaro.org>
On 10/28/19 9:32 PM, richard.henderson@linaro.org wrote:
> +bool arch_get_random_long(unsigned long *v)
> +{
> + bool ok;
> +
> + preempt_disable_notrace();
> +
> + ok = this_cpu_has_cap(ARM64_HAS_RNG);
> + if (ok) {
> + /*
> + * Reads of RNDR set PSTATE.NZCV to 0b0000 on success,
> + * and set PSTATE.NZCV to 0b0100 otherwise.
> + */
> + asm volatile(
> + __mrs_s("%0", SYS_RNDR_EL0) "\n"
> + " cset %w1, ne\n"
> + : "=r"(*v), "=r"(ok)
> + :
> + : "cc");
> +
> + if (unlikely(!ok)) {
> + pr_warn_ratelimited("cpu%d: sys_rndr failed\n",
> + read_cpuid_id());
> + }
> + }
> +
> + preempt_enable_notrace();
> + return ok;
> +}
...
> +bool arch_get_random_seed_long(unsigned long *v)
> +{
> + preempt_disable_notrace();
> +
> + if (this_cpu_has_cap(ARM64_HAS_RNG)) {
> + unsigned long ok, val;
> +
> + /*
> + * Reads of RNDRRS set PSTATE.NZCV to 0b0000 on success,
> + * and set PSTATE.NZCV to 0b0100 otherwise.
> + */
> + asm volatile(
> + __mrs_s("%0", SYS_RNDRRS_EL0) "\n"
> + " cset %1, ne\n"
> + : "=r"(val), "=r"(ok)
> + :
> + : "cc");
> +
> + if (likely(ok)) {
> + *v = val;
> + preempt_enable_notrace();
> + return true;
> + }
> +
> + pr_warn_ratelimited("cpu%d: sys_rndrrs failed\n",
> + read_cpuid_id());
> + }
> +
> + preempt_enable_notrace();
> + return false;
> +}
Ho hum. The difference in form between these two functions is unintentional.
I had peeked at the assembly for arch_get_random_long, tweaked the structure a
bit, and meant to copy the result to arch_get_random_seed_long, but forgot.
The first form above produces fewer register spills from gcc8. I'll use that
for both for v3, supposing there are further comments to be addressed in review.
r~
next prev parent reply other threads:[~2019-10-29 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 20:32 [PATCH v2 0/1] arm64: Implement archrandom.h for ARMv8.5-RNG richard.henderson
2019-10-28 20:32 ` richard.henderson
2019-10-28 20:32 ` [PATCH v2 1/1] " richard.henderson
2019-10-28 20:32 ` richard.henderson
2019-10-29 13:24 ` Richard Henderson [this message]
2019-10-29 13:24 ` Richard Henderson
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=bfda9074-a866-d5d6-7f2a-3d91258a7113@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Dave.Martin@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arch@vger.kernel.org \
--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).