[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190730124517.GE24038@mellanox.com>
Date: Tue, 30 Jul 2019 12:45:22 +0000
From: Jason Gunthorpe <jgg@...lanox.com>
To: Christoph Hellwig <hch@....de>
CC: Jérôme Glisse <jglisse@...hat.com>,
Ben Skeggs <bskeggs@...hat.com>,
Felix Kuehling <Felix.Kuehling@....com>,
Ralph Campbell <rcampbell@...dia.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>,
"amd-gfx@...ts.freedesktop.org" <amd-gfx@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 05/13] mm: remove the unused vma argument to
hmm_range_dma_unmap
On Tue, Jul 30, 2019 at 08:51:55AM +0300, Christoph Hellwig wrote:
> Signed-off-by: Christoph Hellwig <hch@....de>
> include/linux/hmm.h | 1 -
> mm/hmm.c | 2 --
> 2 files changed, 3 deletions(-)
Reviewed-by: Jason Gunthorpe <jgg@...lanox.com>
Unclear what this was intended for, but I think if we need to carry
information from the dma_map to unmap it should be done in some opaque
way.
The driver should not have to care about VMAs, beyond perhaps using
VMAs to guide what VA ranges to mirror.
Jason
Powered by blists - more mailing lists