All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Ian Molton <ian.molton@collabora.co.uk>,
	Paul Brook <paul@codesourcery.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] VirtIO RNG
Date: Wed, 21 Apr 2010 10:40:07 +0100	[thread overview]
Message-ID: <20100421094007.GC13114@shareable.org> (raw)
In-Reply-To: <4BCEAC99.8000206@redhat.com>

Gerd Hoffmann wrote:
> On 04/20/10 23:31, Ian Molton wrote:
> 
> >Using virtio-rng means that the data is going into the guest
> >kernels hwrng subsystem.
> 
> Which is *the* major advantage of the virtio-rng driver.  In case the 
> guest kernel is recent enougth to have support for it, it will 
> JustWork[tm].  No need for guest configuration, no need for some 
> userspace tool.  I'd like to see this driver being merged.
> 
> With any kind of serial port (be it a emulated 16550 or virtio-serial) 
> you'll need some daemon running inside the guest grabbing entropy data 
> from the port and feeding it back into the kernel.

That's a bunch of false assumptions.

There's no reason a hwrng connector to virtio-serial could not be
automatic in a similar way to the console.

But enough of that: It's history now; the guest virtio-rng has existed
for more than a year.  It is also amazingly short and simple.  Yay for Rusty!

I don't object to virtio-rng; I think it's fine in principle and would
be happy to see the existing guests which have a virtio-rng driver
make use of it.

A bit of overlapping functionality is rife in emulators anyway :-)

-- Jamie

  reply	other threads:[~2010-04-21  9:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 14:05 [Qemu-devel] [PATCH 0/2] VirtIO RNG Ian Molton
2010-03-30 14:12 ` [Qemu-devel] [PATCH 1/2] " Ian Molton
2010-03-30 14:13 ` [Qemu-devel] [PATCH 2/2] " Ian Molton
2010-04-01 12:17   ` Paul Brook
2010-04-01 12:30     ` Jamie Lokier
2010-04-01 14:03       ` Paul Brook
2010-04-02 10:13         ` Ian Molton
2010-04-03 15:06           ` Paul Brook
2010-04-13 14:41             ` Ian Molton
2010-04-13 15:01               ` Paul Brook
2010-04-13 15:32               ` Paul Brook
2010-04-20 15:15                 ` Ian Molton
2010-04-20 16:13                   ` Jamie Lokier
2010-04-20 19:52                     ` Ian Molton
2010-04-20 20:11                       ` Blue Swirl
2010-04-20 20:56                       ` Jamie Lokier
2010-04-20 21:31                         ` Ian Molton
2010-04-20 21:55                           ` Jamie Lokier
2010-04-21  7:43                           ` Gerd Hoffmann
2010-04-21  9:40                             ` Jamie Lokier [this message]
2010-04-21 12:34                               ` Ian Molton
2010-04-21 13:55                                 ` Gerd Hoffmann
2010-04-22 19:06                                   ` Ian Molton
2010-04-22 21:05                                     ` Jamie Lokier
2010-04-23 10:17                                       ` Ian Molton
2010-04-24  1:37                                         ` Jamie Lokier
2010-04-24  8:58                                           ` Ian Molton
2010-04-23  8:27                                     ` Gerd Hoffmann
2010-04-23  9:28                                       ` Ian Molton
2010-04-23 14:07                                         ` Gerd Hoffmann
2010-04-23 15:49                                           ` Ian Molton
2010-04-23 17:32                                             ` Jamie Lokier
2010-04-24  9:16                                               ` Ian Molton
2010-04-02 10:15       ` Ian Molton
2010-04-02 10:07     ` Ian Molton
2010-05-03 17:56   ` Anthony Liguori

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=20100421094007.GC13114@shareable.org \
    --to=jamie@shareable.org \
    --cc=ian.molton@collabora.co.uk \
    --cc=kraxel@redhat.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.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 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.