From: Mario Smarduch <m.smarduch@samsung.com>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Cc: peter.maydell@linaro.org, kvm@vger.kernel.org,
steve.capper@arm.com, marc.zyngier@arm.com,
gavin.guo@canonical.com, christoffer.dall@linaro.org,
jays.lee@samsung.com, sungjinn.chung@samsung.com,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH v7 3/4] arm: dirty log write protect management support
Date: Thu, 05 Jun 2014 12:09:03 -0700 [thread overview]
Message-ID: <5390C04F.6060201@samsung.com> (raw)
In-Reply-To: <5390146F.8020407@linux.vnet.ibm.com>
On 06/04/2014 11:55 PM, Xiao Guangrong wrote:
> On 06/05/2014 05:11 AM, Mario Smarduch wrote:
>
>> + spin_lock(&kvm->mmu_lock);
>> +
>> + for (i = 0; i < n / sizeof(long); i++) {
>> + unsigned long mask;
>> + gfn_t offset;
>> +
>> + if (!dirty_bitmap[i])
>> + continue;
>> +
>> + is_dirty = true;
>> +
>> + mask = xchg(&dirty_bitmap[i], 0);
>> + dirty_bitmap_buffer[i] = mask;
>> +
>> + offset = i * BITS_PER_LONG;
>> + kvm_mmu_write_protect_pt_masked(kvm, memslot, offset, mask);
>> + }
>> + if (is_dirty)
>> + kvm_flush_remote_tlbs(kvm);
>
> You moved the flush into mmu-lock. Please do not :).
>
> See commit 198c74f43f0f5473f99967aead30ddc622804bc1
>
Thanks for reviewing, I revised to pick up your version.
Functionally there should be no impact on ARM, the
TLB flush function is different.
- Mario
next prev parent reply other threads:[~2014-06-05 19:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2014-06-06 5:52 ` Xiao Guangrong
2014-06-06 17:36 ` Mario Smarduch
-- strict thread matches above, loose matches on Subject: below --
2014-06-03 23:19 [PATCH v7 0/4] arm: dirty page logging support for ARMv7 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
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
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=5390C04F.6060201@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