From: Thomas Arouge <agentlecomputer@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1802915] Re: GTK display refresh rate is throttled
Date: Sat, 15 Dec 2018 14:50:05 -0000 [thread overview]
Message-ID: <154488540561.1570.2729750501782833146.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 154202828346.10437.1411488850787353605.malonedeb@wampee.canonical.com
Instead of changing the value, I think there should be a function that
determines the ideal "GUI_REFRESH_INTERVAL_DEFAULT" value, with the
option to override it. That way, monitor greater than 60 Hz can also
benefit.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1802915
Title:
GTK display refresh rate is throttled
Status in QEMU:
New
Bug description:
Guest OS running with GL enabled GTK display shows a reduced refresh
rate, e.g. moving cursor around with iGVT-g DMA Buf.
Apparently, a default refresh interval GUI_REFRESH_INTERVAL_DEFAULT
(30ms) is defined in include/ui/console.h, throttling the display
refresh rate at 33Hz.
To correct this throttle issue, a shorter interval (16 or 17
milliseconds) should be applied to display change listener or the
default value should be modified.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1802915/+subscriptions
next prev parent reply other threads:[~2018-12-15 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 13:11 [Qemu-devel] [Bug 1802915] [NEW] GTK display refresh rate is throttled Chen Zhang
2018-11-12 13:17 ` [Qemu-devel] [Bug 1802915] " Chen Zhang
2018-11-13 3:15 ` Chen Zhang
2018-12-15 14:50 ` Thomas Arouge [this message]
2021-05-02 5:52 ` Thomas Huth
2021-07-02 4:17 ` Launchpad Bug Tracker
2021-10-29 7:41 ` Jose Biosca
2021-10-29 16:04 ` Lee Garrett
2021-10-29 16:49 ` Thomas Huth
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=154488540561.1570.2729750501782833146.malone@chaenomeles.canonical.com \
--to=agentlecomputer@gmail.com \
--cc=1802915@bugs.launchpad.net \
--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).