From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: GM.Ijewski@web.de, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] error: qcrypto_random_bytes() tried to read from /dev/[u]random, even on windows
Date: Mon, 24 Apr 2017 16:52:55 +0100 [thread overview]
Message-ID: <20170424155255.GD7705@redhat.com> (raw)
In-Reply-To: <CAFEAcA8noBf9VCZ+n24NMqVKGZC9D7KKMhLoacNyEA=WJ39uAg@mail.gmail.com>
On Mon, Apr 24, 2017 at 04:42:38PM +0100, Peter Maydell wrote:
> On 24 April 2017 at 16:41, Daniel P. Berrange <berrange@redhat.com> wrote:
> > We can have the existing qcrypto_init() call a qcrypto_random_init()
> > method to do the one-time initialization task, since that's already
> > required to run early in order to initialize gnutls when we use it.
>
> Yep, that would work, or initialize-on-first-call.
I avoided suggesting that, to avoid having to worry about thread-safe
initialization :-)
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-04-24 15:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 12:17 [Qemu-devel] error: qcrypto_random_bytes() tried to read from /dev/[u]random, even on windows GM.Ijewski
2017-04-24 12:50 ` Daniel P. Berrange
2017-04-24 13:30 ` Peter Maydell
2017-04-24 13:36 ` Daniel P. Berrange
2017-04-24 13:52 ` Peter Maydell
2017-04-24 13:57 ` Daniel P. Berrange
2017-04-24 14:05 ` Peter Maydell
2017-04-24 15:41 ` Daniel P. Berrange
2017-04-24 15:42 ` Peter Maydell
2017-04-24 15:52 ` Daniel P. Berrange [this message]
2017-04-24 16:33 ` Geert Martin Ijewski
2017-04-24 16:39 ` Daniel P. Berrange
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=20170424155255.GD7705@redhat.com \
--to=berrange@redhat.com \
--cc=GM.Ijewski@web.de \
--cc=peter.maydell@linaro.org \
--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.