From: Amit Shah <amit.shah@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [RFC] virtio-console fails on unconnected pty
Date: Fri, 16 Dec 2011 14:53:57 +0530 [thread overview]
Message-ID: <20111216092357.GA3071@amit-x200.redhat.com> (raw)
In-Reply-To: <4EE9EBB9.9020300@de.ibm.com>
Hi Christian,
On (Thu) 15 Dec 2011 [13:44:41], Christian Borntraeger wrote:
> Amit,
>
> 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.
Unfortunately we don't yet have chardevs to signal to frontends that
they're writable again. This leads to things staying blocked, and
guests spinning. (At least Fedora has patches that mitigate this
situation, after upstream acceptance of the patches failed.)
> 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.
Hm, looks like pty open/close notifications might be broken if you
never attached a pty to a console but the guest sent out stuff to the
host anyway.
> For the virtio-serial use case we dont want to loose data but for the console we better drop
> data instead of "killing" the guest console. The old serial console also drops data after a
> retry, so what about dropping data righ away if no listener is connected to the pty?
This should be temporary, though. Once chardevs can notify frontends
about the ability to consume more data, this patch should be reverted,
right?
> This experimental patch seems to help. Makes sense?
If it's a temporary thing, I don't mind. Can you please re-submit
without the RFC tag and perhaps a comment below to make explicit why
we're doing this?
> --- a/hw/virtio-serial-bus.c
> +++ b/hw/virtio-serial-bus.c
> @@ -163,7 +163,9 @@ static void do_flush_queued_data(VirtIOSerialPort *port, VirtQueue *vq,
> abort();
> }
> if (ret == -EAGAIN || (ret >= 0 && ret < buf_size)) {
> - virtio_serial_throttle_port(port, true);
> + if (!info->is_console) {
> + virtio_serial_throttle_port(port, true);
> + }
> port->iov_idx = i;
> if (ret > 0) {
> port->iov_offset += ret;
>
Amit
next prev parent reply other threads:[~2011-12-16 9:24 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 [this message]
2011-12-29 12:47 ` [Qemu-devel] [PATCHv2] Fix virtio-console failure " Christian Borntraeger
2011-12-29 13:27 ` 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=20111216092357.GA3071@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.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).