From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752986AbbE0Odv (ORCPT ); Wed, 27 May 2015 10:33:51 -0400 Received: from mail-qk0-f175.google.com ([209.85.220.175]:33063 "EHLO mail-qk0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751754AbbE0Odt (ORCPT ); Wed, 27 May 2015 10:33:49 -0400 Date: Wed, 27 May 2015 10:33:43 -0400 From: Jerome Glisse To: "Aneesh Kumar K.V" Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Linus Torvalds , joro@8bytes.org, Mel Gorman , "H. Peter Anvin" , Peter Zijlstra , Andrea Arcangeli , Johannes Weiner , Larry Woodman , Rik van Riel , Dave Airlie , Brendan Conoboy , Joe Donohue , Duncan Poole , Sherry Cheung , Subhash Gutti , John Hubbard , Mark Hairgrove , Lucien Dunning , Cameron Buschardt , Arvind Gopalakrishnan , Haggai Eran , Shachar Raindel , Liran Liss , Roland Dreier , Ben Sander , Greg Stoner , John Bridgman , Michael Mantor , Paul Blinzer , Laurent Morichetti , Alexander Deucher , Oded Gabbay , =?iso-8859-1?B?Suly9G1l?= Glisse Subject: Re: [PATCH 03/36] mmu_notifier: pass page pointer to mmu_notifier_invalidate_page() Message-ID: <20150527143342.GB1948@gmail.com> References: <1432236705-4209-1-git-send-email-j.glisse@gmail.com> <1432236705-4209-4-git-send-email-j.glisse@gmail.com> <87wpzulhtz.fsf@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87wpzulhtz.fsf@linux.vnet.ibm.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 27, 2015 at 10:47:44AM +0530, Aneesh Kumar K.V wrote: > j.glisse@gmail.com writes: > > > From: Jérôme Glisse > > > > Listener of mm event might not have easy way to get the struct page > > behind and address invalidated with mmu_notifier_invalidate_page() > > function as this happens after the cpu page table have been clear/ > > updated. This happens for instance if the listener is storing a dma > > mapping inside its secondary page table. To avoid complex reverse > > dma mapping lookup just pass along a pointer to the page being > > invalidated. > > ..... > > > diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h > > index ada3ed1..283ad26 100644 > > --- a/include/linux/mmu_notifier.h > > +++ b/include/linux/mmu_notifier.h > > @@ -172,6 +172,7 @@ struct mmu_notifier_ops { > > void (*invalidate_page)(struct mmu_notifier *mn, > > struct mm_struct *mm, > > unsigned long address, > > + struct page *page, > > enum mmu_event event); > > > > How do we handle this w.r.t invalidate_range ? With range invalidation the CPU page table is still reliable when invalidate_range_start() callback happen. So we can lookup the CPU page table to get the page backing the address. Cheers, Jérôme