[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190708173219.GL23966@mellanox.com>
Date: Mon, 8 Jul 2019 17:32:24 +0000
From: Jason Gunthorpe <jgg@...lanox.com>
To: Ralph Campbell <rcampbell@...dia.com>
CC: Christoph Hellwig <hch@....de>,
Jérôme Glisse <jglisse@...hat.com>,
Ben Skeggs <bskeggs@...hat.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: hmm_range_fault related fixes and legacy API removal v2
On Mon, Jul 08, 2019 at 10:30:55AM -0700, Ralph Campbell wrote:
>
> On 7/4/19 9:42 AM, Jason Gunthorpe wrote:
> > On Wed, Jul 03, 2019 at 03:02:08PM -0700, Christoph Hellwig wrote:
> > > Hi Jérôme, Ben and Jason,
> > >
> > > below is a series against the hmm tree which fixes up the mmap_sem
> > > locking in nouveau and while at it also removes leftover legacy HMM APIs
> > > only used by nouveau.
> > >
> > > Changes since v1:
> > > - don't return the valid state from hmm_range_unregister
> > > - additional nouveau cleanups
> >
> > Ralph, since most of this is nouveau could you contribute a
> > Tested-by? Thanks
> >
> > Jason
> >
>
> I can test things fairly easily but with all the different patches,
> conflicts, and personal git trees, can you specify the git tree
> and branch with everything applied that you want me to test?
This series will be pushed to the next cycle, so if you test v5.3-rc1
+ this series you'd get the right coverage.
Thanks,
Jason
Powered by blists - more mailing lists