From: "Samer El-Haj-Mahmoud" <samer.el-haj-mahmoud@arm.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "rfc@edk2.groups.io" <rfc@edk2.groups.io>,
Jiewen Yao <jiewen.yao@intel.com>,
Rahul Kumar <rahul1.kumar@intel.com>
Subject: Re: [edk2-devel] RFC: Adding support for ARM (RNDR etc.) to RngDxe
Date: Wed, 9 Dec 2020 04:47:49 +0000 [thread overview]
Message-ID: <DB7PR08MB3260A8786D9E46AC468846CA90CC0@DB7PR08MB3260.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <70a4f9e7-952c-cf05-bca7-009ee5b2cd3f@nuviainc.com>
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
There is also the TRNG FW API, which is an architected SMC firmware interface:
https://developer.arm.com/documentation/den0098/latest/
________________________________
From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of Rebecca Cran via groups.io <rebecca=nuviainc.com@groups.io>
Sent: Tuesday, December 8, 2020, 11:33 PM
To: devel@edk2.groups.io
Cc: rfc@edk2.groups.io; Jiewen Yao; Rahul Kumar
Subject: [edk2-devel] RFC: Adding support for ARM (RNDR etc.) to RngDxe
Currently, RngDxe in SecurityPkg only supports Intel, with RdRand support.
This RFC is to start a discussion about adding support for ARM.
I have a Git branch with support for the optional ARMv8.5 RNDR
instruction at https://github.com/bcran/edk2/commits/bcran-rndr which
moves the existing Intel support into a Rand directory, and adds code to
support RNDR in a new AArch64 directory.
There are other RNG implementations available for ARM, including
platform-specific approaches on Graviton
(https://lwn.net/Articles/790304/) and other platforms, so a more
thorough rearchitecting/redesign may be desired.
--
Rebecca Cran
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
[-- Attachment #2: Type: text/html, Size: 2999 bytes --]
next prev parent reply other threads:[~2020-12-09 4:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 4:32 RFC: Adding support for ARM (RNDR etc.) to RngDxe Rebecca Cran
2020-12-09 4:47 ` Samer El-Haj-Mahmoud [this message]
2020-12-10 11:26 ` [edk2-devel] " Sami Mujawar
2020-12-10 12:52 ` Leif Lindholm
2020-12-10 13:43 ` [edk2-rfc] " Yao, Jiewen
2021-01-14 21:05 ` Rebecca Cran
2021-01-16 2:51 ` Sami Mujawar
2021-02-10 22:49 ` Rebecca Cran
2021-02-11 18:26 ` Ard Biesheuvel
2021-04-20 20:04 ` Rebecca Cran
2021-04-22 9:30 ` Sami Mujawar
2021-04-26 14:45 ` Rebecca Cran
2021-04-26 21:28 ` Rebecca Cran
2021-04-26 21:45 ` [EXTERNAL] " Bret Barkelew
2021-04-27 13:22 ` Sami Mujawar
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-list 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=DB7PR08MB3260A8786D9E46AC468846CA90CC0@DB7PR08MB3260.eurprd08.prod.outlook.com \
--to=devel@edk2.groups.io \
/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