qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] [PATCHv2] Fix virtio-console failure on unconnected pty
Date: Thu, 29 Dec 2011 13:47:43 +0100	[thread overview]
Message-ID: <4EFC616F.4060806@de.ibm.com> (raw)
In-Reply-To: <4EE9EBB9.9020300@de.ibm.com>

From: Christian Borntraeger <borntraeger@de.ibm.com>
    
when I tried qemu with -virtio-console pty the guest hangs and attaching on /dev/pts/<x> does
not return anything if the attachement is too late.
Turns out that the console is already throttled and the guest is heavily spinning but get_buf
never returns the buffer. There seems to be no way for the console to unthrottle the port.
    
For the virtio-serial use case we dont want to loose data but for the console case we better
drop  data instead of "killing" the guest console. If we get chardev->frontend notification
and a better behaving virtio-console we can revert this fix.
    
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>

---
 hw/virtio-serial-bus.c |   14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

Index: b/hw/virtio-serial-bus.c
===================================================================
--- a/hw/virtio-serial-bus.c
+++ 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);
+		/*
+                 * this is a temporary check until chardevs can signal to
+                 * frontends that they are writable again. This prevents
+                 * the console from going into throttled mode (forever)
+                 * if virtio-console is connected to a pty without a
+                 * listener. Otherwise the guest spins forever.
+                 * We can revert this if
+                 * 1: chardevs can notify frondends
+                 * 2: the guest driver does not spin in these cases
+                 */
+                if (!info->is_console) {
+                    virtio_serial_throttle_port(port, true);
+                }
                 port->iov_idx = i;
                 if (ret > 0) {
                     port->iov_offset += ret;

  parent reply	other threads:[~2011-12-29 12:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 12:44 [Qemu-devel] [RFC] virtio-console fails on unconnected pty Christian Borntraeger
2011-12-16  9:23 ` Amit Shah
2011-12-29 12:47 ` Christian Borntraeger [this message]
2011-12-29 13:27   ` [Qemu-devel] [PATCHv2] Fix virtio-console failure " Amit Shah
2011-12-29 13:39     ` Andreas Färber
2011-12-29 14:04   ` Amit Shah
2011-12-29 14:16     ` Christian Borntraeger
2011-12-29 14:19       ` Christian Borntraeger
2011-12-29 14:26       ` Amit Shah
2011-12-29 14:32         ` Christian Borntraeger
2011-12-29 14:56           ` Amit Shah
2011-12-29 15:14             ` Christian Borntraeger
2011-12-29 15:14           ` Amit Shah
2012-01-02 15:34             ` Alexander Graf
2012-01-02 15:41               ` Christian Borntraeger
2012-01-02 16:55                 ` Alexander Graf
2012-01-03 15:49                   ` 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=4EFC616F.4060806@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=amit.shah@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).