From: Gerd Hoffmann <kraxel@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RfC PATCH 0/4] make display updates thread safe.
Date: Mon, 03 Apr 2017 10:44:00 +0200 [thread overview]
Message-ID: <1491209040.17505.18.camel@redhat.com> (raw)
In-Reply-To: <4ccee8ca-8045-784e-5074-3007d8667238@ilande.co.uk>
Hi,
> I've spent a bit of time over the weekend attempting to convert the
> SPARC CG3/TCX framebuffers over to use your new code and pushed the
> result to my github branch here:
> https://github.com/mcayland/qemu/commits/vga-fixes-sparc.
work/vga-fixes branch updated & rebased to latest master, with your
patches added.
> Using your current git branch, I get an assert() using VGA under
> qemu-system-ppc on startup unless I change the first assert to
> "assert(start >= snap->start)".
>
> I'm also not convinced by the second assert "assert(start + length <
> snap->end)" either. In the example CG3/TCX conversions I ended up having
> to subtract 1 from the size of the region passed to
> memory_region_snapshot_get_dirty() in order to avoid it firing when
> accessing the last scanline which seems wrong. I didn't explicitly add a
> patch to change this to "<=" in my git patchset just in case it broke
> further assumptions in the bitmap code relating to the end address.
Both asserts should use inclusive compare. Added a patch fixing the
other assert too.
> 2) Redraw issues with CG3/TCX after conversion
>
> Despite the conversion from your patches looking reasonably
> straightforward, I still see problems with areas of the screen not
> updating after conversion. I can easily reproduce these locally as follows:
>
> ./qemu-system-sparc -vga cg3 -prom-env 'auto-boot?=false'
> ./qemu-system-sparc -vga tcx -g 1024x768x8 -prom-env 'auto-boot?=false'
> ./qemu-system-sparc -vga tcx -g 1024x768x24 -prom-env 'auto-boot?=false'
Hmm, I have a blank screen only (yellow with cg3, black with tcx).
No openfirmware prompt showing up ...
> Finally on a slightly unrelated note, the TCX driver still has old code
> for 8 and 16 bpp surfaces in QEMU. Am I right in understanding that all
> surfaces in QEMU are now 32-bit and the 8/16 bpp code can be removed?
Yes, that is correct. tcx uses qemu_resize_console() so surfaces will
always be 32bpp.
cheers,
Gerd
next prev parent reply other threads:[~2017-04-03 8:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 6:55 [Qemu-devel] [RfC PATCH 0/4] make display updates thread safe Gerd Hoffmann
2017-03-30 6:55 ` [Qemu-devel] [RfC PATCH 1/4] vga: add vga_scanline_invalidated helper Gerd Hoffmann
2017-03-30 6:55 ` [Qemu-devel] [RfC PATCH 2/4] memory: add support getting and using a dirty bitmap copy Gerd Hoffmann
2017-03-30 15:48 ` Paolo Bonzini
2017-03-31 11:44 ` Paolo Bonzini
2017-03-30 6:55 ` [Qemu-devel] [RfC PATCH 3/4] vga: make display updates thread safe Gerd Hoffmann
2017-03-30 6:55 ` [Qemu-devel] [RfC PATCH 4/4] [testing] console: remove do_safe_dpy_refresh Gerd Hoffmann
2017-03-30 11:14 ` [Qemu-devel] [RfC PATCH 0/4] make display updates thread safe Mark Cave-Ayland
2017-03-30 13:41 ` Gerd Hoffmann
2017-04-03 5:26 ` Mark Cave-Ayland
2017-04-03 8:44 ` Gerd Hoffmann [this message]
2017-04-03 9:18 ` Mark Cave-Ayland
2017-04-03 11:49 ` Paolo Bonzini
2017-04-03 12:03 ` Gerd Hoffmann
2017-04-03 12:24 ` Mark Cave-Ayland
2017-04-03 12:42 ` Gerd Hoffmann
2017-04-03 15:06 ` Mark Cave-Ayland
2017-04-04 6:12 ` Gerd Hoffmann
2017-04-04 7:25 ` Mark Cave-Ayland
2017-04-03 17:02 ` Paolo Bonzini
2017-04-04 6:13 ` 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=1491209040.17505.18.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@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.