From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeff Garzik <jeff@garzik.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
virtualization@lists.osdl.org, jeremy@xensource.com,
Herbert Xu <herbert@gondor.apana.org.au>,
Avi Kivity <avi@qumranet.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: Virt RNG?
Date: Fri, 16 May 2008 09:43:08 +1000 [thread overview]
Message-ID: <200805160943.08788.rusty@rustcorp.com.au> (raw)
In-Reply-To: <482C8595.5030509@garzik.org>
On Friday 16 May 2008 04:48:53 Jeff Garzik wrote:
> Has anyone yet written a "hw" RNG module for virt, that reads the host's
> random number pool?
>
> All this talk[1] about IRQF_SAMPLE_RANDOM in network drivers reminds me
> that virt guest instances should be grabbing random numbers from the
> host, especially if the host has a hardware RNG.
Yes, I prepared one earlier. I was a little surprised to see that hwrng
drivers don't contribute in any way to the entropy pool though, but now
reading the thread I find out about rngd (not installed on my Ubuntu system,
but available at least).
One could argue that virtual rng should try to feed the kernel rng directly,
with or without entropy credit.
Anyway, since there's interest, I'll drag virtio_rng from the bottom of the
queue, apply Christian's fix (which I somehow missed before, sorry
Christian), and re-post.
Thanks,
Rusty.
next prev parent reply other threads:[~2008-05-15 23:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 18:48 Virt RNG? Jeff Garzik
2008-05-15 19:53 ` Jeremy Fitzhardinge
2008-05-15 20:26 ` Dor Laor
2008-05-15 20:31 ` Christian Borntraeger
2008-05-15 20:44 ` Jeff Garzik
2008-05-15 20:43 ` Jeff Dike
2008-05-15 23:43 ` Rusty Russell [this message]
2008-05-16 0:07 ` Henrique de Moraes Holschuh
2008-05-16 5:31 ` [PATCH 1/2] virtio: hardware random device Rusty Russell
[not found] ` <200805161531.44725.rusty@rustcorp.com.au>
2008-05-16 5:39 ` [PATCH 2/2] lguest: virtio-rng support Rusty Russell
2008-05-16 5:39 ` Rusty Russell
2008-05-16 7:31 ` [PATCH 1/2] virtio: hardware random device Christian Borntraeger
[not found] ` <200805161539.59739.rusty@rustcorp.com.au>
2008-05-16 10:49 ` [PATCH 2/2] lguest: virtio-rng support Johannes Berg
[not found] ` <1210934981.6381.1.camel@johannes.berg>
2008-05-16 20:25 ` H. Peter Anvin
2008-05-17 4:46 ` Rusty Russell
[not found] ` <200805171446.39814.rusty@rustcorp.com.au>
2008-05-17 4:50 ` H. Peter Anvin
2008-05-17 6:28 ` Rusty Russell
[not found] ` <200805171628.03801.rusty@rustcorp.com.au>
2008-05-17 6:43 ` Herbert Xu
2008-05-17 7:43 ` Christian Borntraeger
2008-05-17 15:56 ` H. Peter Anvin
2008-05-17 7:47 ` Jeremy Fitzhardinge
2008-05-17 15:57 ` H. Peter Anvin
[not found] ` <482E8D75.10606@goop.org>
2008-05-19 9:05 ` Rusty Russell
[not found] ` <200805191905.11452.rusty@rustcorp.com.au>
2008-05-19 9:10 ` Jeremy Fitzhardinge
[not found] ` <48314419.4080606@goop.org>
2008-05-19 9:28 ` Rusty Russell
[not found] ` <200805191928.13043.rusty@rustcorp.com.au>
2008-05-19 9:45 ` Jeremy Fitzhardinge
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=200805160943.08788.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=avi@qumranet.com \
--cc=borntraeger@de.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=jeff@garzik.org \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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 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).