[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190703180356.GB18673@ziepe.ca>
Date: Wed, 3 Jul 2019 15:03:56 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Christoph Hellwig <hch@....de>,
AlexDeucher <alexander.deucher@....com>
Cc: Dan Williams <dan.j.williams@...el.com>,
Jérôme Glisse <jglisse@...hat.com>,
Ben Skeggs <bskeggs@...hat.com>,
Ira Weiny <ira.weiny@...el.com>, linux-mm@...ck.org,
nouveau@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
linux-nvdimm@...ts.01.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 20/22] mm: move hmm_vma_fault to nouveau
On Mon, Jul 01, 2019 at 08:20:18AM +0200, Christoph Hellwig wrote:
> hmm_vma_fault is marked as a legacy API to get rid of, but quite suites
> the current nouvea flow. Move it to the only user in preparation for
> fixing a locking bug involving caller and callee.
>
> Signed-off-by: Christoph Hellwig <hch@....de>
> drivers/gpu/drm/nouveau/nouveau_svm.c | 54 ++++++++++++++++++++++++++-
> include/linux/hmm.h | 54 ---------------------------
> 2 files changed, 53 insertions(+), 55 deletions(-)
I was thinking about doing exactly this too, but amdgpu started using
this already obsolete API in their latest driver :(
So, we now need to get both drivers to move to the modern API.
Jason
Powered by blists - more mailing lists