qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: qemu list <qemu-devel@nongnu.org>
Cc: Amit Shah <amit.shah@redhat.com>,
	Paul Brook <paul@codesourcery.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] [PATCH v5 0/6] char: non-blocking writes, virtio-console flow control
Date: Tue,  4 May 2010 16:22:41 +0530	[thread overview]
Message-ID: <1272970367-24647-1-git-send-email-amit.shah@redhat.com> (raw)

Hello,

This series lets interested callers ask for an -EAGAIN return from the
chardev backends (only unix and tcp sockets as of now) to implement
their own flow control.

A new call, qemu_chr_write_nb() is added, that will fallback to
qemu_chr_write() if the backend file isn't non-blocking or if no
callback was supplied.

Support for other backend types is easy to add and will be done in
later patches.

v5:
- Fix bug pointed out by Gerd
- Convert to using a struct for passing on handlers to
  qemu_chr_add_handlers() instead of passing each one
  individually. Simplifies patches. (Inspired by Juan's comment)
- Re-arranged patches

Amit Shah (6):
  virtio-console: Factor out common init between console and generic
    ports
  char: Add a QemuChrHandlers struct to initialise chardev handlers
  char: Let writers know how much data was written in case of errors
  char: Add qemu_chr_write_nb() for nonblocking writes
  char: unix/tcp: Add a non-blocking write handler
  virtio-console: Throttle virtio-serial-bus if we can't consume any
    more guest data

 gdbstub.c            |    9 ++-
 hw/debugcon.c        |    2 +-
 hw/escc.c            |    9 ++-
 hw/etraxfs_ser.c     |   13 +++-
 hw/mcf_uart.c        |    9 ++-
 hw/pl011.c           |    9 ++-
 hw/pxa2xx.c          |   13 +++-
 hw/serial.c          |    9 ++-
 hw/sh_serial.c       |   12 +++-
 hw/syborg_serial.c   |    9 ++-
 hw/usb-serial.c      |    9 ++-
 hw/virtio-console.c  |  162 +++++++++++++++++++++++++++++++++++++++++++------
 hw/xen_console.c     |   16 ++++--
 hw/xilinx_uartlite.c |   11 +++-
 monitor.c            |   19 +++++-
 net/slirp.c          |    8 ++-
 net/socket.c         |    4 +-
 qemu-char.c          |  119 +++++++++++++++++++++++++++++++------
 qemu-char.h          |   20 +++++-
 qemu_socket.h        |    3 +-
 20 files changed, 381 insertions(+), 84 deletions(-)

             reply	other threads:[~2010-05-04 10:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 10:52 Amit Shah [this message]
2010-05-04 10:52 ` [Qemu-devel] [PATCH v5 1/6] virtio-console: Factor out common init between console and generic ports Amit Shah
2010-05-04 10:52   ` [Qemu-devel] [PATCH v5 2/6] char: Add a QemuChrHandlers struct to initialise chardev handlers Amit Shah
2010-05-04 10:52     ` [Qemu-devel] [PATCH v5 3/6] char: Let writers know how much data was written in case of errors Amit Shah
2010-05-04 10:52       ` [Qemu-devel] [PATCH v5 4/6] char: Add qemu_chr_write_nb() for nonblocking writes Amit Shah
2010-05-04 10:52         ` [Qemu-devel] [PATCH v5 5/6] char: unix/tcp: Add a non-blocking write handler Amit Shah
2010-05-04 10:52           ` [Qemu-devel] [PATCH v5 6/6] virtio-console: Throttle virtio-serial-bus if we can't consume any more guest data Amit Shah
2010-05-04 11:24       ` [Qemu-devel] Re: [PATCH v5 3/6] char: Let writers know how much data was written in case of errors Gerd Hoffmann
2010-05-04 11:31         ` Amit Shah
2010-05-04 13:30           ` Gerd Hoffmann
2010-05-04 20:09     ` [Qemu-devel] [PATCH v5 2/6] char: Add a QemuChrHandlers struct to initialise chardev handlers Blue Swirl

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=1272970367-24647-1-git-send-email-amit.shah@redhat.com \
    --to=amit.shah@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=paul@codesourcery.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).