From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NzeD9-0000Av-VE for qemu-devel@nongnu.org; Wed, 07 Apr 2010 18:59:04 -0400 Received: from [140.186.70.92] (port=52025 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NzeD8-0000AF-Ir for qemu-devel@nongnu.org; Wed, 07 Apr 2010 18:59:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NzeD6-0004Sc-TI for qemu-devel@nongnu.org; Wed, 07 Apr 2010 18:59:02 -0400 Received: from mx20.gnu.org ([199.232.41.8]:25399) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NzeD6-0004SR-LI for qemu-devel@nongnu.org; Wed, 07 Apr 2010 18:59:00 -0400 Received: from mail.codesourcery.com ([38.113.113.100]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NzeD6-0001k5-4R for qemu-devel@nongnu.org; Wed, 07 Apr 2010 18:59:00 -0400 From: Paul Brook Date: Wed, 7 Apr 2010 23:58:53 +0100 References: <1270674156-9345-1-git-send-email-amit.shah@redhat.com> In-Reply-To: <1270674156-9345-1-git-send-email-amit.shah@redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201004072358.53971.paul@codesourcery.com> Subject: [Qemu-devel] Re: [PATCH 0/8] (v2) chardev, virtio-console: flow control, error handling, fixes List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Amit Shah Cc: Juan Quintela , "Michael S. Tsirkin" , qemu list , Gerd Hoffmann > Hello, > > This patchset introduces flow control to virtio-console and > chardev-based virtio serial ports. This series is based on the > previous series I sent on Mar 31st (00/17: v4: virtio-serial fixes, > new abi for port discovery) > > The qemu chardevs can now return -EAGAIN when a non-blocking remote > isn't ready to accept more data. > > Comments? This is a major change in semantics. Are you sure all users handle this correctly? My guess is that most of the devices don't. EAGAIN isn't really a useful response unless you have some way of notifying the device that it can send more data. Paul