From: richard.henderson@linaro.org To: linux-arm-kernel@lists.infradead.org Cc: mark.rutland@arm.com, ard.biesheuvel@linaro.org, linux-crypto@vger.kernel.org, Richard Henderson <richard.henderson@linaro.org> Subject: [PATCH v6 0/1] arm64: Implement archrandom.h for ARMv8.5-RNG Date: Wed, 13 Nov 2019 11:11:50 +0100 [thread overview] Message-ID: <20191113101151.13389-1-richard.henderson@linaro.org> (raw) From: Richard Henderson <richard.henderson@linaro.org> Here's v6. I believe I've collected all of the comments from both Ard and Mark across v4 and v5, as well as from the cafe in Lyon. I had thought about using a simple function pointer for arch_get_random_seed_long, but didn't see a good place where I could update that at the end of boot. Which lead me to ALTERNATIVE_CB, which is way overkill, but is already part of the update infrastructure. Tested with qemu -cpu {max,cortex-a57}, which covers both sides of the alternative. GDB breakpoints confirm that boot_get_random_seed_long is what is called from rand_initialize, and that this_cpu_has_cap returns the correct result. r~ Documentation/arm64/cpu-feature-registers.rst | 2 + arch/arm64/include/asm/archrandom.h | 55 +++++++++++++++ arch/arm64/include/asm/cpucaps.h | 3 +- arch/arm64/include/asm/sysreg.h | 4 ++ arch/arm64/kernel/cpufeature.c | 13 ++++ arch/arm64/kernel/random.c | 67 +++++++++++++++++++ arch/arm64/Kconfig | 12 ++++ arch/arm64/kernel/Makefile | 1 + drivers/char/Kconfig | 4 +- 9 files changed, 158 insertions(+), 3 deletions(-) create mode 100644 arch/arm64/include/asm/archrandom.h create mode 100644 arch/arm64/kernel/random.c -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: richard.henderson@linaro.org To: linux-arm-kernel@lists.infradead.org Cc: mark.rutland@arm.com, Richard Henderson <richard.henderson@linaro.org>, linux-crypto@vger.kernel.org, ard.biesheuvel@linaro.org Subject: [PATCH v6 0/1] arm64: Implement archrandom.h for ARMv8.5-RNG Date: Wed, 13 Nov 2019 11:11:50 +0100 [thread overview] Message-ID: <20191113101151.13389-1-richard.henderson@linaro.org> (raw) From: Richard Henderson <richard.henderson@linaro.org> Here's v6. I believe I've collected all of the comments from both Ard and Mark across v4 and v5, as well as from the cafe in Lyon. I had thought about using a simple function pointer for arch_get_random_seed_long, but didn't see a good place where I could update that at the end of boot. Which lead me to ALTERNATIVE_CB, which is way overkill, but is already part of the update infrastructure. Tested with qemu -cpu {max,cortex-a57}, which covers both sides of the alternative. GDB breakpoints confirm that boot_get_random_seed_long is what is called from rand_initialize, and that this_cpu_has_cap returns the correct result. r~ Documentation/arm64/cpu-feature-registers.rst | 2 + arch/arm64/include/asm/archrandom.h | 55 +++++++++++++++ arch/arm64/include/asm/cpucaps.h | 3 +- arch/arm64/include/asm/sysreg.h | 4 ++ arch/arm64/kernel/cpufeature.c | 13 ++++ arch/arm64/kernel/random.c | 67 +++++++++++++++++++ arch/arm64/Kconfig | 12 ++++ arch/arm64/kernel/Makefile | 1 + drivers/char/Kconfig | 4 +- 9 files changed, 158 insertions(+), 3 deletions(-) create mode 100644 arch/arm64/include/asm/archrandom.h create mode 100644 arch/arm64/kernel/random.c -- 2.17.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-11-13 10:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-13 10:11 richard.henderson [this message] 2019-11-13 10:11 ` [PATCH v6 0/1] arm64: Implement archrandom.h for ARMv8.5-RNG richard.henderson 2019-11-13 10:11 ` [PATCH v6 1/1] " richard.henderson 2019-11-13 10:11 ` richard.henderson 2019-11-13 17:08 ` Mark Rutland 2019-11-13 17:08 ` Mark Rutland
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=20191113101151.13389-1-richard.henderson@linaro.org \ --to=richard.henderson@linaro.org \ --cc=ard.biesheuvel@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-crypto@vger.kernel.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: linkBe 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.