qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "Stefan Weil" <sw@weilnetz.de>, "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [BUG] GTK terminal is broken
Date: Mon, 29 Jul 2013 16:09:26 -0500	[thread overview]
Message-ID: <8761vt8455.fsf@codemonkey.ws> (raw)
In-Reply-To: <51F6D388.9090406@weilnetz.de>

Stefan Weil <sw@weilnetz.de> writes:

> Am 29.07.2013 22:34, schrieb Andreas Färber:
>> Am 29.07.2013 21:27, schrieb Stefan Weil:
>>> Am 29.07.2013 20:55, schrieb Anthony Liguori:
>>>> Stefan Weil <sw@weilnetz.de> writes:
>>>>
>>>>> Am 29.07.2013 20:05, schrieb Anthony Liguori:
>>>>>> Stefan Weil <sw@weilnetz.de> writes:
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> maybe most developers will already have noticed that the terminal output
>>>>>>> in QEMU's GTK user interface is broken. As far as I know, it never worked,
>>>>>>> but as there are working alternatives, I did not care much and forgot to
>>>>>>> report the issues.
>>>>>>>
>>>>>>> See these snapshots which show the problems with QEMU's GTK terminals:
>>>>>>>
>>>>>>> http://qemu.weilnetz.de/test/bugs/qemu-gtk-demo1.png
>>>>>>>
>>>>>>> Here the first line of the QEMUmonitor is only partially visible.
>>>>>>> Tested with Cygwin/X on W64 host, QEMU running on Debian Linux.
>>>>>>> Other X servers (e.g. native X on Debian Linux) don't show this
>>>>>>> problem.
>>>>>> It's a GTK/Cygwin/X bug.
>>>>>>
>>>>>> We use a vbox without anything particularly fancy happening.  Looks like
>>>>>> something is calculating layout incorrectly.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Anthony Liguori
>>>>> I miss a comment on the more important next two points.
>>>>> They are _not_ related to Cygwin / X.
>>>>>
>>>>> Do you investigate them?
>>>> What you're seeing has always existed and is not GTK specific.  There is
>>>> not flow control on the outgoing side of serial emulation.  Data will
>>>> get dropped.
>>>>
>>>> My guess is that your system is sufficiently slow and overloaded that
>>>> it's happening a lot for you.
>>>>
>>>> Regards,
>>>>
>>>> Anthony Liguori
>>> If it were as simply as that, that would be fine, but alas,
>>> it isn't. Even fast servers without any load show dropped
>>> characters. There are dropped characters for QEMU's
>>> monitor window (Alt-ctrl-2) and for Malta's line display
>>> (Alt-Ctrl-5). Neither of these two should suffer from missing
>>> flow control.
>>>
>>> And even a current X.Org on Ubuntu shows the first bug
>>> (crippled first line) here, so it is not Cygwin / X specific.
>> FWIW I've been seeing similar garbled-Gtk-output issues on openSUSE 12.3
>> but didn't investigate further. -monitor stdio has so far not failed me
>> on the same system by comparison.
>>
>> One reproducible test case was the openrisc kernel that Jia provided
>> recently.
>>
>> Regards,
>> Andreas
>
> Maybe the problems only occur with TCG, but not with KVM.
> That might explain why I get them more often than Anthony :-)
>
> Up to now, I did not try GTK terminals with KVM because my
> typical test scenario uses MIPS or ARM boards on Intel hosts.

x86 vs. other will come into play too.

The serial driver for x86 has some basic backoff logic.  I suspect
others don't.

My guess why you don't see this on -serial stdio is that it probably is
using synchronous I/O.

Regards,

Anthony Liguori

>
> Regards,
> Stefan

  reply	other threads:[~2013-07-29 21:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 16:04 [Qemu-devel] [BUG] GTK terminal is broken Stefan Weil
2013-07-29 18:05 ` Anthony Liguori
2013-07-29 18:18   ` Stefan Weil
2013-07-29 18:55     ` Anthony Liguori
2013-07-29 19:27       ` Stefan Weil
2013-07-29 20:34         ` Andreas Färber
2013-07-29 20:41           ` Stefan Weil
2013-07-29 21:09             ` Anthony Liguori [this message]
2013-07-29 20:43           ` Andreas Färber
2013-07-29 22:35     ` Laszlo Ersek
2013-08-28 17:50       ` Stefan Weil
2013-11-14 21:32 ` Stefan Weil
2013-11-15  6:00   ` Stefan Weil

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=8761vt8455.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=afaerber@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).