From: Xudong Hao <xudong.hao@intel.com>
To: xen-devel@lists.xen.org
Cc: xudong.hao@intel.com, haitao.shan@intel.com, keir@xen.org,
xiantao.zhang@intel.com, JBeulich@suse.com
Subject: [PATCH v2 0/4] xen: enable EPT A/D bit feature
Date: Wed, 20 Jun 2012 09:57:43 +0800 [thread overview]
Message-ID: <1340157467-19553-1-git-send-email-xudong.hao@intel.com> (raw)
Changes from v1:
- Move hap_has_dirty_bit and hap_has_access_bit definition from patch 3 to patch2.
- define them as bool_t instead of int.
Extended Page Tables introduce two bit: access bit and dirty bit, A/D bits
enable VMMs to efficiently implement memory management and page classification
algorithms to optimize VM memory operations.
This series of patches enable EPT dirty bit feature for guest live migration.
PATCH 1/4: Add EPT A/D bits definitions.
PATCH 2/4: Add xen parameter to control A/D bits support, it on by default.
PATCH 3/4: Introduce a log_dirty new function update_dirty_bitmap, which will
only update the log dirty bitmap, but won't clear the EPT page dirty bit.
The function is used by live migration peek round with EPT D bit supported.
PATCH 4/4: enable EPT dirty bit for guest live migration.
next reply other threads:[~2012-06-20 1:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 1:57 Xudong Hao [this message]
2012-06-20 1:57 ` [PATCH v2 1/4] xen: Add EPT A/D bits definitions Xudong Hao
2012-06-20 1:57 ` [PATCH v2 2/4] xen: add xen parameter to control A/D bits support Xudong Hao
2012-06-20 1:57 ` [PATCH v2 3/4] xen: introduce new function update_dirty_bitmap Xudong Hao
2012-06-28 13:42 ` Tim Deegan
2012-06-29 8:46 ` Hao, Xudong
2012-06-20 1:57 ` [PATCH v2 4/4] xen: enable EPT dirty bit for guest live migration Xudong Hao
2012-06-28 13:52 ` Tim Deegan
2012-06-29 7:50 ` Hao, Xudong
2012-06-25 6:27 ` [PATCH v2 0/4] xen: enable EPT A/D bit feature Hao, Xudong
2012-06-25 7:22 ` Keir Fraser
2012-06-25 9:02 ` Tim Deegan
2012-06-26 5:31 ` Hao, Xudong
2012-06-28 10:30 ` Tim Deegan
2012-06-29 9:27 ` Hao, Xudong
2012-06-28 12:14 ` George Dunlap
2012-06-29 9:31 ` Hao, Xudong
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=1340157467-19553-1-git-send-email-xudong.hao@intel.com \
--to=xudong.hao@intel.com \
--cc=JBeulich@suse.com \
--cc=haitao.shan@intel.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=xiantao.zhang@intel.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).