qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu list <qemu-devel@nongnu.org>,
	Amit Shah <amit.shah@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] [PATCH v5 15/17] virtio-serial: Apps should consume all data that guest sends out / Fix virtio api abuse
Date: Wed, 14 Apr 2010 10:58:35 +0530	[thread overview]
Message-ID: <1271222917-7803-16-git-send-email-amit.shah@redhat.com> (raw)
In-Reply-To: <1271222917-7803-15-git-send-email-amit.shah@redhat.com>

We cannot indicate to the guest how much data was consumed by an app for
out_bufs.  So we just have to assume the apps will consume all the data
that are handed over to them.

Fix the virtio api abuse in control_out() and handle_output().

Signed-off-by: Amit Shah <amit.shah@redhat.com>
---
 hw/virtio-console.c    |    7 ++-----
 hw/virtio-serial-bus.c |    6 +++---
 hw/virtio-serial.h     |    6 +++---
 3 files changed, 8 insertions(+), 11 deletions(-)

diff --git a/hw/virtio-console.c b/hw/virtio-console.c
index bbbb6b8..caea11f 100644
--- a/hw/virtio-console.c
+++ b/hw/virtio-console.c
@@ -20,14 +20,11 @@ typedef struct VirtConsole {
 
 
 /* Callback function that's called when the guest sends us data */
-static size_t flush_buf(VirtIOSerialPort *port, const uint8_t *buf, size_t len)
+static void flush_buf(VirtIOSerialPort *port, const uint8_t *buf, size_t len)
 {
     VirtConsole *vcon = DO_UPCAST(VirtConsole, port, port);
-    ssize_t ret;
 
-    ret = qemu_chr_write(vcon->chr, buf, len);
-
-    return ret < 0 ? 0 : ret;
+    qemu_chr_write(vcon->chr, buf, len);
 }
 
 /* Readiness of the guest to accept data on a port */
diff --git a/hw/virtio-serial-bus.c b/hw/virtio-serial-bus.c
index 3053a35..ad44127 100644
--- a/hw/virtio-serial-bus.c
+++ b/hw/virtio-serial-bus.c
@@ -335,7 +335,7 @@ static void control_out(VirtIODevice *vdev, VirtQueue *vq)
         copied = iov_to_buf(elem.out_sg, elem.out_num, buf, 0, len);
 
         handle_control_message(vser, buf, copied);
-        virtqueue_push(vq, &elem, copied);
+        virtqueue_push(vq, &elem, 0);
     }
     qemu_free(buf);
     virtio_notify(vdev, vq);
@@ -379,11 +379,11 @@ static void handle_output(VirtIODevice *vdev, VirtQueue *vq)
         buf = qemu_malloc(buf_size);
         ret = iov_to_buf(elem.out_sg, elem.out_num, buf, 0, buf_size);
 
-        ret = port->info->have_data(port, buf, ret);
+        port->info->have_data(port, buf, ret);
         qemu_free(buf);
 
     next_buf:
-        virtqueue_push(vq, &elem, ret);
+        virtqueue_push(vq, &elem, 0);
     }
     virtio_notify(vdev, vq);
 }
diff --git a/hw/virtio-serial.h b/hw/virtio-serial.h
index f023873..62d76a2 100644
--- a/hw/virtio-serial.h
+++ b/hw/virtio-serial.h
@@ -136,10 +136,10 @@ struct VirtIOSerialPortInfo {
 
     /*
      * Guest wrote some data to the port. This data is handed over to
-     * the app via this callback. The app should return the number of
-     * bytes it successfully consumed.
+     * the app via this callback.  The app is supposed to consume all
+     * the data that is presented to it.
      */
-    size_t (*have_data)(VirtIOSerialPort *port, const uint8_t *buf, size_t len);
+    void (*have_data)(VirtIOSerialPort *port, const uint8_t *buf, size_t len);
 };
 
 /* Interface to the virtio-serial bus */
-- 
1.6.2.5

  reply	other threads:[~2010-04-14  5:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14  5:28 [Qemu-devel] [PATCH v5 00/17] virtio-serial fixes, new abi for port discovery, flow control Amit Shah
2010-04-14  5:28 ` [Qemu-devel] [PATCH v5 01/17] virtio-serial: save/load: Ensure target has enough ports Amit Shah
2010-04-14  5:28   ` [Qemu-devel] [PATCH v5 02/17] virtio-serial: save/load: Ensure nr_ports on src and dest are same Amit Shah
2010-04-14  5:28     ` [Qemu-devel] [PATCH v5 03/17] virtio-serial: save/load: Ensure we have hot-plugged ports instantiated Amit Shah
2010-04-14  5:28       ` [Qemu-devel] [PATCH v5 04/17] virtio-serial: save/load: Send target host connection status if different Amit Shah
2010-04-14  5:28         ` [Qemu-devel] [PATCH v5 05/17] virtio-serial: Use control messages to notify guest of new ports Amit Shah
2010-04-14  5:28           ` [Qemu-devel] [PATCH v5 06/17] virtio-serial: whitespace: match surrounding code Amit Shah
2010-04-14  5:28             ` [Qemu-devel] [PATCH v5 07/17] virtio-serial: Remove redundant check for 0-sized write request Amit Shah
2010-04-14  5:28               ` [Qemu-devel] [PATCH v5 08/17] virtio-serial: Update copyright year to 2010 Amit Shah
2010-04-14  5:28                 ` [Qemu-devel] [PATCH v5 09/17] virtio-serial: Propagate errors in initialising ports / devices in guest Amit Shah
2010-04-14  5:28                   ` [Qemu-devel] [PATCH v5 10/17] virtio-serial: Send out guest data to ports only if port is opened Amit Shah
2010-04-14  5:28                     ` [Qemu-devel] [PATCH v5 11/17] iov: Introduce a new file for helpers around iovs, add iov_from_buf() Amit Shah
2010-04-14  5:28                       ` [Qemu-devel] [PATCH v5 12/17] iov: Add iov_to_buf and iov_size helpers Amit Shah
2010-04-14  5:28                         ` [Qemu-devel] [PATCH v5 13/17] virtio-serial: Handle scatter-gather buffers for control messages Amit Shah
2010-04-14  5:28                           ` [Qemu-devel] [PATCH v5 14/17] virtio-serial: Handle scatter/gather input from the guest Amit Shah
2010-04-14  5:28                             ` Amit Shah [this message]
2010-04-14  5:28                               ` [Qemu-devel] [PATCH v5 16/17] virtio-serial: Discard data that guest sends us when ports aren't connected Amit Shah
2010-04-14  5:28                                 ` [Qemu-devel] [PATCH v5 17/17] virtio-serial: Implement flow control for individual ports Amit Shah
2010-04-14  7:48 ` [Qemu-devel] Re: [PATCH v5 00/17] virtio-serial fixes, new abi for port discovery, flow control Juan Quintela

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=1271222917-7803-16-git-send-email-amit.shah@redhat.com \
    --to=amit.shah@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).