From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH -mm v8 5/7] mmu-notifier: add clear_young callback Date: Thu, 16 Jul 2015 13:35:02 +0200 Message-ID: <55A796E6.3090603@redhat.com> References: <82693bd5b5dbf4e65657fa22288942650aa04a0a.1436967694.git.vdavydov@parallels.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: owner-linux-mm@kvack.org To: Andres Lagar-Cavilla , Vladimir Davydov , kvm@vger.kernel.org, Eric Northup Cc: Andrew Morton , Minchan Kim , Raghavendra K T , Johannes Weiner , Michal Hocko , Greg Thelen , Michel Lespinasse , David Rientjes , Pavel Emelyanov , Cyrill Gorcunov , Jonathan Corbet , linux-api@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-api@vger.kernel.org On 15/07/2015 21:16, Andres Lagar-Cavilla wrote: >> > +static int kvm_mmu_notifier_clear_young(struct mmu_notifier *mn, >> > + struct mm_struct *mm, >> > + unsigned long start, >> > + unsigned long end) >> > +{ >> > + struct kvm *kvm = mmu_notifier_to_kvm(mn); >> > + int young, idx; > For reclaim, the clear_flush_young notifier may blow up the secondary > pte to estimate the access pattern, depending on hardware support (EPT > access bits available in Haswell onwards, not sure about AMD, PPC, > etc). It seems like this problem is limited to pre-Haswell EPT. I'm okay with the patch. If we find problems later we can always add a parameter to kvm_age_hva so that it effectively doesn't do anything on clear_young. Acked-by: Paolo Bonzini Paolo -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org