From: Ladi Prosek <lprosek@redhat.com>
To: qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, pbonzini@redhat.com, mst@redhat.com,
Ladi Prosek <lprosek@redhat.com>,
pagupta@redhat.com
Subject: [Qemu-devel] [PATCH] virtio-rng: ask for more data if queue is not fully drained
Date: Thu, 3 Mar 2016 10:48:34 +0100 [thread overview]
Message-ID: <1456998514-19271-1-git-send-email-lprosek@redhat.com> (raw)
This commit effectively reverts:
commit 4621c1768ef5d12171cca2aa1473595ecb9f1c9e
Author: Amit Shah <amit.shah@redhat.com>
Date: Wed Nov 21 11:21:19 2012 +0530
virtio-rng: remove extra request for entropy
but instead of calling virtio_rng_process unconditionally, it
first checks to see if the queue is empty as a little bit of
optimization.
Signed-off-by: Ladi Prosek <lprosek@redhat.com>
---
This commit has a logical dependency on
[PATCH v3 0/4] rng-random: implement request queue
which removes a synchronous invocation of the receive_func callback in
rng_random_request_entropy, thereby eliminating the risk of infinite
recursion.
hw/virtio/virtio-rng.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/hw/virtio/virtio-rng.c b/hw/virtio/virtio-rng.c
index 17da2f8..d713464 100644
--- a/hw/virtio/virtio-rng.c
+++ b/hw/virtio/virtio-rng.c
@@ -69,6 +69,13 @@ static void chr_read(void *opaque, const void *buf, size_t size)
g_free(elem);
}
virtio_notify(vdev, vrng->vq);
+
+ if (!virtio_queue_empty(vrng->vq)) {
+ /* If we didn't drain the queue, call virtio_rng_process
+ * to take care of asking for more data as appropriate.
+ */
+ virtio_rng_process(vrng);
+ }
}
static void virtio_rng_process(VirtIORNG *vrng)
--
2.5.0
next reply other threads:[~2016-03-03 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 9:48 Ladi Prosek [this message]
2016-03-03 12:08 ` [Qemu-devel] [PATCH] virtio-rng: ask for more data if queue is not fully drained Amit Shah
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=1456998514-19271-1-git-send-email-lprosek@redhat.com \
--to=lprosek@redhat.com \
--cc=amit.shah@redhat.com \
--cc=mst@redhat.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--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 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).