From: m.smarduch@samsung.com (Mario Smarduch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 0/6] arm: dirty page logging support for ARMv7
Date: Thu, 28 Aug 2014 12:58:02 -0700 [thread overview]
Message-ID: <53FF89CA.3020608@samsung.com> (raw)
In-Reply-To: <53FF8252.2030304@amd.com>
On 08/28/2014 12:26 PM, Joel Schopp wrote:
>
> On 08/26/2014 06:51 PM, Mario Smarduch wrote:
>> This patch adds support for ARMv7 dirty page logging. Some functions
>> of dirty
>> page logging have been split to generic and arch specific
>> implementations,
>> details below. Dirty page logging is one of serveral features required
>> for
>> live migration, live migration has been tested for ARMv7.
> Any reason not to cc the kvm arm list? I almost missed this patch set.
> kvmarm at lists.cs.columbia.edu
All previous series were copied to kvm arm list.
This time around email sever setup caused some problems,
including this and few others.
Sorry about that.
- Mario
WARNING: multiple messages have this Message-ID (diff)
From: Mario Smarduch <m.smarduch@samsung.com>
To: Joel Schopp <joel.schopp@amd.com>
Cc: christoffer.dall@linaro.org, marc.zyngier@arm.com,
pbonzini@redhat.com, ralf@linux-mips.org, gleb@kernel.org,
agraf@suse.de, borntraeger@de.ibm.com, cornelia.huck@de.ibm.com,
xiaoguangrong@linux.vnet.ibm.com, steve.capper@arm.com,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [PATCH v10 0/6] arm: dirty page logging support for ARMv7
Date: Thu, 28 Aug 2014 12:58:02 -0700 [thread overview]
Message-ID: <53FF89CA.3020608@samsung.com> (raw)
In-Reply-To: <53FF8252.2030304@amd.com>
On 08/28/2014 12:26 PM, Joel Schopp wrote:
>
> On 08/26/2014 06:51 PM, Mario Smarduch wrote:
>> This patch adds support for ARMv7 dirty page logging. Some functions
>> of dirty
>> page logging have been split to generic and arch specific
>> implementations,
>> details below. Dirty page logging is one of serveral features required
>> for
>> live migration, live migration has been tested for ARMv7.
> Any reason not to cc the kvm arm list? I almost missed this patch set.
> kvmarm@lists.cs.columbia.edu
All previous series were copied to kvm arm list.
This time around email sever setup caused some problems,
including this and few others.
Sorry about that.
- Mario
next prev parent reply other threads:[~2014-08-28 19:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 23:51 [PATCH v10 0/6] arm: dirty page logging support for ARMv7 Mario Smarduch
2014-08-26 23:51 ` Mario Smarduch
2014-08-26 23:51 ` [PATCH v10 1/6] KVM: Add architecture-specific TLB flush implementations Mario Smarduch
2014-08-26 23:51 ` Mario Smarduch
2014-08-26 23:51 ` [PATCH v10 2/6] KVM: Add generic implementation of kvm_vm_ioctl_get_dirty_log Mario Smarduch
2014-08-26 23:51 ` Mario Smarduch
2014-08-26 23:51 ` [PATCH v10 3/6] arm: KVM: Add ARMv7 API to flush TLBs Mario Smarduch
2014-08-26 23:51 ` Mario Smarduch
2014-08-26 23:51 ` [PATCH v10 4/6] arm: KVM: Add initial dirty page locking infrastructure Mario Smarduch
2014-08-26 23:51 ` Mario Smarduch
2014-08-28 19:26 ` [PATCH v10 0/6] arm: dirty page logging support for ARMv7 Joel Schopp
2014-08-28 19:26 ` Joel Schopp
2014-08-28 19:58 ` Mario Smarduch [this message]
2014-08-28 19:58 ` 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=53FF89CA.3020608@samsung.com \
--to=m.smarduch@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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.