From: Hongxu Jia <hongxu.jia@windriver.com>
To: <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] libjitterentropy: add 2.1.2
Date: Fri, 9 Nov 2018 22:18:21 +0800 [thread overview]
Message-ID: <48b3a122-eeda-66ee-48a9-79eee6d64efb@windriver.com> (raw)
In-Reply-To: <f04feafb7ce74b451ee4e514e0331642c3fc12ac.camel@linuxfoundation.org>
On 2018/11/9 下午6:30, richard.purdie@linuxfoundation.org wrote:
> On Fri, 2018-11-09 at 17:12 +0800, Hongxu Jia wrote:
>> From the following kernel commit we know: Fedora has integrated the
>> jitter
>> entropy daemon to work around slow boot problems, especially on VM's
>> that
>> don't support virtio-rng
>>
>>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=81e69df38e2911b642ec121dec319fad2a4782f3
>> Do the same thing for Yocto.
>>
>> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> I'm not convinced this is going to help. The userspace support comes up
> quite late and the kernel blocking has already happened before that
> point when I last saw these issues. This was why I just enabled the
> virtio rng passthrough everywhere...
Yes, if VM support virtio-rng, we indeed do not need it, but for VM not
support virtio-rng, it makes sense.
> Is libjitterentropy actually helping your use cases?
Yes, it helps, I use runqemu without virtio-rng on qemumips64 to
simulate VM that don't support virtio-rng
With libjitterentropy and rng-tools, it takes <60s to init crng (after
rngd-tools started successfully)
[ 48.967114] random: crng init done
Fri Nov 9 14:06:49 2018: Starting random number generator daemon
Fri Nov 9 14:06:50 2018: Initalizing available sources
Fri Nov 9 14:06:50 2018:
Fri Nov 9 14:06:50 2018: Failed to init entropy source hwrng
Fri Nov 9 14:06:50 2018:
Fri Nov 9 14:07:05 2018: Enabling JITTER rng support
Fri Nov 9 14:07:06 2018:
Fri Nov 9 14:07:06 2018: Initalizing entropy source jitter
Fri Nov 9 14:07:06 2018:
Fri Nov 9 14:07:06 2018: .
Fri Nov 9 14:07:06 2018: Starting OpenBSD Secure Shell server: sshd
Fri Nov 9 14:07:06 2018: done.
Fri Nov 9 14:07:07 2018: hwclock: can't open '/dev/misc/rtc': No such
file or directory
Fri Nov 9 14:07:07 2018: Starting syslogd/klogd: done
Nov 9 14:07:07 qemumips64 user.notice kernel: [ 48.967114] random:
crng init done
Without libjitterentropy and rng-tools, it takes >2minutes to init crng
(there are some other
virtual device to generate noise for entropy)
[ 124.728869] random: crng init done
By the way, without virtio-rng, /dev/hwrng is dead on guest, that's the
reason why I upgrade
rng-tools and integrate libjitterentropy, previously old rng-tools hung
minutes in this situation.
//Hongxu
> Cheers,
>
> Richard
>
prev parent reply other threads:[~2018-11-09 14:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 9:12 [PATCH 0/2] Integrated the jitter entropy daemon to work around slow boot problems for Yocto Hongxu Jia
2018-11-09 9:12 ` [PATCH 1/2] rng-tools: 5 -> 6.6 Hongxu Jia
2018-11-09 22:50 ` richard.purdie
2018-11-09 23:00 ` Richard Purdie
2018-11-10 1:14 ` Hongxu Jia
2018-11-10 2:22 ` Hongxu Jia
2018-11-11 10:18 ` richard.purdie
2018-11-12 2:10 ` Hongxu Jia
2018-11-12 13:32 ` richard.purdie
2018-11-09 9:12 ` [PATCH 2/2] libjitterentropy: add 2.1.2 Hongxu Jia
2018-11-09 10:30 ` richard.purdie
2018-11-09 14:18 ` Hongxu Jia [this message]
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=48b3a122-eeda-66ee-48a9-79eee6d64efb@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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