From: Dor Laor <dor.laor@qumranet.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Jeff Garzik <jeff@garzik.org>,
virtualization@lists.osdl.org,
LKML <linux-kernel@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: Virt RNG?
Date: Thu, 15 May 2008 23:26:18 +0300 [thread overview]
Message-ID: <1210883178.24261.914.camel@localhost.localdomain> (raw)
In-Reply-To: <482C94AF.2010202@goop.org>
On Thu, 2008-05-15 at 20:53 +0100, Jeremy Fitzhardinge wrote:
> 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.
>
> It was actually one of the first device types proposed for what would
> become virtio, but as far as I know there has been no work on such a
> device. It certainly makes lots of sense.
>
There was a virtio-rng device:
http://www.mail-archive.com/virtualization@lists.linux-foundation.org/msg02902.html
Need to search what happened to it in Rusty's queues.
> J
> _______________________________________________
> Virtualization mailing list
> Virtualization@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2008-05-15 20:26 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 [this message]
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
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=1210883178.24261.914.camel@localhost.localdomain \
--to=dor.laor@qumranet.com \
--cc=herbert@gondor.apana.org.au \
--cc=jeff@garzik.org \
--cc=jeremy@goop.org \
--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).