From: Laszlo Ersek <lersek@redhat.com>
To: Gal Hammer <ghammer@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] virtio-serial: Do not notify virtqueue if no element was pushed back.
Date: Mon, 12 Aug 2013 15:34:39 +0200 [thread overview]
Message-ID: <5208E46F.7010506@redhat.com> (raw)
In-Reply-To: <1376227525-28639-1-git-send-email-ghammer@redhat.com>
On 08/11/13 15:25, Gal Hammer wrote:
> 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)
>
Differs from v1 only in a more precise subject / more details in the
commit msg.
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
next prev parent reply other threads:[~2013-08-12 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 13:25 [Qemu-devel] [PATCH v2] virtio-serial: Do not notify virtqueue if no element was pushed back Gal Hammer
2013-08-12 13:34 ` Laszlo Ersek [this message]
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=5208E46F.7010506@redhat.com \
--to=lersek@redhat.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.