From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND v15 10/10] KVM: arm/arm64: Enable Dirty Page logging for ARMv8
Date: Sun, 11 Jan 2015 15:03:27 +0100 [thread overview]
Message-ID: <20150111140327.GY21092@cbox> (raw)
In-Reply-To: <1420767727-20851-2-git-send-email-m.smarduch@samsung.com>
On Thu, Jan 08, 2015 at 05:42:07PM -0800, Mario Smarduch wrote:
> This patch enables ARMv8 dirty page logging support. Plugs ARMv8 into generic
> layer through Kconfig symbol, and drops earlier ARM64 constraints to enable
> logging at architecture layer. I applies cleanly on top patches series
> posted Dec 15:
> https://lists.cs.columbia.edu/pipermail/kvmarm/2014-December/012826.html
>
> Patch number #11 of the series has be dropped.
Again, the stuff about where this applied and other information related
to the series should go below the '---' markers.
I suggest we iterate on patch 07 and make sure we agree, and then you
send out a complete new series (collect the acks and reviewed-by's in
there please), so I know I'll end up picking the right patches, as this
whole series has sort of sprawled.
>
> Signed-off-by: Mario Smarduch <m.smarduch@samsung.com>
Otherwise:
Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
Thanks,
-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,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND v15 10/10] KVM: arm/arm64: Enable Dirty Page logging for ARMv8
Date: Sun, 11 Jan 2015 15:03:27 +0100 [thread overview]
Message-ID: <20150111140327.GY21092@cbox> (raw)
In-Reply-To: <1420767727-20851-2-git-send-email-m.smarduch@samsung.com>
On Thu, Jan 08, 2015 at 05:42:07PM -0800, Mario Smarduch wrote:
> This patch enables ARMv8 dirty page logging support. Plugs ARMv8 into generic
> layer through Kconfig symbol, and drops earlier ARM64 constraints to enable
> logging at architecture layer. I applies cleanly on top patches series
> posted Dec 15:
> https://lists.cs.columbia.edu/pipermail/kvmarm/2014-December/012826.html
>
> Patch number #11 of the series has be dropped.
Again, the stuff about where this applied and other information related
to the series should go below the '---' markers.
I suggest we iterate on patch 07 and make sure we agree, and then you
send out a complete new series (collect the acks and reviewed-by's in
there please), so I know I'll end up picking the right patches, as this
whole series has sort of sprawled.
>
> Signed-off-by: Mario Smarduch <m.smarduch@samsung.com>
Otherwise:
Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
Thanks,
-Christoffer
next prev parent reply other threads:[~2015-01-11 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 1:42 [PATCH RESEND v15 07/10] KVM: arm: page logging 2nd stage fault handling Mario Smarduch
2015-01-09 1:42 ` Mario Smarduch
2015-01-09 1:42 ` [PATCH RESEND v15 10/10] KVM: arm/arm64: Enable Dirty Page logging for ARMv8 Mario Smarduch
2015-01-09 1:42 ` Mario Smarduch
2015-01-11 14:03 ` Christoffer Dall [this message]
2015-01-11 14:03 ` Christoffer Dall
2015-01-12 16:29 ` Mario Smarduch
2015-01-12 16:29 ` 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=20150111140327.GY21092@cbox \
--to=christoffer.dall@linaro.org \
--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.