Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752040AbaKFRRb (ORCPT ); Thu, 6 Nov 2014 12:17:31 -0500 Received: from mx1.redhat.com ([209.132.183.28]:43448 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750970AbaKFRR3 (ORCPT ); Thu, 6 Nov 2014 12:17:29 -0500 Message-ID: <545BACF4.2080808@redhat.com> Date: Thu, 06 Nov 2014 12:16:36 -0500 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: j.glisse@gmail.com, akpm@linux-foundation.org CC: 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 , Dave Airlie , Brendan Conoboy , Joe Donohue , Duncan Poole , Sherry Cheung , Subhash Gutti , John Hubbard , Mark Hairgrove , Lucien Dunning , Cameron Buschardt , Arvind Gopalakrishnan , Shachar Raindel , Liran Liss , Roland Dreier , Ben Sander , Greg Stoner , John Bridgman , Michael Mantor , Paul Blinzer , Laurent Morichetti , Alexander Deucher , Oded Gabbay , =?UTF-8?B?SsOpcsO0bWUgR2xpc3Nl?= Subject: Re: [PATCH 1/5] mmu_notifier: add event information to address invalidation v5 References: <1415047353-29160-1-git-send-email-j.glisse@gmail.com> <1415047353-29160-2-git-send-email-j.glisse@gmail.com> In-Reply-To: <1415047353-29160-2-git-send-email-j.glisse@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/03/2014 03:42 PM, j.glisse@gmail.com wrote: > From: Jérôme Glisse > > The event information will be usefull for new user of mmu_notifier > API. The event argument differentiate between a vma disappearing, a > page being write protected or simply a page being unmaped. This > allow new user to take different path for different event for > instance on unmap the resource used to track a vma are still valid > and should stay around. While if the event is saying that a vma is > being destroy it means that any resources used to track this vma > can be free. Looks good. All I found was one spelling mistake :) > + * - MMU_WRITE_BACK: memory is being written back to disk, all > write accesses + * must stop after invalidate_range_start > callback returns. Read access are + * still allowed. + * + * > - MMU_WRITE_PROTECT: memory is being writte protected (ie should be > mapped "write protected" > + * read only no matter what the vma memory protection allows). > All write + * accesses must stop after invalidate_range_start > callback returns. Read + * access are still allowed. After fixing the spelling mistake, feel free to add my Reviewed-by: Rik van Riel - -- All rights reversed -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUW6z0AAoJEM553pKExN6DN3wIALqZPmNihc/AbOc6MCnp+two do5pO0DTl61AD0SmPsjSKrADa8deHKDL3PqsEcA7aYOlwrJOkPhNxZZsq1SHscAO iw4Ar9BbI0JwBZO4xq4RwFhAVnu5r5NZEcyG1t1EqOGoOVc8NIflTNCxQYOU+vkj YxCZb4A0+e6nKe3P+tWso69AGHH5GVvFOqLy709OxneLbTVDRRBM1KzYtdkGR62i u3Xa41WGVjAa6OVYEoENloa/o8cmL9vgqPG3bhbCjR8zpBPAQ7fS3g8Ckux72mS+ UNzyoZjCGpWg7IxF94xhTvydzER0XDMancbKzrYW14YoJ3mW7ZDj58vpK25SKM8= =f2u6 -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/