From: Will Deacon <will.deacon@arm.com>
To: Ali Saidi <alisaidi@amazon.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ron Rindjunsky <ronrindj@amazon.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: [PATCH 0/3] Add support for Graviton TRNG
Date: Wed, 5 Jun 2019 13:20:31 +0100 [thread overview]
Message-ID: <20190605122031.GK15030@fuggles.cambridge.arm.com> (raw)
In-Reply-To: <20190604203100.15050-1-alisaidi@amazon.com>
On Tue, Jun 04, 2019 at 08:30:57PM +0000, Ali Saidi wrote:
> AWS Graviton based systems provide an Arm SMC call in the vendor defined
> hypervisor region to read random numbers from a HW TRNG and return them to the
> guest.
>
> We've observed slower guest boot and especially reboot times due to lack of
> entropy and providing access to a TRNG is meant to address this.
Curious, but why this over something like virtio-rng?
Will
next prev parent reply other threads:[~2019-06-05 12:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 20:30 [PATCH 0/3] Add support for Graviton TRNG Ali Saidi
2019-06-04 20:30 ` [PATCH 1/3] arm/arm64: Add smccc hypervisor service identifiers Ali Saidi
2019-06-04 20:30 ` [PATCH 2/3] arm64: export acpi_psci_use_hvc Ali Saidi
2019-06-05 9:40 ` Sudeep Holla
2019-06-05 10:38 ` Mark Rutland
2019-06-05 11:02 ` Sudeep Holla
2019-06-05 16:07 ` Saidi, Ali
2019-06-04 20:31 ` [PATCH 3/3] hwrng: Add support for AWS Graviton TRNG Ali Saidi
2019-06-05 12:20 ` Will Deacon [this message]
2019-06-07 12:58 ` [PATCH 0/3] Add support for " Saidi, Ali
2019-06-28 18:05 ` Saidi, Ali
2019-07-01 8:28 ` Will Deacon
2019-07-01 17:02 ` Will Deacon
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=20190605122031.GK15030@fuggles.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=alisaidi@amazon.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=ronrindj@amazon.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 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).