From: "H. Peter Anvin" <hpa@zytor.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Hubert Kario <hkario@redhat.com>, Eric Blake <eblake@redhat.com>,
Cole Robinson <crobinso@redhat.com>,
libvirt-list@redhat.com, qemu-devel <qemu-devel@nongnu.org>,
"Richard W.M. Jones" <rjones@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Peter Krempa <pkrempa@redhat.com>,
Amit Shah <amit.shah@redhat.com>,
mik@miknet.net, jjaburek@redhat.com, sgrubb@redhat.com
Subject: Re: [Qemu-devel] RFC: virtio-rng and /dev/urandom
Date: Sun, 17 Apr 2016 17:20:05 -0700 [thread overview]
Message-ID: <57142835.7090603@zytor.com> (raw)
In-Reply-To: <1808605284.5070717.1460795498043.JavaMail.zimbra@redhat.com>
On 04/16/16 01:31, Paolo Bonzini wrote:
>
> Right, but there's always the point about people that use heterogeneous
> hosts and cannot pass rdrand/rdseed to the guest. For these, we should
> add a QEMU driver that uses rdrand/rdseed, and thus decouples virtio-rng
> from the host /dev/* completely.
>
You should be able to crib the code from rngd (rng-tools) pretty much
verbatim.
-hpa
next prev parent reply other threads:[~2016-04-18 0:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 10:41 [Qemu-devel] RFC: virtio-rng and /dev/urandom Cole Robinson
2016-04-15 11:46 ` Richard W.M. Jones
2016-04-15 11:54 ` [Qemu-devel] [libvirt] " Richard W.M. Jones
2016-04-20 22:48 ` [Qemu-devel] " Steve Grubb
2016-04-15 15:47 ` Eric Blake
2016-04-15 16:10 ` Hubert Kario
2016-04-16 0:46 ` H. Peter Anvin
2016-04-16 0:51 ` H. Peter Anvin
2016-04-16 8:31 ` Paolo Bonzini
2016-04-18 0:20 ` H. Peter Anvin [this message]
2016-04-18 0:27 ` H. Peter Anvin
2016-04-18 11:21 ` Hubert Kario
2016-04-18 11:00 ` Hubert Kario
2016-04-19 11:30 ` [Qemu-devel] [libvirt] " Yaniv Kaul
2016-04-15 15:56 ` [Qemu-devel] " H. Peter Anvin
2016-04-15 16:06 ` Hubert Kario
2016-04-18 9:28 ` Daniel P. Berrange
2016-04-18 9:46 ` H. Peter Anvin
2016-04-18 11:07 ` Hubert Kario
2016-04-18 11:26 ` Daniel P. Berrange
2016-04-18 21:45 ` H. Peter Anvin
2016-04-20 22:21 ` Cole Robinson
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=57142835.7090603@zytor.com \
--to=hpa@zytor.com \
--cc=amit.shah@redhat.com \
--cc=berrange@redhat.com \
--cc=crobinso@redhat.com \
--cc=eblake@redhat.com \
--cc=hkario@redhat.com \
--cc=jjaburek@redhat.com \
--cc=libvirt-list@redhat.com \
--cc=mik@miknet.net \
--cc=pbonzini@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=sgrubb@redhat.com \
/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).