[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190627165349.GB10652@lst.de>
Date: Thu, 27 Jun 2019 18:53:49 +0200
From: Christoph Hellwig <hch@....de>
To: Jason Gunthorpe <jgg@...lanox.com>
Cc: Christoph Hellwig <hch@....de>,
Dan Williams <dan.j.williams@...el.com>,
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-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ralph Campbell <rcampbell@...dia.com>
Subject: Re: [PATCH 12/25] memremap: add a migrate_to_ram method to struct
dev_pagemap_ops
On Thu, Jun 27, 2019 at 04:29:45PM +0000, Jason Gunthorpe wrote:
> I'ver heard there are some other use models for fault() here beyond
> migrate to ram, but we can rename it if we ever see them.
Well, it absolutely needs to migrate to some piece of addressable
and coherent memory, so ram might be a nice shortcut for that.
> > +static vm_fault_t hmm_devmem_migrate_to_ram(struct vm_fault *vmf)
> > {
> > - struct hmm_devmem *devmem = page->pgmap->data;
> > + struct hmm_devmem *devmem = vmf->page->pgmap->data;
> >
> > - return devmem->ops->fault(devmem, vma, addr, page, flags, pmdp);
> > + return devmem->ops->fault(devmem, vmf->vma, vmf->address, vmf->page,
> > + vmf->flags, vmf->pmd);
> > }
>
> Next cycle we should probably rename this fault to migrate_to_ram as
> well and pass in the vmf..
That ->fault op goes away entirely in one of the next patches in the
series.
Powered by blists - more mailing lists