From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:46094) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RgGn8-0004yY-8L for qemu-devel@nongnu.org; Thu, 29 Dec 2011 09:17:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RgGn7-0002cs-EA for qemu-devel@nongnu.org; Thu, 29 Dec 2011 09:17:10 -0500 Received: from e06smtp10.uk.ibm.com ([195.75.94.106]:36562) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RgGn6-0002cD-UE for qemu-devel@nongnu.org; Thu, 29 Dec 2011 09:17:09 -0500 Received: from /spool/local by e06smtp10.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 29 Dec 2011 14:17:01 -0000 Received: from d06av12.portsmouth.uk.ibm.com (d06av12.portsmouth.uk.ibm.com [9.149.37.247]) by d06nrmr1407.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pBTEGwIQ2232564 for ; Thu, 29 Dec 2011 14:16:58 GMT Received: from d06av12.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av12.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id pBTEGwe6009097 for ; Thu, 29 Dec 2011 07:16:58 -0700 Message-ID: <4EFC7657.5090804@de.ibm.com> Date: Thu, 29 Dec 2011 15:16:55 +0100 From: Christian Borntraeger MIME-Version: 1.0 References: <4EE9EBB9.9020300@de.ibm.com> <4EFC616F.4060806@de.ibm.com> <20111229140407.GC4576@amit.redhat.com> In-Reply-To: <20111229140407.GC4576@amit.redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCHv2] Fix virtio-console failure on unconnected pty List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Amit Shah Cc: "qemu-devel@nongnu.org" , Alexander Graf >> +++ b/hw/virtio-serial-bus.c >> @@ -163,7 +163,19 @@ static void do_flush_queued_data(VirtIOS >> abort(); >> } >> if (ret == -EAGAIN || (ret >= 0 && ret < buf_size)) { >> - virtio_serial_throttle_port(port, true); > > I'm surprised: did you test this with upstream qemu? That codebase > doesn't yet throttle writes, and this code path won't execute. Does > it really not reproduce with this patch? I think static void handle_output(VirtIODevice *vdev, VirtQueue *vq) [....] if (!port->throttled) { do_flush_queued_data(port, vq, vdev); return; makes a difference here, since we will never return the buffer to the guest, no? Christian