From: Carwyn Ellis <carwynellis@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Carwyn Ellis <carwynellis@gmail.com>
Subject: [PATCH v3 0/2] use trace events and fix garbled output
Date: Sun, 6 Feb 2022 18:39:54 +0000 [thread overview]
Message-ID: <20220206183956.10694-1-carwynellis@gmail.com> (raw)
This patchset supersedes earlier submissions and incorporates feedback
from Laurent Vivier, Gerd Hoffmann and Philippe Mathieu-Daudé.
There are two patches addressing the following in the vmware vga display
code
- use of fprintf to log debug output to STDERR
This has been replaced with trace events.
- garbled display due to lost display updates
This prevents an issue that can cause garbled display output when
a high number of screen updates are being requested.
The queue is now flushed when it reaches capacity.
The code traversing the queue when updates are being applied to the
display has also been simplified, since we always start the traversal
at the beginning of the queue to ensure that all updates are applied.
Carwyn Ellis (2):
hw/display/vmware_vga: replace fprintf calls with trace events
hw/display/vmware_vga: do not discard screen updates
hw/display/trace-events | 4 +++
hw/display/vmware_vga.c | 71 ++++++++++++++++++++++++-----------------
2 files changed, 45 insertions(+), 30 deletions(-)
--
2.35.1
next reply other threads:[~2022-02-06 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 18:39 Carwyn Ellis [this message]
2022-02-06 18:39 ` [PATCH v3 1/2] hw/display/vmware_vga: replace fprintf calls with trace events Carwyn Ellis
2022-02-06 21:13 ` Philippe Mathieu-Daudé via
2022-02-06 18:39 ` [PATCH v3 2/2] hw/display/vmware_vga: do not discard screen updates Carwyn Ellis
2022-04-10 16:49 ` Carwyn Ellis
2022-04-22 10:40 ` Gerd Hoffmann
2022-04-22 10:42 ` Carwyn Ellis
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=20220206183956.10694-1-carwynellis@gmail.com \
--to=carwynellis@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).