From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Gerd Stolpmann <info@gerd-stolpmann.de>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Strange behaviour of hwrng
Date: Fri, 21 Oct 2005 23:11:36 -0400 [thread overview]
Message-ID: <20051022031136.GA13689@localhost.localdomain> (raw)
In-Reply-To: <200510220252.00871.blaisorblade@yahoo.it>
On Sat, Oct 22, 2005 at 02:52:00AM +0200, Blaisorblade wrote:
> Proper solution: use a separate _host_ thread, which either sits blocked in a
> blocking read or calls poll() on the host /dev/random, and have it do the
> work.
Yeah, unfortunately. The real right thing to do is give the host random
driver fasync support (I'm not sure how possible this is, however, given the
nature of the hardware). Then we could register an IRQ for having some
randomness and do this right.
> It's not easy however.
It's fairly trivial. Look at the SIGIO workaround thread - this is essentially
the same thing.
> The ubd driver works currently this way, but the thing is not trivial to get
> right (and the UBD rewrite in the works has shown that).
The complexity there is due to entirely different causes, namely making sure
that requests are sent out in order and that pieces of the bitmap are written
out when they should be, and not before.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-10-22 3:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 18:24 [uml-devel] Strange behaviour of hwrng Gerd Stolpmann
2005-10-21 18:42 ` Blaisorblade
2005-10-21 19:06 ` Gerd Stolpmann
2005-10-22 0:52 ` Blaisorblade
2005-10-22 3:11 ` Jeff Dike [this message]
2005-10-22 11:29 ` Blaisorblade
2005-10-22 16:16 ` Gerd Stolpmann
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=20051022031136.GA13689@localhost.localdomain \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=info@gerd-stolpmann.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.