[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7EC45708-38A1-4826-BC82-298EFAAE30B1@amazon.com>
Date: Fri, 7 Jun 2019 12:58:35 +0000
From: "Saidi, Ali" <alisaidi@...zon.com>
To: Will Deacon <will.deacon@....com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
Catalin Marinas <catalin.marinas@....com>,
Matt Mackall <mpm@...enic.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rindjunsky, Ron" <ronrindj@...zon.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
"Woodhouse, David" <dwmw@...zon.co.uk>
Subject: Re: [PATCH 0/3] Add support for Graviton TRNG
On 6/5/19, 7:20 AM, "Will Deacon" <will.deacon@....com> wrote:
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?
This interface allows us to provide the functionality from both EL2 and EL3 and support multiple different types of our instances which we unfortunately can't do with virt-io.
Ali
Powered by blists - more mailing lists