[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181207153249.GA3293@redhat.com>
Date: Fri, 7 Dec 2018 10:32:49 -0500
From: Jerome Glisse <jglisse@...hat.com>
To: Jason Gunthorpe <jgg@...pe.ca>
Cc: linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Matthew Wilcox <mawilcox@...rosoft.com>,
Ross Zwisler <zwisler@...nel.org>, Jan Kara <jack@...e.cz>,
Dan Williams <dan.j.williams@...el.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
Michal Hocko <mhocko@...nel.org>,
Christian Koenig <christian.koenig@....com>,
Felix Kuehling <felix.kuehling@....com>,
Ralph Campbell <rcampbell@...dia.com>,
John Hubbard <jhubbard@...dia.com>, kvm@...r.kernel.org,
dri-devel@...ts.freedesktop.org, linux-rdma@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v2 1/3] mm/mmu_notifier: use structure for
invalidate_range_start/end callback
On Thu, Dec 06, 2018 at 08:30:27PM -0700, Jason Gunthorpe wrote:
> On Wed, Dec 05, 2018 at 12:36:26AM -0500, jglisse@...hat.com wrote:
> > From: Jérôme Glisse <jglisse@...hat.com>
> >
> > To avoid having to change many callback definition everytime we want
> > to add a parameter use a structure to group all parameters for the
> > mmu_notifier invalidate_range_start/end callback. No functional changes
> > with this patch.
> >
> > Signed-off-by: Jérôme Glisse <jglisse@...hat.com>
> > Cc: Andrew Morton <akpm@...ux-foundation.org>
> > Cc: Matthew Wilcox <mawilcox@...rosoft.com>
> > Cc: Ross Zwisler <zwisler@...nel.org>
> > Cc: Jan Kara <jack@...e.cz>
> > Cc: Dan Williams <dan.j.williams@...el.com>
> > Cc: Paolo Bonzini <pbonzini@...hat.com>
> > Cc: Radim Krčmář <rkrcmar@...hat.com>
> > Cc: Michal Hocko <mhocko@...nel.org>
> > Cc: Christian Koenig <christian.koenig@....com>
> > Cc: Felix Kuehling <felix.kuehling@....com>
> > Cc: Ralph Campbell <rcampbell@...dia.com>
> > Cc: John Hubbard <jhubbard@...dia.com>
> > Cc: kvm@...r.kernel.org
> > Cc: dri-devel@...ts.freedesktop.org
> > Cc: linux-rdma@...r.kernel.org
> > Cc: linux-fsdevel@...r.kernel.org
> > ---
> > drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c | 43 +++++++++++--------------
> > drivers/gpu/drm/i915/i915_gem_userptr.c | 14 ++++----
> > drivers/gpu/drm/radeon/radeon_mn.c | 16 ++++-----
> > drivers/infiniband/core/umem_odp.c | 20 +++++-------
> > drivers/infiniband/hw/hfi1/mmu_rb.c | 13 +++-----
> > drivers/misc/mic/scif/scif_dma.c | 11 ++-----
> > drivers/misc/sgi-gru/grutlbpurge.c | 14 ++++----
> > drivers/xen/gntdev.c | 12 +++----
> > include/linux/mmu_notifier.h | 14 +++++---
> > mm/hmm.c | 23 ++++++-------
> > mm/mmu_notifier.c | 21 ++++++++++--
> > virt/kvm/kvm_main.c | 14 +++-----
> > 12 files changed, 102 insertions(+), 113 deletions(-)
>
> The changes to drivers/infiniband look mechanical and fine to me.
>
> It even looks like this avoids merge conflicts with the other changes
> to these files :)
>
> For infiniband:
>
> Acked-by: Jason Gunthorpe <jgg@...lanox.com>
>
> I assume this will go through the mm tree?
Yes this is my exceptation as in the ends it touch more mm
stuff than anything else. Andrew already added v1 to its
patchset.
Cheers,
Jérôme
Powered by blists - more mailing lists