From: richard.purdie@linuxfoundation.org
To: Hongxu Jia <hongxu.jia@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] libjitterentropy: add 2.1.2
Date: Fri, 09 Nov 2018 10:30:34 +0000 [thread overview]
Message-ID: <f04feafb7ce74b451ee4e514e0331642c3fc12ac.camel@linuxfoundation.org> (raw)
In-Reply-To: <cb45fc25b42e280523a2a8c0173dd7b494cb4635.1541754618.git.hongxu.jia@windriver.com>
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...
Is libjitterentropy actually helping your use cases?
Cheers,
Richard
next prev parent reply other threads:[~2018-11-09 10:30 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 [this message]
2018-11-09 14:18 ` Hongxu Jia
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=f04feafb7ce74b451ee4e514e0331642c3fc12ac.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.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