Messages in this thread |  | | Date | Thu, 06 Nov 2014 12:16:36 -0500 | | From | Rik van Riel <> | | Subject | Re: [PATCH 1/5] mmu_notifier: add event information to address invalidation v5 |
| |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/03/2014 03:42 PM, j.glisse@gmail.com wrote: > From: Jérôme Glisse <jglisse@redhat.com> > > 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 <riel@redhat.com>
- -- 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/
|  |