From: Peter Xu <peterx@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: "Juraj Marcin" <jmarcin@redhat.com>,
qemu-devel@nongnu.org, kraxel@redhat.com,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH] ui/vnc: Update display update interval when VM state changes to RUNNING
Date: Wed, 11 Jun 2025 09:13:32 -0400 [thread overview]
Message-ID: <aEmA_NE9GWfTx97m@x1.local> (raw)
In-Reply-To: <CAMxuvaxTKMEVHOQyjcyWFw=+LbyfbFJgMb4ZfSjkiT-VJsjAWw@mail.gmail.com>
On Wed, Jun 11, 2025 at 04:41:21PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Wed, Jun 11, 2025 at 4:34 PM Peter Xu <peterx@redhat.com> wrote:
>
> > On Wed, May 21, 2025 at 05:16:13PM +0200, Juraj Marcin wrote:
> > > From: Juraj Marcin <jmarcin@redhat.com>
> > >
> > > If a virtual machine is paused for an extended period time, for example,
> > > due to an incoming migration, there are also no changes on the screen.
> > > VNC in such case increases the display update interval by
> > > VNC_REFRESH_INTERVAL_INC (50 ms). The update interval can then grow up
> > > to VNC_REFRESH_INTERVAL_MAX (3000 ms).
> > >
> > > When the machine resumes, it can then take up to 3 seconds for the first
> > > display update. Furthermore, the update interval is then halved with
> > > each display update with changes on the screen. If there are moving
> > > elements on the screen, such as a video, this can be perceived as
> > > freezing and stuttering for few seconds before the movement is smooth
> > > again.
> > >
> > > This patch resolves this issue, by adding a listener to VM state changes
> > > and changing the update interval when the VM state changes to RUNNING.
> > > The update_displaychangelistener() function updates the internal timer,
> > > and the display is refreshed immediately if the timer is expired.
> > >
> > > Signed-off-by: Juraj Marcin <jmarcin@redhat.com>
> >
> > [add Dan]
> >
> > Ping - anyone is willing to pick this one up?
> >
>
> I haven't started gathering pending UI patches. Feel free to pick it up
I'm queuing it for migration if no one beats me to it. Thanks!
--
Peter Xu
prev parent reply other threads:[~2025-06-11 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 15:16 [PATCH] ui/vnc: Update display update interval when VM state changes to RUNNING Juraj Marcin
2025-05-21 15:28 ` Daniel P. Berrangé
2025-05-21 16:04 ` Peter Xu
2025-05-22 9:04 ` Juraj Marcin
2025-05-27 18:04 ` Marc-André Lureau
2025-06-11 12:34 ` Peter Xu
2025-06-11 12:41 ` Marc-André Lureau
2025-06-11 13:13 ` Peter Xu [this message]
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=aEmA_NE9GWfTx97m@x1.local \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=jmarcin@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@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 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.