From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ard Biesheuvel <ardb@kernel.org>,
Andre Przywara <andre.przywara@arm.com>
Cc: Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>,
"Saidi, Ali" <alisaidi@amazon.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: RNDR/SS vs. SMCCC
Date: Thu, 03 Jun 2021 08:04:43 +1000 [thread overview]
Message-ID: <2ae9253c6f5753c13a7ed755ab0c67316c06d9b0.camel@kernel.crashing.org> (raw)
In-Reply-To: <CAMj1kXFVXe83jDddMc8RjSRDSm_csd4GJ+ZUug24NkziMB4f9w@mail.gmail.com>
On Mon, 2021-05-31 at 07:24 +0200, Ard Biesheuvel wrote:
>
> The SMCCC interface was created not as an alternative/complement to
> RNDR/RNDRRS, but to codify what several partners (including AWS) were
> doing at the time:
Talking of which, any particular reasons not to have (happy to
contribute ours) a /dev/hwrng wrapper around SMCCC ? For various "gov
compliance" kind of thing it's useful in addition to seeding the kernel
CRNG.
Cheers,
Ben.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-02 22:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 23:54 RNDR/SS vs. SMCCC Benjamin Herrenschmidt
2021-05-27 12:50 ` Mark Brown
2021-05-27 23:12 ` Benjamin Herrenschmidt
2021-05-28 12:56 ` Mark Brown
2021-05-29 2:36 ` Benjamin Herrenschmidt
2021-05-31 1:02 ` Andre Przywara
2021-05-31 5:24 ` Ard Biesheuvel
2021-06-02 22:04 ` Benjamin Herrenschmidt [this message]
2021-06-03 0:19 ` Andre Przywara
2021-06-03 1:41 ` Benjamin Herrenschmidt
2021-06-03 7:10 ` Ard Biesheuvel
2021-06-03 21:30 ` Benjamin Herrenschmidt
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=2ae9253c6f5753c13a7ed755ab0c67316c06d9b0.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=alisaidi@amazon.com \
--cc=andre.przywara@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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 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.