From: <anthony.perard@citrix.com>
To: QEMU-devel <qemu-devel@nongnu.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Alexander Graf <agraf@suse.de>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Xen Devel <xen-devel@lists.xensource.com>
Subject: [Qemu-devel] [PATCH V3 0/2] Xen VGA dirtybit support
Date: Tue, 24 May 2011 14:34:19 +0100 [thread overview]
Message-ID: <1306244061-18503-1-git-send-email-anthony.perard@citrix.com> (raw)
From: Anthony PERARD <anthony.perard@citrix.com>
Hi,
This two patches provides the support for sync dirty bitmap, especially useful
for the VGA output. The sync dirty bitmap is not provided for Xen 3.3.
Change v2 -> v3:
* use the new log_dirty parameter of set_memory clients.
* fix some mistakes related to the use of TARGET_PAGE_MASK and
TARGET_PAGE_ALIGN macro in xen_client_set_memory.
* The patch that provide log_start/log_stop in CPUPhysMemoryClient as already
been applied.
Change v1 -> v2:
* Introduce a patch to put log_start/log_stop in CPUPhysMemoryClient;
* There are now only one function to get/check for old physmapping
(get_physmapping);
* The function xen_sync_dirty_bitmap only do a sync on range that are
physmapped and only on one range;
* Physmapping list and CPUPhysMemoryClient is now in XenIOState structure;
* Introduce log_for_dirtybit that hold the range for dirty bit tracking.
Anthony PERARD (2):
xen: Add xc_domain_add_to_physmap to xen_interface.
xen: Introduce VGA sync dirty bitmap support
configure | 29 ++++++-
hw/xen_common.h | 14 +++
trace-events | 1 +
xen-all.c | 267 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
4 files changed, 310 insertions(+), 1 deletions(-)
--
1.7.2.5
next reply other threads:[~2011-05-24 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 13:34 anthony.perard [this message]
2011-05-24 13:34 ` [Qemu-devel] [PATCH V3 1/2] xen: Add xc_domain_add_to_physmap to xen_interface anthony.perard
2011-05-24 13:34 ` [Qemu-devel] [PATCH V3 2/2] xen: Introduce VGA sync dirty bitmap support anthony.perard
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=1306244061-18503-1-git-send-email-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).