From: Mario Smarduch <m.smarduch@samsung.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH v16 00/10] KVM/arm/arm64/x86: dirty page logging for ARMv7/8 (3.18.0-rc2)
Date: Wed, 21 Jan 2015 18:38:50 +0000 [thread overview]
Message-ID: <54BFF23A.30205@samsung.com> (raw)
In-Reply-To: <1421366341-26012-1-git-send-email-m.smarduch@samsung.com>
On 01/21/2015 03:08 AM, Christoffer Dall wrote:
> On Thu, Jan 15, 2015 at 03:58:51PM -0800, Mario Smarduch wrote:
>> Patch series adds support for armv7/8 dirty page logging. As we move
>> towards generic dirty page logging interface we move some common code to
>> generic layer shared by x86, armv7 and armv8.
>>
>> armv7/8 Dirty page logging implementation overivew-
>> - initially write protects memory region 2nd stage page tables
>> - read dirty page log and again write protect dirty pages for next pass.
>> - second stage huge pages are dissolved into normal pages to keep track of
>> dirty memory at page granularity. Tracking at huge page granularity
>> limits granularity of marking dirty memory and migration to a light memory
>> load. Small page size logging supports higher memory dirty rates, enables
>> rapid migration.
>>
>> armv7 supports 2MB Huge page, and armv8 supports 2MB (4kb) and
>> 512MB (64kb)
>> - In the event migration is canceled, normal behavior is resumed huge pages
>> are rebuilt over time.
>>
>
> Thanks, applied.
>
> -Christoffer
>
Thanks! And also to other folks that helped along the way
in shaping the design and reviews.
- Mario
prev parent reply other threads:[~2015-01-21 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 23:58 [PATCH v16 00/10] KVM/arm/arm64/x86: dirty page logging for ARMv7/8 (3.18.0-rc2) Mario Smarduch
2015-01-21 11:08 ` Christoffer Dall
2015-01-21 18:38 ` Mario Smarduch [this message]
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=54BFF23A.30205@samsung.com \
--to=m.smarduch@samsung.com \
--cc=kvm-ia64@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).