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 v4 0/5] char: non-blocking writes, virtio-console flow control
Date: Tue,  4 May 2010 12:47:17 +0530	[thread overview]
Message-ID: <1272957442-7832-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.

Amit Shah (5):
  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: Factor out common init between console and generic
    ports
  virtio-console: Throttle virtio-serial-bus if we can't consume any
    more guest data

 gdbstub.c            |    2 +-
 hw/debugcon.c        |    2 +-
 hw/escc.c            |    3 +-
 hw/etraxfs_ser.c     |    4 +-
 hw/mcf_uart.c        |    2 +-
 hw/pl011.c           |    2 +-
 hw/pxa2xx.c          |    2 +-
 hw/serial.c          |    2 +-
 hw/sh_serial.c       |    2 +-
 hw/syborg_serial.c   |    3 +-
 hw/usb-serial.c      |    2 +-
 hw/virtio-console.c  |  156 +++++++++++++++++++++++++++++++++++++++++++-------
 hw/xen_console.c     |    7 +-
 hw/xilinx_uartlite.c |    5 +-
 monitor.c            |    4 +-
 net/slirp.c          |    2 +-
 net/socket.c         |    4 +-
 qemu-char.c          |   94 +++++++++++++++++++++++++++---
 qemu-char.h          |    9 +++
 qemu_socket.h        |    3 +-
 20 files changed, 257 insertions(+), 53 deletions(-)

             reply	other threads:[~2010-05-04  7:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04  7:17 Amit Shah [this message]
2010-05-04  7:17 ` [Qemu-devel] [PATCH v4 1/5] char: Let writers know how much data was written in case of errors Amit Shah
2010-05-04  7:17   ` [Qemu-devel] [PATCH v4 2/5] char: Add qemu_chr_write_nb() for nonblocking writes Amit Shah
2010-05-04  7:17     ` [Qemu-devel] [PATCH v4 3/5] char: unix/tcp: Add a non-blocking write handler Amit Shah
2010-05-04  7:17       ` [Qemu-devel] [PATCH v4 4/5] virtio-console: Factor out common init between console and generic ports Amit Shah
2010-05-04  7:17         ` [Qemu-devel] [PATCH v4 5/5] virtio-console: Throttle virtio-serial-bus if we can't consume any more guest data Amit Shah
2010-05-04  7:43       ` [Qemu-devel] Re: [PATCH v4 3/5] char: unix/tcp: Add a non-blocking write handler Gerd Hoffmann
2010-05-04  7:56         ` Amit Shah
2010-05-04  8:13           ` Gerd Hoffmann
2010-05-04  7:38     ` [Qemu-devel] Re: [PATCH v4 2/5] char: Add qemu_chr_write_nb() for nonblocking writes Gerd Hoffmann
2010-05-04  7:58       ` 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=1272957442-7832-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).