From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH 00/10] make display updates thread safe.
Date: Tue, 4 Apr 2017 12:23:05 +0200 [thread overview]
Message-ID: <20170404102315.24923-1-kraxel@redhat.com> (raw)
Hi,
Second round. Helper API should be solid now, after patch discussions
and initial testing. API is documented now in the header file.
Additionally to vga the sparc display adapters (cg3, tcx) are converted
too. Still quite some work until we've got them all converted. Still
enough progress that I think posting the new revision is useful.
cheers,
Gerd
Gerd Hoffmann (5):
bitmap: add bitmap_copy_and_clear_atomic
memory: add support getting and using a dirty bitmap copy.
vga: add vga_scanline_invalidated helper
vga: make display updates thread safe.
[testing] console: remove do_safe_dpy_refresh
Mark Cave-Ayland (5):
cg3: remove TARGET_PAGE_SIZE rounding on dirty page detection
cg3: fix up size parameter for memory_region_get_dirty()
cg3: make display updates thread safe
tcx: introduce tcx_check_dirty() function
tcx: make display updates thread safe
include/exec/memory.h | 47 +++++++++++++++++++++++++++
include/exec/ram_addr.h | 7 ++++
include/qemu/bitmap.h | 2 ++
include/qemu/typedefs.h | 1 +
exec.c | 75 ++++++++++++++++++++++++++++++++++++++++++
hw/display/cg3.c | 40 +++++++++++------------
hw/display/tcx.c | 86 ++++++++++++++++++-------------------------------
hw/display/vga.c | 50 +++++++++++++++-------------
memory.c | 17 ++++++++++
ui/console.c | 25 +-------------
util/bitmap.c | 11 +++++++
11 files changed, 241 insertions(+), 120 deletions(-)
--
2.9.3
next reply other threads:[~2017-04-04 10:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 10:23 Gerd Hoffmann [this message]
2017-04-04 10:23 ` [Qemu-devel] [PATCH 01/10] bitmap: add bitmap_copy_and_clear_atomic Gerd Hoffmann
2017-04-04 10:23 ` [Qemu-devel] [PATCH 02/10] memory: add support getting and using a dirty bitmap copy Gerd Hoffmann
2017-04-04 10:29 ` Paolo Bonzini
2017-04-04 10:23 ` [Qemu-devel] [PATCH 03/10] vga: add vga_scanline_invalidated helper Gerd Hoffmann
2017-04-15 10:39 ` Richard Henderson
2017-04-18 9:23 ` Gerd Hoffmann
2017-04-04 10:23 ` [Qemu-devel] [PATCH 04/10] vga: make display updates thread safe Gerd Hoffmann
2017-04-04 10:23 ` [Qemu-devel] [PATCH 05/10] cg3: remove TARGET_PAGE_SIZE rounding on dirty page detection Gerd Hoffmann
2017-04-04 10:23 ` [Qemu-devel] [PATCH 06/10] cg3: fix up size parameter for memory_region_get_dirty() Gerd Hoffmann
2017-04-04 12:32 ` Mark Cave-Ayland
2017-04-04 10:23 ` [Qemu-devel] [PATCH 07/10] cg3: make display updates thread safe Gerd Hoffmann
2017-04-04 10:23 ` [Qemu-devel] [PATCH 08/10] tcx: introduce tcx_check_dirty() function Gerd Hoffmann
2017-04-04 10:23 ` [Qemu-devel] [PATCH 09/10] tcx: make display updates thread safe Gerd Hoffmann
2017-04-04 12:43 ` Mark Cave-Ayland
2017-04-04 10:23 ` [Qemu-devel] [PATCH 10/10] [testing] console: remove do_safe_dpy_refresh Gerd Hoffmann
2017-04-04 12:54 ` [Qemu-devel] [PATCH 00/10] make display updates thread safe Mark Cave-Ayland
2017-04-05 8:33 ` Mark Cave-Ayland
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=20170404102315.24923-1-kraxel@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.