qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gal Hammer <ghammer@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gal Hammer <ghammer@redhat.com>
Subject: [Qemu-devel] [PATCH v2] virtio-serial: Do not notify virtqueue if no element was pushed back.
Date: Sun, 11 Aug 2013 16:25:25 +0300	[thread overview]
Message-ID: <1376227525-28639-1-git-send-email-ghammer@redhat.com> (raw)

The redundant notification caused the Windows' driver to duplicate the
pending write request's buffer. The driver was fixed, but I think this
change is still required.

Signed-off-by: Gal Hammer <ghammer@redhat.com>
---
 hw/char/virtio-serial-bus.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c
index da417c7..0d38b4b 100644
--- a/hw/char/virtio-serial-bus.c
+++ b/hw/char/virtio-serial-bus.c
@@ -105,6 +105,7 @@ static void do_flush_queued_data(VirtIOSerialPort *port, VirtQueue *vq,
                                  VirtIODevice *vdev)
 {
     VirtIOSerialPortClass *vsc;
+    bool elem_pushed = false;
 
     assert(port);
     assert(virtio_queue_ready(vq));
@@ -145,9 +146,12 @@ static void do_flush_queued_data(VirtIOSerialPort *port, VirtQueue *vq,
             break;
         }
         virtqueue_push(vq, &port->elem, 0);
+        elem_pushed = true;
         port->elem.out_num = 0;
     }
-    virtio_notify(vdev, vq);
+    if (elem_pushed) {
+        virtio_notify(vdev, vq);
+    }
 }
 
 static void flush_queued_data(VirtIOSerialPort *port)
-- 
1.8.1.4

             reply	other threads:[~2013-08-11 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-11 13:25 Gal Hammer [this message]
2013-08-12 13:34 ` [Qemu-devel] [PATCH v2] virtio-serial: Do not notify virtqueue if no element was pushed back Laszlo Ersek
2013-09-05 19:05 ` 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=1376227525-28639-1-git-send-email-ghammer@redhat.com \
    --to=ghammer@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).