From: Gerd Hoffmann <kraxel@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [RfC PATCH 0/4] make display updates thread safe.
Date: Thu, 30 Mar 2017 15:41:55 +0200 [thread overview]
Message-ID: <1490881315.28523.11.camel@redhat.com> (raw)
In-Reply-To: <e1ccd5bc-f683-93b7-374d-0707765a8715@ilande.co.uk>
Hi,
> Excellent! I can help out with converting and/or testing the SPARC
> devices (cg3/tcx) if required.
Sure, test results and patches are very welcome.
I've touched dirty bitmap code for the first time, so I've sent out this
rfc for early feedback at the approach taken before going out converting
more display drivers. Seems nobody found patch #2 horrible so far, I
take that as good sign that we can go on with this draft API.
> Out of interest, from your work do you have a rough estimate as to how
> this affects guest performance? For example benchmarks with Jan's
> original commit to reduce the locking vs. Alex's current workaround vs.
> with this patchset applied?
I expect this improves performance with mttcg because the locking goes
away, which allows more concurrency, probably more visible with more
guest cores. Didn't benchmark it though.
cheers,
Gerd
next prev parent reply other threads:[~2017-03-30 13:42 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 [this message]
2017-04-03 5:26 ` Mark Cave-Ayland
2017-04-03 8:44 ` Gerd Hoffmann
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=1490881315.28523.11.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 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).