| Message ID | 20190326164747.24405-8-jglisse@redhat.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | mmu notifier provide context informations | expand |
On Tue, Mar 26, 2019 at 12:47:46PM -0400, Jerome Glisse wrote: > From: Jérôme Glisse <jglisse@redhat.com> > > CPU page table update can happens for many reasons, not only as a result > of a syscall (munmap(), mprotect(), mremap(), madvise(), ...) but also > as a result of kernel activities (memory compression, reclaim, migration, > ...). > > Users of mmu notifier API track changes to the CPU page table and take > specific action for them. While current API only provide range of virtual > address affected by the change, not why the changes is happening > > This patch is just passing down the new informations by adding it to the > mmu_notifier_range structure. > > Changes since v1: > - Initialize flags field from mmu_notifier_range_init() arguments > > Signed-off-by: Jérôme Glisse <jglisse@redhat.com> > Cc: Andrew Morton <akpm@linux-foundation.org> > Cc: linux-mm@kvack.org > Cc: Christian König <christian.koenig@amd.com> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > Cc: Jani Nikula <jani.nikula@linux.intel.com> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> > Cc: Jan Kara <jack@suse.cz> > Cc: Andrea Arcangeli <aarcange@redhat.com> > Cc: Peter Xu <peterx@redhat.com> > Cc: Felix Kuehling <Felix.Kuehling@amd.com> > Cc: Jason Gunthorpe <jgg@mellanox.com> > Cc: Ross Zwisler <zwisler@kernel.org> > Cc: Dan Williams <dan.j.williams@intel.com> > Cc: Paolo Bonzini <pbonzini@redhat.com> > Cc: Radim Krčmář <rkrcmar@redhat.com> > Cc: Michal Hocko <mhocko@kernel.org> > Cc: Christian Koenig <christian.koenig@amd.com> > Cc: Ralph Campbell <rcampbell@nvidia.com> > Cc: John Hubbard <jhubbard@nvidia.com> > Cc: kvm@vger.kernel.org > Cc: dri-devel@lists.freedesktop.org > Cc: linux-rdma@vger.kernel.org > Cc: Arnd Bergmann <arnd@arndb.de> > --- > include/linux/mmu_notifier.h | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h > index 62f94cd85455..0379956fff23 100644 > --- a/include/linux/mmu_notifier.h > +++ b/include/linux/mmu_notifier.h > @@ -58,10 +58,12 @@ struct mmu_notifier_mm { > #define MMU_NOTIFIER_RANGE_BLOCKABLE (1 << 0) > > struct mmu_notifier_range { > + struct vm_area_struct *vma; > struct mm_struct *mm; > unsigned long start; > unsigned long end; > unsigned flags; > + enum mmu_notifier_event event; > }; > > struct mmu_notifier_ops { > @@ -363,10 +365,12 @@ static inline void mmu_notifier_range_init(struct mmu_notifier_range *range, > unsigned long start, > unsigned long end) > { > + range->vma = vma; > + range->event = event; > range->mm = mm; > range->start = start; > range->end = end; > - range->flags = 0; > + range->flags = flags; Which of the "user patch sets" uses the new flags? I'm not seeing that user yet. In general I don't see anything wrong with the series and I like the idea of telling drivers why the invalidate has fired. But is the flags a future feature? For the series: Reviewed-by: Ira Weiny <ira.weiny@intel.com> Ira > } > > #define ptep_clear_flush_young_notify(__vma, __address, __ptep) \ > -- > 2.20.1 >
On Wed, Apr 10, 2019 at 04:41:57PM -0700, Ira Weiny wrote: > On Tue, Mar 26, 2019 at 12:47:46PM -0400, Jerome Glisse wrote: > > From: Jérôme Glisse <jglisse@redhat.com> > > > > CPU page table update can happens for many reasons, not only as a result > > of a syscall (munmap(), mprotect(), mremap(), madvise(), ...) but also > > as a result of kernel activities (memory compression, reclaim, migration, > > ...). > > > > Users of mmu notifier API track changes to the CPU page table and take > > specific action for them. While current API only provide range of virtual > > address affected by the change, not why the changes is happening > > > > This patch is just passing down the new informations by adding it to the > > mmu_notifier_range structure. > > > > Changes since v1: > > - Initialize flags field from mmu_notifier_range_init() arguments > > > > Signed-off-by: Jérôme Glisse <jglisse@redhat.com> > > Cc: Andrew Morton <akpm@linux-foundation.org> > > Cc: linux-mm@kvack.org > > Cc: Christian König <christian.koenig@amd.com> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > > Cc: Jani Nikula <jani.nikula@linux.intel.com> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> > > Cc: Jan Kara <jack@suse.cz> > > Cc: Andrea Arcangeli <aarcange@redhat.com> > > Cc: Peter Xu <peterx@redhat.com> > > Cc: Felix Kuehling <Felix.Kuehling@amd.com> > > Cc: Jason Gunthorpe <jgg@mellanox.com> > > Cc: Ross Zwisler <zwisler@kernel.org> > > Cc: Dan Williams <dan.j.williams@intel.com> > > Cc: Paolo Bonzini <pbonzini@redhat.com> > > Cc: Radim Krčmář <rkrcmar@redhat.com> > > Cc: Michal Hocko <mhocko@kernel.org> > > Cc: Christian Koenig <christian.koenig@amd.com> > > Cc: Ralph Campbell <rcampbell@nvidia.com> > > Cc: John Hubbard <jhubbard@nvidia.com> > > Cc: kvm@vger.kernel.org > > Cc: dri-devel@lists.freedesktop.org > > Cc: linux-rdma@vger.kernel.org > > Cc: Arnd Bergmann <arnd@arndb.de> > > --- > > include/linux/mmu_notifier.h | 6 +++++- > > 1 file changed, 5 insertions(+), 1 deletion(-) > > > > diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h > > index 62f94cd85455..0379956fff23 100644 > > --- a/include/linux/mmu_notifier.h > > +++ b/include/linux/mmu_notifier.h > > @@ -58,10 +58,12 @@ struct mmu_notifier_mm { > > #define MMU_NOTIFIER_RANGE_BLOCKABLE (1 << 0) > > > > struct mmu_notifier_range { > > + struct vm_area_struct *vma; > > struct mm_struct *mm; > > unsigned long start; > > unsigned long end; > > unsigned flags; > > + enum mmu_notifier_event event; > > }; > > > > struct mmu_notifier_ops { > > @@ -363,10 +365,12 @@ static inline void mmu_notifier_range_init(struct mmu_notifier_range *range, > > unsigned long start, > > unsigned long end) > > { > > + range->vma = vma; > > + range->event = event; > > range->mm = mm; > > range->start = start; > > range->end = end; > > - range->flags = 0; > > + range->flags = flags; > > Which of the "user patch sets" uses the new flags? > > I'm not seeing that user yet. In general I don't see anything wrong with the > series and I like the idea of telling drivers why the invalidate has fired. > > But is the flags a future feature? It seems that it is used in HMM ODP patch. https://patchwork.kernel.org/patch/10894281/ Thanks > > For the series: > > Reviewed-by: Ira Weiny <ira.weiny@intel.com> > > Ira > > > } > > > > #define ptep_clear_flush_young_notify(__vma, __address, __ptep) \ > > -- > > 2.20.1 > >
On Wed, Apr 10, 2019 at 04:41:57PM -0700, Ira Weiny wrote: > On Tue, Mar 26, 2019 at 12:47:46PM -0400, Jerome Glisse wrote: > > From: Jérôme Glisse <jglisse@redhat.com> > > > > CPU page table update can happens for many reasons, not only as a result > > of a syscall (munmap(), mprotect(), mremap(), madvise(), ...) but also > > as a result of kernel activities (memory compression, reclaim, migration, > > ...). > > > > Users of mmu notifier API track changes to the CPU page table and take > > specific action for them. While current API only provide range of virtual > > address affected by the change, not why the changes is happening > > > > This patch is just passing down the new informations by adding it to the > > mmu_notifier_range structure. > > > > Changes since v1: > > - Initialize flags field from mmu_notifier_range_init() arguments > > > > Signed-off-by: Jérôme Glisse <jglisse@redhat.com> > > Cc: Andrew Morton <akpm@linux-foundation.org> > > Cc: linux-mm@kvack.org > > Cc: Christian König <christian.koenig@amd.com> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > > Cc: Jani Nikula <jani.nikula@linux.intel.com> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> > > Cc: Jan Kara <jack@suse.cz> > > Cc: Andrea Arcangeli <aarcange@redhat.com> > > Cc: Peter Xu <peterx@redhat.com> > > Cc: Felix Kuehling <Felix.Kuehling@amd.com> > > Cc: Jason Gunthorpe <jgg@mellanox.com> > > Cc: Ross Zwisler <zwisler@kernel.org> > > Cc: Dan Williams <dan.j.williams@intel.com> > > Cc: Paolo Bonzini <pbonzini@redhat.com> > > Cc: Radim Krčmář <rkrcmar@redhat.com> > > Cc: Michal Hocko <mhocko@kernel.org> > > Cc: Christian Koenig <christian.koenig@amd.com> > > Cc: Ralph Campbell <rcampbell@nvidia.com> > > Cc: John Hubbard <jhubbard@nvidia.com> > > Cc: kvm@vger.kernel.org > > Cc: dri-devel@lists.freedesktop.org > > Cc: linux-rdma@vger.kernel.org > > Cc: Arnd Bergmann <arnd@arndb.de> > > --- > > include/linux/mmu_notifier.h | 6 +++++- > > 1 file changed, 5 insertions(+), 1 deletion(-) > > > > diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h > > index 62f94cd85455..0379956fff23 100644 > > --- a/include/linux/mmu_notifier.h > > +++ b/include/linux/mmu_notifier.h > > @@ -58,10 +58,12 @@ struct mmu_notifier_mm { > > #define MMU_NOTIFIER_RANGE_BLOCKABLE (1 << 0) > > > > struct mmu_notifier_range { > > + struct vm_area_struct *vma; > > struct mm_struct *mm; > > unsigned long start; > > unsigned long end; > > unsigned flags; > > + enum mmu_notifier_event event; > > }; > > > > struct mmu_notifier_ops { > > @@ -363,10 +365,12 @@ static inline void mmu_notifier_range_init(struct mmu_notifier_range *range, > > unsigned long start, > > unsigned long end) > > { > > + range->vma = vma; > > + range->event = event; > > range->mm = mm; > > range->start = start; > > range->end = end; > > - range->flags = 0; > > + range->flags = flags; > > Which of the "user patch sets" uses the new flags? > > I'm not seeing that user yet. In general I don't see anything wrong with the > series and I like the idea of telling drivers why the invalidate has fired. > > But is the flags a future feature? > I believe the link were in the cover: https://lkml.org/lkml/2019/1/23/833 https://lkml.org/lkml/2019/1/23/834 https://lkml.org/lkml/2019/1/23/832 https://lkml.org/lkml/2019/1/23/831 I have more coming for HMM but i am waiting after 5.2 once amdgpu HMM patch are merge upstream as it will change what is passed down to driver and it would conflict with non merged HMM driver (like amdgpu today). Cheers, Jérôme
> On Wed, Apr 10, 2019 at 04:41:57PM -0700, Ira Weiny wrote: > > On Tue, Mar 26, 2019 at 12:47:46PM -0400, Jerome Glisse wrote: > > > From: Jérôme Glisse <jglisse@redhat.com> > > > > > > CPU page table update can happens for many reasons, not only as a > > > result of a syscall (munmap(), mprotect(), mremap(), madvise(), ...) > > > but also as a result of kernel activities (memory compression, > > > reclaim, migration, ...). > > > > > > Users of mmu notifier API track changes to the CPU page table and > > > take specific action for them. While current API only provide range > > > of virtual address affected by the change, not why the changes is > > > happening > > > > > > This patch is just passing down the new informations by adding it to > > > the mmu_notifier_range structure. > > > > > > Changes since v1: > > > - Initialize flags field from mmu_notifier_range_init() > > > arguments > > > > > > Signed-off-by: Jérôme Glisse <jglisse@redhat.com> > > > Cc: Andrew Morton <akpm@linux-foundation.org> > > > Cc: linux-mm@kvack.org > > > Cc: Christian König <christian.koenig@amd.com> > > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > > > Cc: Jani Nikula <jani.nikula@linux.intel.com> > > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> > > > Cc: Jan Kara <jack@suse.cz> > > > Cc: Andrea Arcangeli <aarcange@redhat.com> > > > Cc: Peter Xu <peterx@redhat.com> > > > Cc: Felix Kuehling <Felix.Kuehling@amd.com> > > > Cc: Jason Gunthorpe <jgg@mellanox.com> > > > Cc: Ross Zwisler <zwisler@kernel.org> > > > Cc: Dan Williams <dan.j.williams@intel.com> > > > Cc: Paolo Bonzini <pbonzini@redhat.com> > > > Cc: Radim Krčmář <rkrcmar@redhat.com> > > > Cc: Michal Hocko <mhocko@kernel.org> > > > Cc: Christian Koenig <christian.koenig@amd.com> > > > Cc: Ralph Campbell <rcampbell@nvidia.com> > > > Cc: John Hubbard <jhubbard@nvidia.com> > > > Cc: kvm@vger.kernel.org > > > Cc: dri-devel@lists.freedesktop.org > > > Cc: linux-rdma@vger.kernel.org > > > Cc: Arnd Bergmann <arnd@arndb.de> > > > --- > > > include/linux/mmu_notifier.h | 6 +++++- > > > 1 file changed, 5 insertions(+), 1 deletion(-) > > > > > > diff --git a/include/linux/mmu_notifier.h > > > b/include/linux/mmu_notifier.h index 62f94cd85455..0379956fff23 > > > 100644 > > > --- a/include/linux/mmu_notifier.h > > > +++ b/include/linux/mmu_notifier.h > > > @@ -58,10 +58,12 @@ struct mmu_notifier_mm { #define > > > MMU_NOTIFIER_RANGE_BLOCKABLE (1 << 0) > > > > > > struct mmu_notifier_range { > > > + struct vm_area_struct *vma; > > > struct mm_struct *mm; > > > unsigned long start; > > > unsigned long end; > > > unsigned flags; > > > + enum mmu_notifier_event event; > > > }; > > > > > > struct mmu_notifier_ops { > > > @@ -363,10 +365,12 @@ static inline void > mmu_notifier_range_init (struct mmu_notifier_range *range, > > > unsigned long start, > > > unsigned long end) > > > { > > > + range->vma = vma; > > > + range->event = event; > > > range->mm = mm; > > > range->start = start; > > > range->end = end; > > > - range->flags = 0; > > > + range->flags = flags; > > > > Which of the "user patch sets" uses the new flags? > > > > I'm not seeing that user yet. In general I don't see anything wrong > > with the series and I like the idea of telling drivers why the invalidate has > fired. > > > > But is the flags a future feature? > > > > I believe the link were in the cover: > > https://lkml.org/lkml/2019/1/23/833 > https://lkml.org/lkml/2019/1/23/834 > https://lkml.org/lkml/2019/1/23/832 > https://lkml.org/lkml/2019/1/23/831 > > I have more coming for HMM but i am waiting after 5.2 once amdgpu HMM > patch are merge upstream as it will change what is passed down to driver > and it would conflict with non merged HMM driver (like amdgpu today). > Unfortunately this does not answer my question. Yes I saw the links to the patches which use this in the header. Furthermore, I checked the links again, I still do not see a use of range->flags nor a use of the new flags parameter to mmu_notifier_range_init(). I still gave a reviewed by because I'm not saying it is wrong I'm just trying to understand what use drivers have of this flag. So again I'm curious what is the use case of these flags and the use case of exposing it to the users of MMU notifiers? Ira > Cheers, > Jérôme
On Thu, Apr 11, 2019 at 03:21:08PM +0000, Weiny, Ira wrote: > > On Wed, Apr 10, 2019 at 04:41:57PM -0700, Ira Weiny wrote: > > > On Tue, Mar 26, 2019 at 12:47:46PM -0400, Jerome Glisse wrote: > > > > From: Jérôme Glisse <jglisse@redhat.com> > > > > > > > > CPU page table update can happens for many reasons, not only as a > > > > result of a syscall (munmap(), mprotect(), mremap(), madvise(), ...) > > > > but also as a result of kernel activities (memory compression, > > > > reclaim, migration, ...). > > > > > > > > Users of mmu notifier API track changes to the CPU page table and > > > > take specific action for them. While current API only provide range > > > > of virtual address affected by the change, not why the changes is > > > > happening > > > > > > > > This patch is just passing down the new informations by adding it to > > > > the mmu_notifier_range structure. > > > > > > > > Changes since v1: > > > > - Initialize flags field from mmu_notifier_range_init() > > > > arguments > > > > > > > > Signed-off-by: Jérôme Glisse <jglisse@redhat.com> > > > > Cc: Andrew Morton <akpm@linux-foundation.org> > > > > Cc: linux-mm@kvack.org > > > > Cc: Christian König <christian.koenig@amd.com> > > > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > > > > Cc: Jani Nikula <jani.nikula@linux.intel.com> > > > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> > > > > Cc: Jan Kara <jack@suse.cz> > > > > Cc: Andrea Arcangeli <aarcange@redhat.com> > > > > Cc: Peter Xu <peterx@redhat.com> > > > > Cc: Felix Kuehling <Felix.Kuehling@amd.com> > > > > Cc: Jason Gunthorpe <jgg@mellanox.com> > > > > Cc: Ross Zwisler <zwisler@kernel.org> > > > > Cc: Dan Williams <dan.j.williams@intel.com> > > > > Cc: Paolo Bonzini <pbonzini@redhat.com> > > > > Cc: Radim Krčmář <rkrcmar@redhat.com> > > > > Cc: Michal Hocko <mhocko@kernel.org> > > > > Cc: Christian Koenig <christian.koenig@amd.com> > > > > Cc: Ralph Campbell <rcampbell@nvidia.com> > > > > Cc: John Hubbard <jhubbard@nvidia.com> > > > > Cc: kvm@vger.kernel.org > > > > Cc: dri-devel@lists.freedesktop.org > > > > Cc: linux-rdma@vger.kernel.org > > > > Cc: Arnd Bergmann <arnd@arndb.de> > > > > --- > > > > include/linux/mmu_notifier.h | 6 +++++- > > > > 1 file changed, 5 insertions(+), 1 deletion(-) > > > > > > > > diff --git a/include/linux/mmu_notifier.h > > > > b/include/linux/mmu_notifier.h index 62f94cd85455..0379956fff23 > > > > 100644 > > > > --- a/include/linux/mmu_notifier.h > > > > +++ b/include/linux/mmu_notifier.h > > > > @@ -58,10 +58,12 @@ struct mmu_notifier_mm { #define > > > > MMU_NOTIFIER_RANGE_BLOCKABLE (1 << 0) > > > > > > > > struct mmu_notifier_range { > > > > + struct vm_area_struct *vma; > > > > struct mm_struct *mm; > > > > unsigned long start; > > > > unsigned long end; > > > > unsigned flags; > > > > + enum mmu_notifier_event event; > > > > }; > > > > > > > > struct mmu_notifier_ops { > > > > @@ -363,10 +365,12 @@ static inline void > > mmu_notifier_range_init (struct mmu_notifier_range *range, > > > > unsigned long start, > > > > unsigned long end) > > > > { > > > > + range->vma = vma; > > > > + range->event = event; > > > > range->mm = mm; > > > > range->start = start; > > > > range->end = end; > > > > - range->flags = 0; > > > > + range->flags = flags; > > > > > > Which of the "user patch sets" uses the new flags? > > > > > > I'm not seeing that user yet. In general I don't see anything wrong > > > with the series and I like the idea of telling drivers why the invalidate has > > fired. > > > > > > But is the flags a future feature? > > > > > > > I believe the link were in the cover: > > > > https://lkml.org/lkml/2019/1/23/833 > > https://lkml.org/lkml/2019/1/23/834 > > https://lkml.org/lkml/2019/1/23/832 > > https://lkml.org/lkml/2019/1/23/831 > > > > I have more coming for HMM but i am waiting after 5.2 once amdgpu HMM > > patch are merge upstream as it will change what is passed down to driver > > and it would conflict with non merged HMM driver (like amdgpu today). > > > > Unfortunately this does not answer my question. Yes I saw the links to the patches which use this in the header. Furthermore, I checked the links again, I still do not see a use of range->flags nor a use of the new flags parameter to mmu_notifier_range_init(). > > I still gave a reviewed by because I'm not saying it is wrong I'm just trying to understand what use drivers have of this flag. > > So again I'm curious what is the use case of these flags and the use case of exposing it to the users of MMU notifiers? Oh sorry did miss the exact question, not enough coffee. The flags is use for BLOCKABLE i converted the bool blockable to an int flags field so that we can have flags in the future. The first user is probably gonna be for restoring the KVM change_pte() optimization. https://lkml.org/lkml/2019/2/19/754 https://lkml.org/lkml/2019/2/20/1087 I droped the CHANGE_PTE flags from this version as i need to harass the KVM people some more for them to review this as today the change_pte() optimization does not work so today the change_pte() callback are useless and just wasting CPU cycles. Cheers, Jérôme
On Thu, Apr 11, 2019 at 08:41:30AM +0300, Leon Romanovsky wrote: > On Wed, Apr 10, 2019 at 04:41:57PM -0700, Ira Weiny wrote: > > On Tue, Mar 26, 2019 at 12:47:46PM -0400, Jerome Glisse wrote: > > > From: Jérôme Glisse <jglisse@redhat.com> > > > [snip] > > > diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h > > > index 62f94cd85455..0379956fff23 100644 > > > --- a/include/linux/mmu_notifier.h > > > +++ b/include/linux/mmu_notifier.h > > > @@ -58,10 +58,12 @@ struct mmu_notifier_mm { > > > #define MMU_NOTIFIER_RANGE_BLOCKABLE (1 << 0) > > > > > > struct mmu_notifier_range { > > > + struct vm_area_struct *vma; > > > struct mm_struct *mm; > > > unsigned long start; > > > unsigned long end; > > > unsigned flags; > > > + enum mmu_notifier_event event; > > > }; > > > > > > struct mmu_notifier_ops { > > > @@ -363,10 +365,12 @@ static inline void mmu_notifier_range_init(struct mmu_notifier_range *range, > > > unsigned long start, > > > unsigned long end) > > > { > > > + range->vma = vma; > > > + range->event = event; > > > range->mm = mm; > > > range->start = start; > > > range->end = end; > > > - range->flags = 0; > > > + range->flags = flags; > > > > Which of the "user patch sets" uses the new flags? > > > > I'm not seeing that user yet. In general I don't see anything wrong with the > > series and I like the idea of telling drivers why the invalidate has fired. > > > > But is the flags a future feature? > > It seems that it is used in HMM ODP patch. > https://patchwork.kernel.org/patch/10894281/ AFAICT the flags in that patch are "hmm_range->flags" not "mmu_notifier_range->flags" They are not the same. Ira > > Thanks > > > > > For the series: > > > > Reviewed-by: Ira Weiny <ira.weiny@intel.com> > > > > Ira > > > > > } > > > > > > #define ptep_clear_flush_young_notify(__vma, __address, __ptep) \ > > > -- > > > 2.20.1 > > >
diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h index 62f94cd85455..0379956fff23 100644 --- a/include/linux/mmu_notifier.h +++ b/include/linux/mmu_notifier.h @@ -58,10 +58,12 @@ struct mmu_notifier_mm { #define MMU_NOTIFIER_RANGE_BLOCKABLE (1 << 0) struct mmu_notifier_range { + struct vm_area_struct *vma; struct mm_struct *mm; unsigned long start; unsigned long end; unsigned flags; + enum mmu_notifier_event event; }; struct mmu_notifier_ops { @@ -363,10 +365,12 @@ static inline void mmu_notifier_range_init(struct mmu_notifier_range *range, unsigned long start, unsigned long end) { + range->vma = vma; + range->event = event; range->mm = mm; range->start = start; range->end = end; - range->flags = 0; + range->flags = flags; } #define ptep_clear_flush_young_notify(__vma, __address, __ptep) \