From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Zack Marvel" <zpmarvel@gmail.com>,
"Volker Rümelin" <vr_qemu@t-online.de>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH for 6.1 1/2] ui/gtk: add a keyboard fifo to the VTE consoles
Date: Mon, 19 Jul 2021 10:20:25 +0100 [thread overview]
Message-ID: <YPVD2RUFEizWsKq8@redhat.com> (raw)
In-Reply-To: <CAFEAcA9hzbs71s4aeLgwGsepwU9DgZrxcY16hr4EX9tDeeJv3Q@mail.gmail.com>
On Sun, Jul 18, 2021 at 02:00:03PM +0100, Peter Maydell wrote:
> On Sun, 18 Jul 2021 at 08:50, Volker Rümelin <vr_qemu@t-online.de> wrote:
> >
> > Since commit 8eb13bbbac ("ui/gtk: vte: fix sending multiple
> > characeters") it's very easy to lock up QEMU with the gtk ui.
> > If you configure a guest with a serial device and the guest
> > doesn't listen on this device, QEMU will lock up after
> > entering two characters in the serial console.
> >
> > To fix this problem copy the function kbd_send_chars() and
> > related code from ui/console.c to ui/gtk.c. kbd_send_chars()
> > doesn't lock up because it uses a timer instead of a busy loop
> > for the write retries.
> >
> > Fixes: 8eb13bbbac ("ui/gtk: vte: fix sending multiple characeters")
> > Signed-off-by: Volker Rümelin <vr_qemu@t-online.de>
> > ---
> > include/ui/gtk.h | 5 +++++
> > ui/gtk.c | 53 ++++++++++++++++++++++++++++++++++++++++--------
> > 2 files changed, 50 insertions(+), 8 deletions(-)
>
> This feels like maybe it's the kind of thing that should be handled
> more generically rather than in one particular UI frontend ?
IIUC none of the other frontends directly talk to the chardevs for the
serial ports. Instead they communicate via the text console interfaces.
So GTK is a bit special already here.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-07-19 9:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 7:46 [PATCH 0/2] ui/gtk: prevent QEMU lock up Volker Rümelin
2021-07-18 7:47 ` [PATCH for 6.1 1/2] ui/gtk: add a keyboard fifo to the VTE consoles Volker Rümelin
2021-07-18 13:00 ` Peter Maydell
2021-07-19 9:20 ` Daniel P. Berrangé [this message]
2021-07-19 18:22 ` Volker Rümelin
2021-07-19 18:37 ` Peter Maydell
2021-07-19 18:41 ` Daniel P. Berrangé
2021-07-19 18:52 ` Peter Maydell
2021-07-21 12:39 ` Gerd Hoffmann
2021-07-21 21:11 ` Volker Rümelin
2021-07-18 7:47 ` [PATCH for 6.2 2/2] ui/gtk: drop chars if the chardev frontend makes no progress Volker Rümelin
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=YPVD2RUFEizWsKq8@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vr_qemu@t-online.de \
--cc=zpmarvel@gmail.com \
/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).