From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 49CCEC6787C for ; Fri, 12 Oct 2018 17:24:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 17C59205F4 for ; Fri, 12 Oct 2018 17:24:26 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 17C59205F4 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727832AbeJMA5z (ORCPT ); Fri, 12 Oct 2018 20:57:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43644 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726761AbeJMA5y (ORCPT ); Fri, 12 Oct 2018 20:57:54 -0400 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 7862781DE5; Fri, 12 Oct 2018 17:24:23 +0000 (UTC) Received: from sky.random (ovpn-120-22.rdu2.redhat.com [10.10.120.22]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 0B2BB10027D8; Fri, 12 Oct 2018 17:24:23 +0000 (UTC) Date: Fri, 12 Oct 2018 13:24:22 -0400 From: Andrea Arcangeli To: Zi Yan Cc: jglisse@redhat.com, linux-mm@kvack.org, Andrew Morton , linux-kernel@vger.kernel.org, Greg Kroah-Hartman , "Kirill A . Shutemov" , "H. Peter Anvin" , Anshuman Khandual , Dave Hansen , David Nellans , Ingo Molnar , Mel Gorman , Minchan Kim , Naoya Horiguchi , Thomas Gleixner , Vlastimil Babka , Michal Hocko Subject: Re: [PATCH] mm/thp: fix call to mmu_notifier in set_pmd_migration_entry() Message-ID: <20181012172422.GA7395@redhat.com> References: <20181012160953.5841-1-jglisse@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Fri, 12 Oct 2018 17:24:23 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Fri, Oct 12, 2018 at 12:20:54PM -0400, Zi Yan wrote: > On 12 Oct 2018, at 12:09, jglisse@redhat.com wrote: > > > From: Jérôme Glisse > > > > Inside set_pmd_migration_entry() we are holding page table locks and > > thus we can not sleep so we can not call invalidate_range_start/end() > > > > So remove call to mmu_notifier_invalidate_range_start/end() and add > > call to mmu_notifier_invalidate_range(). Note that we are already Why the call to mmu_notifier_invalidate_range if we're under range_start and followed by range_end? (it's not _range_only_end, if it was _range_only_end the above would be needed) > > calling mmu_notifier_invalidate_range_start/end() inside the function > > calling set_pmd_migration_entry() (see try_to_unmap_one()). > > > > Signed-off-by: Jérôme Glisse > > Reported-by: Andrea Arcangeli > > Cc: Andrew Morton > > Cc: Greg Kroah-Hartman > > Cc: Zi Yan > > Cc: Kirill A. Shutemov > > Cc: "H. Peter Anvin" > > Cc: Anshuman Khandual > > Cc: Dave Hansen > > Cc: David Nellans > > Cc: Ingo Molnar > > Cc: Mel Gorman > > Cc: Minchan Kim > > Cc: Naoya Horiguchi > > Cc: Thomas Gleixner > > Cc: Vlastimil Babka > > Cc: Michal Hocko > > Cc: Andrea Arcangeli > > --- > > mm/huge_memory.c | 7 +------ > > 1 file changed, 1 insertion(+), 6 deletions(-) > > > > diff --git a/mm/huge_memory.c b/mm/huge_memory.c > > index 533f9b00147d..93cb80fe12cb 100644 > > --- a/mm/huge_memory.c > > +++ b/mm/huge_memory.c > > @@ -2885,9 +2885,6 @@ void set_pmd_migration_entry(struct page_vma_mapped_walk *pvmw, > > if (!(pvmw->pmd && !pvmw->pte)) > > return; > > > > - mmu_notifier_invalidate_range_start(mm, address, > > - address + HPAGE_PMD_SIZE); > > - > > flush_cache_range(vma, address, address + HPAGE_PMD_SIZE); > > pmdval = *pvmw->pmd; > > pmdp_invalidate(vma, address, pvmw->pmd); > > @@ -2898,11 +2895,9 @@ void set_pmd_migration_entry(struct page_vma_mapped_walk *pvmw, > > if (pmd_soft_dirty(pmdval)) > > pmdswp = pmd_swp_mksoft_dirty(pmdswp); > > set_pmd_at(mm, address, pvmw->pmd, pmdswp); > > + mmu_notifier_invalidate_range(mm, address, address + HPAGE_PMD_SIZE); It's not obvious why it's needed, if it's needed maybe a comment can be added. > > page_remove_rmap(page, true); > > put_page(page); > > - > > - mmu_notifier_invalidate_range_end(mm, address, > > - address + HPAGE_PMD_SIZE); > > } > > > > void remove_migration_pmd(struct page_vma_mapped_walk *pvmw, struct page *new) > > -- > > 2.17.2 > > Yes, these are the redundant calls to mmu_notifier_invalidate_range_start/end() > in set_pmd_migration_entry(). Thanks for the patch. They're not just redundant, it's called in non blockable path with __mmu_notifier_invalidate_range_start(blockable=true). Furthermore mmu notifier API doesn't support nesting. KVM is actually robust against the nesting: kvm->mmu_notifier_count++; kvm->mmu_notifier_count--; and KVM is always fine with non blockable calls, but that's not universally true for all mmu notifier users. Thanks, Andrea