All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: "Volker Rümelin" <vr_qemu@t-online.de>
Cc: Gerd Hoffmann <kraxel@redhat.com>, QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH for 6.1] ui/gtk: retry sending VTE console input
Date: Tue, 10 Aug 2021 12:16:42 +0400	[thread overview]
Message-ID: <CAJ+F1CL0=w8zqyjYp5Av96R=Q1KT2SZt4jB_LrgYPg=xmix_3w@mail.gmail.com> (raw)
In-Reply-To: <20210810063257.17411-1-vr_qemu@t-online.de>

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

On Tue, Aug 10, 2021 at 10:35 AM Volker Rümelin <vr_qemu@t-online.de> wrote:

> Commit 584af1f1d9 ("ui/gtk: add a keyboard fifo to the VTE
> consoles") changed the VTE chardev backend code to rely on the
> chr_accept_input() callback function. The code expects a
> chr_accept_input() call whenever qemu_chr_be_can_write() bytes
> were written. It turns out this is wrong. Some chardev
> frontends only call this callback after can_write was 0.
>
> Change the code to send data until the keyboard fifo is empty
> or qemu_chr_be_can_write() returns 0.
>
> Fixes: 584af1f1d9 ("ui/gtk: add a keyboard fifo to the VTE consoles")
> Signed-off-by: Volker Rümelin <vr_qemu@t-online.de>
>

Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>

---
>  ui/gtk.c | 10 ++++------
>  1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/ui/gtk.c b/ui/gtk.c
> index 974e4dfc0b..cfb0728d1f 100644
> --- a/ui/gtk.c
> +++ b/ui/gtk.c
> @@ -1646,16 +1646,14 @@ static void gd_vc_send_chars(VirtualConsole *vc)
>
>      len = qemu_chr_be_can_write(vc->vte.chr);
>      avail = fifo8_num_used(&vc->vte.out_fifo);
> -    if (len > avail) {
> -        len = avail;
> -    }
> -    while (len > 0) {
> +    while (len > 0 && avail > 0) {
>          const uint8_t *buf;
>          uint32_t size;
>
> -        buf = fifo8_pop_buf(&vc->vte.out_fifo, len, &size);
> +        buf = fifo8_pop_buf(&vc->vte.out_fifo, MIN(len, avail), &size);
>          qemu_chr_be_write(vc->vte.chr, (uint8_t *)buf, size);
> -        len -= size;
> +        len = qemu_chr_be_can_write(vc->vte.chr);
> +        avail -= size;
>      }
>  }
>
> --
> 2.26.2
>
>

-- 
Marc-André Lureau

[-- Attachment #2: Type: text/html, Size: 2601 bytes --]

  reply	other threads:[~2021-08-10  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10  6:32 [PATCH for 6.1] ui/gtk: retry sending VTE console input Volker Rümelin
2021-08-10  8:16 ` Marc-André Lureau [this message]
2021-08-10  8:55 ` Gerd Hoffmann

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='CAJ+F1CL0=w8zqyjYp5Av96R=Q1KT2SZt4jB_LrgYPg=xmix_3w@mail.gmail.com' \
    --to=marcandre.lureau@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vr_qemu@t-online.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.