From: Mario Smarduch <m.smarduch@samsung.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: marc.zyngier@arm.com, pbonzini@redhat.com,
catalin.marinas@arm.com, kvmarm@lists.cs.columbia.edu,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] KVM: arm/arm64: Enable Dirty Page logging for ARMv8
Date: Mon, 24 Nov 2014 13:22:16 -0800 [thread overview]
Message-ID: <5473A188.4030709@samsung.com> (raw)
In-Reply-To: <20141122200254.GS3401@cbox>
On 11/22/2014 12:02 PM, Christoffer Dall wrote:
> On Sat, Nov 15, 2014 at 12:19:10AM -0800, m.smarduch@samsung.com wrote:
>> From: Mario Smarduch <m.smarduch@samsung.com>
>>
>> This patch enables ARMv8 ditry page logging support. Plugs ARMv8 into generic
>> layer through Kconfig symbol, and drops earlier ARM64 constraints to enable
>> logging at architecture layer.
>>
>> Signed-off-by: Mario Smarduch <m.smarduch@samsung.com>
>
> Just reminding you again of what I said in the previous thread (think
> that was before you sent this out), that you need to handle the pud_huge
> case in arch/arm/kvm/mmu.c for ARMv8 here.
>
> -Christoffer
>
Yes, so like similar handling to what unmap_puds() does when
it encounters a PUD Block?
Should next revision be rebased to 'queued' 3.18.0-rc2?
Thanks.
next prev parent reply other threads:[~2014-11-24 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 8:19 [PATCH v2 0/3] arm/arm64: Add dirty page logging for ARMv8 (3.17.0-rc1) m.smarduch
2014-11-15 8:19 ` [PATCH v2 1/3] KVM: arm64: ARMv8 header changes for page logging m.smarduch
2014-11-22 20:01 ` Christoffer Dall
2014-11-15 8:19 ` [PATCH v2 2/3] KVM: arm64: Add HYP interface to flush VM TLB entires m.smarduch
2014-11-15 8:19 ` [PATCH v2 3/3] KVM: arm/arm64: Enable Dirty Page logging for ARMv8 m.smarduch
2014-11-22 20:02 ` Christoffer Dall
2014-11-24 21:22 ` Mario Smarduch [this message]
2014-11-25 11:10 ` Christoffer Dall
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=5473A188.4030709@samsung.com \
--to=m.smarduch@samsung.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.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