From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
"Ted Ts'o" <tytso@mit.edu>, "H. Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>
Subject: [PATCH 0/3] RDSEED support for the Linux kernel
Date: Tue, 4 Mar 2014 14:40:12 -0800 [thread overview]
Message-ID: <1393972815-16689-1-git-send-email-hpa@linux.intel.com> (raw)
From: "H. Peter Anvin" <hpa@linux.intel.com>
Upcoming Intel silicon adds a new RDSEED instruction. Whereas RDRAND
returns output from a PRNG, the RDSEED instruction returns fully
conditioned entropy that is suitable for use as seeds to a PRNG.
This patchset adds support for RDSEED in the Linux kernel in three
places:
1. During bootup, use RDSEED to initialize the entropy pool if
available (we already use RDRAND for this). We don't add any
credit at this point, but it will give much better starting point.
2. In the slow path to add_interrupt_randomness, executed once per
second, we take a single RDSEED sample and mix it into the entropy
pool, crediting it at 50% of its rated entropy. This was suggested
by Linus.
3. If we are about to block on /dev/random due to lack of entropy,
attempt an "emergency pool refill" using RDSEED.
Comments are, of course, appreciated.
-hpa
next reply other threads:[~2014-03-04 22:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 22:40 H. Peter Anvin [this message]
2014-03-04 22:40 ` [PATCH 1/3] x86, random: Enable the RDSEED instruction H. Peter Anvin
2014-03-05 8:43 ` Ingo Molnar
2014-03-04 22:40 ` [PATCH 2/3] random: Use arch_get_random_seed*() at init time and once a second H. Peter Anvin
2014-03-05 8:44 ` Ingo Molnar
2014-03-04 22:40 ` [PATCH 3/3] random: If we have arch_get_random_seed*(), try it before blocking H. Peter Anvin
2014-03-05 8:45 ` Ingo Molnar
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=1393972815-16689-1-git-send-email-hpa@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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.