From: Martin Wilck <mwilck@suse.com>
To: Claudio Fontana <cfontana@suse.de>,
Laurent Vivier <lvivier@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: "Jason Wang" <jasowang@redhat.com>, "Amit Shah" <amit@kernel.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v3] virtio-rng: return available data with O_NONBLOCK
Date: Wed, 14 Dec 2022 16:36:33 +0100 [thread overview]
Message-ID: <300a721254a21d01e8e408870e7b3db770b0d225.camel@suse.com> (raw)
In-Reply-To: <daf7de5f-2a5d-8b1b-4bcb-04991a4afac0@suse.de>
On Wed, 2022-12-14 at 14:41 +0100, Claudio Fontana wrote:
> On 11/26/20 11:49, Laurent Vivier wrote:
>
>
> Hi Laurent, Martin,
>
> is this resolved now?
>
> I wonder if this is covered by Laurent's kernel commit:
>
> commit 5c8e933050044d6dd2a000f9a5756ae73cbe7c44
> Author: Laurent Vivier <lvivier@redhat.com>
> Date: Thu Oct 28 12:11:10 2021 +0200
>
> hwrng: virtio - don't waste entropy
>
> if we don't use all the entropy available in the buffer, keep it
> and use it later.
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> Link:
> https://lore.kernel.org/r/20211028101111.128049-4-lvivier@redhat.com
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>
>
Hi Claudio,
sorry, I haven't had the time to look into this in more depth.
I don't know what the current situation is.
Martin
prev parent reply other threads:[~2022-12-14 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 14:28 [PATCH v3] virtio-rng: return available data with O_NONBLOCK mwilck
2020-08-11 14:42 ` Laurent Vivier
2020-08-26 12:26 ` Michael S. Tsirkin
2020-08-28 21:34 ` Martin Wilck
2020-08-31 12:37 ` Laurent Vivier
2020-09-08 14:14 ` Michael S. Tsirkin
2020-09-08 15:33 ` Martin Wilck
2020-10-21 14:43 ` Michael S. Tsirkin
2020-11-25 9:39 ` Michael S. Tsirkin
2020-11-26 10:49 ` Laurent Vivier
2022-12-14 13:41 ` Claudio Fontana
2022-12-14 15:36 ` Martin Wilck [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=300a721254a21d01e8e408870e7b3db770b0d225.camel@suse.com \
--to=mwilck@suse.com \
--cc=amit@kernel.org \
--cc=cfontana@suse.de \
--cc=jasowang@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).