All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoffer Dall <christoffer.dall@linaro.org>
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 11:08:23 +0000	[thread overview]
Message-ID: <20150121110823.GB15076@cbox> (raw)
In-Reply-To: <1421366341-26012-1-git-send-email-m.smarduch@samsung.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Mario Smarduch <m.smarduch@samsung.com>
Cc: marc.zyngier@arm.com, pbonzini@redhat.com,
	james.hogan@imgtec.com, agraf@suse.de, cornelia.huck@de.ibm.com,
	borntraeger@de.ibm.com, catalin.marinas@arm.com,
	steve.capper@arm.com, peter.maydell@linaro.org,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kvm-ppc@vger.kernel.org,
	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 11:08:23 +0000	[thread overview]
Message-ID: <20150121110823.GB15076@cbox> (raw)
In-Reply-To: <1421366341-26012-1-git-send-email-m.smarduch@samsung.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v16 00/10] KVM/arm/arm64/x86: dirty page logging for ARMv7/8 (3.18.0-rc2)
Date: Wed, 21 Jan 2015 12:08:23 +0100	[thread overview]
Message-ID: <20150121110823.GB15076@cbox> (raw)
In-Reply-To: <1421366341-26012-1-git-send-email-m.smarduch@samsung.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Mario Smarduch <m.smarduch@samsung.com>
Cc: marc.zyngier@arm.com, pbonzini@redhat.com,
	james.hogan@imgtec.com, agraf@suse.de, cornelia.huck@de.ibm.com,
	borntraeger@de.ibm.com, catalin.marinas@arm.com,
	steve.capper@arm.com, peter.maydell@linaro.org,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kvm-ppc@vger.kernel.org,
	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 12:08:23 +0100	[thread overview]
Message-ID: <20150121110823.GB15076@cbox> (raw)
In-Reply-To: <1421366341-26012-1-git-send-email-m.smarduch@samsung.com>

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

  reply	other threads:[~2015-01-21 11:08 UTC|newest]

Thread overview: 52+ 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-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-21 11:08 ` Christoffer Dall [this message]
2015-01-21 11:08   ` Christoffer Dall
2015-01-21 11:08   ` Christoffer Dall
2015-01-21 11:08   ` Christoffer Dall
2015-01-21 18:38 ` Mario Smarduch
2015-01-21 18:38   ` Mario Smarduch
2015-01-21 18:38   ` Mario Smarduch
2015-01-21 18:38   ` Mario Smarduch
  -- strict thread matches above, loose matches on Subject: below --
2015-01-15 23:58 [PATCH v16 01/10] KVM: Add architecture-defined TLB flush support Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 [PATCH v16 02/10] KVM: Add generic support for dirty page logging Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 [PATCH v16 03/10] KVM: x86: switch to kvm_get_dirty_log_protect Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 [PATCH v16 04/10] KVM: arm: Add ARMv7 API to flush TLBs Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 [PATCH v16 05/10] KVM: arm: Add initial dirty page locking support Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 [PATCH v16 06/10] KVM: arm: dirty logging write protect support Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 [PATCH v16 07/10] KVM: arm: page logging 2nd stage fault handling Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 [PATCH v16 08/10] KVM: arm64: ARMv8 header changes for page logging Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:58 ` Mario Smarduch
2015-01-15 23:59 [PATCH v16 09/10] KVM: arm64: Add HYP interface to flush VM Stage 1/2 TLB entries Mario Smarduch
2015-01-15 23:59 ` Mario Smarduch
2015-01-15 23:59 ` Mario Smarduch
2015-01-15 23:59 ` Mario Smarduch
2015-01-15 23:59 [PATCH v16 10/10] KVM: arm/arm64: Enable Dirty Page logging for ARMv8 Mario Smarduch
2015-01-15 23:59 ` Mario Smarduch
2015-01-15 23:59 ` Mario Smarduch
2015-01-15 23:59 ` Mario Smarduch

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=20150121110823.GB15076@cbox \
    --to=christoffer.dall@linaro.org \
    --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 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.