From: Mario Smarduch <m.smarduch@samsung.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: kvmarm@lists.cs.columbia.edu, marc.zyngier@arm.com,
xiaoguangrong@linux.vnet.ibm.com, steve.capper@arm.com,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
gavin.guo@canonical.com, peter.maydell@linaro.org,
jays.lee@samsung.com, sungjinn.chung@samsung.com
Subject: Re: [RESEND PATCH v7 3/4] arm: dirty log write protect management support
Date: Tue, 10 Jun 2014 11:08:24 -0700 [thread overview]
Message-ID: <53974998.70001@samsung.com> (raw)
In-Reply-To: <20140610092240.GF1388@lvm>
On 06/10/2014 02:22 AM, Christoffer Dall wrote:
> On Mon, Jun 09, 2014 at 06:47:12PM -0700, Mario Smarduch wrote:
>> On 06/08/2014 05:05 AM, Christoffer Dall wrote:
>>> On Fri, Jun 06, 2014 at 10:33:41AM -0700, Mario Smarduch wrote:
>>>> kvm_vm_ioctl_get_dirty_log() is generic used by x86, ARM. x86 recent patch
>>>> changed this function, this patch picks up those changes, re-tested everything
>>>> works. Applies cleanly with other patches.
>>>>
>>>> This patch adds support for keeping track of VM dirty pages. As dirty page log
>>>> is retrieved, the pages that have been written are write protected again for
>>>> next write and log read.
>>>>
>>>> Signed-off-by: Mario Smarduch <m.smarduch@samsung.com>
>>>> ---
>>>> arch/arm/include/asm/kvm_host.h | 3 ++
>>>> arch/arm/kvm/arm.c | 5 ---
>>>> arch/arm/kvm/mmu.c | 79 +++++++++++++++++++++++++++++++++++
>>>> arch/x86/kvm/x86.c | 86 ---------------------------------------
>>>> virt/kvm/kvm_main.c | 86 +++++++++++++++++++++++++++++++++++++++
>>>> 5 files changed, 168 insertions(+), 91 deletions(-)
>>>>
>>>> diff --git a/arch/arm/include/asm/kvm_host.h b/arch/arm/include/asm/kvm_host.h
>>>> index 59565f5..b760f9c 100644
>>>> --- a/arch/arm/include/asm/kvm_host.h
>>>> +++ b/arch/arm/include/asm/kvm_host.h
>>>> @@ -232,5 +232,8 @@ u64 kvm_arm_timer_get_reg(struct kvm_vcpu *, u64 regid);
>>>> int kvm_arm_timer_set_reg(struct kvm_vcpu *, u64 regid, u64 value);
>>>>
>>>> void kvm_mmu_wp_memory_region(struct kvm *kvm, int slot);
>>>> +void kvm_mmu_write_protect_pt_masked(struct kvm *kvm,
>>>> + struct kvm_memory_slot *slot,
>>>> + gfn_t gfn_offset, unsigned long mask);
>>>
>>> Do all other architectures implement this function? arm64?
>>
>> Besides arm, x86 but the function is not generic.
>>>
>
> you're now calling this from generic code, so all architecture must
> implement it, and the prototype should proably be in
> include/linux/kvm_host.h, not in the arch-specific headers.
Ah ok.
>
>>>>
>>>> #endif /* __ARM_KVM_HOST_H__ */
>>>> diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
>>>> index dfd63ac..f06fb21 100644
>>>> --- a/arch/arm/kvm/arm.c
>>>> +++ b/arch/arm/kvm/arm.c
>>>> @@ -780,11 +780,6 @@ long kvm_arch_vcpu_ioctl(struct file *filp,
>>>> }
>>>> }
>>>>
>>>> -int kvm_vm_ioctl_get_dirty_log(struct kvm *kvm, struct kvm_dirty_log *log)
>>>> -{
>>>> - return -EINVAL;
>>>> -}
>>>> -
>>>
>>> What about the other architectures implementing this function?
>>
>> Six architectures define this function. With this patch this
>> function is generic in kvm_main.c used by x86.
>
> But you're not defining it as a weak symbol (and I don't suspect that
> you should unless other archs do this in a *very* different way), so you
> need to either remove it from the other archs, make it a weak symbol (I
> hope this is not the case) or do something else.
Mistake on my part I just cut and paste Xiaos x86's recent upstream patch and
didn't add weak definition.
I looked at IA64, MIPS (two of them ), S390 somewhat similar but quite
different implementations. They use a sync version, where the dirty bitmaps
are maintained at arch level and then copied to memslot->dirty_bitmap. There
is only commonality between x86 and ARM right now, x86 uses
memslot->dirty_bitmap directly.
Maybe this function should go back to architecture layer, it's
unlikely it can become generic across all architectures.
There is also the issue of kvm_flush_remote_tlbs(), that's also weak,
the generic one is using IPIs. Since it's only used in mmu.c maybe make
this one static.
>
> -Christoffer
>
next prev parent reply other threads:[~2014-06-10 18:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 23:19 [PATCH v7 0/4] arm: dirty page logging support for ARMv7 Mario Smarduch
2014-06-03 23:19 ` [PATCH v7 1/4] arm: add ARMv7 HYP API to flush VM TLBs without address param Mario Smarduch
2014-06-08 12:05 ` Christoffer Dall
2014-06-09 17:06 ` Mario Smarduch
2014-06-09 17:49 ` Christoffer Dall
2014-06-09 18:36 ` Mario Smarduch
2014-06-03 23:19 ` [PATCH v7 2/4] arm: dirty page logging inital mem region write protect (w/no huge PUD support) Mario Smarduch
2014-06-08 12:05 ` Christoffer Dall
2014-06-09 17:58 ` Mario Smarduch
2014-06-09 18:09 ` Christoffer Dall
2014-06-09 18:33 ` Mario Smarduch
2014-06-03 23:19 ` [PATCH v7 3/4] arm: dirty log write protect management support Mario Smarduch
2014-06-03 23:19 ` [PATCH v7 4/4] arm: dirty page logging 2nd stage page fault handling support Mario Smarduch
2014-06-08 12:05 ` Christoffer Dall
2014-06-10 18:23 ` Mario Smarduch
2014-06-11 6:58 ` Christoffer Dall
2014-06-12 2:53 ` Mario Smarduch
2014-06-06 17:33 ` [RESEND PATCH v7 3/4] arm: dirty log write protect management support Mario Smarduch
2014-06-08 12:05 ` Christoffer Dall
2014-06-10 1:47 ` Mario Smarduch
2014-06-10 9:22 ` Christoffer Dall
2014-06-10 18:08 ` Mario Smarduch [this message]
2014-06-11 7:03 ` Christoffer Dall
2014-06-12 3:02 ` Mario Smarduch
2014-06-18 1:41 ` Mario Smarduch
2014-07-03 15:04 ` Christoffer Dall
2014-07-04 16:29 ` Paolo Bonzini
2014-07-17 16:00 ` Mario Smarduch
2014-07-17 16:17 ` Mario Smarduch
2014-06-08 10:45 ` [PATCH v7 0/4] arm: dirty page logging support for ARMv7 Christoffer Dall
2014-06-09 17:02 ` Mario Smarduch
-- strict thread matches above, loose matches on Subject: below --
2014-06-04 21:11 [RESEND PATCH v7 3/4] arm: dirty log write protect management support Mario Smarduch
2014-06-05 6:55 ` Xiao Guangrong
2014-06-05 19:09 ` Mario Smarduch
2014-06-06 5:52 ` Xiao Guangrong
2014-06-06 17:36 ` 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=53974998.70001@samsung.com \
--to=m.smarduch@samsung.com \
--cc=christoffer.dall@linaro.org \
--cc=gavin.guo@canonical.com \
--cc=jays.lee@samsung.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=peter.maydell@linaro.org \
--cc=steve.capper@arm.com \
--cc=sungjinn.chung@samsung.com \
--cc=xiaoguangrong@linux.vnet.ibm.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