[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170726191432.GC21717@redhat.com>
Date: Wed, 26 Jul 2017 15:14:32 -0400
From: Jerome Glisse <jglisse@...hat.com>
To: Evgeny Baskakov <ebaskakov@...dia.com>
Cc: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
John Hubbard <jhubbard@...dia.com>,
David Nellans <dnellans@...dia.com>,
Mark Hairgrove <mhairgrove@...dia.com>,
Sherry Cheung <SCheung@...dia.com>,
Subhash Gutti <sgutti@...dia.com>
Subject: Re: [HMM 12/15] mm/migrate: new memory migration helper for use with
device memory v4
On Tue, Jul 25, 2017 at 03:45:14PM -0700, Evgeny Baskakov wrote:
> On 7/20/17 6:33 PM, Jerome Glisse wrote:
>
> > So i pushed an updated hmm-next branch it should have all fixes so far, including
> > something that should fix this issue. I still want to go over all emails again
> > to make sure i am not forgetting anything.
> >
> > Cheers,
> > Jérôme
>
> Hi Jerome,
>
> Thanks for updating the documentation for hmm_devmem_ops.
>
> I have an inquiry about the "fault" callback, though. The documentation says
> "Returns: 0 on success", but can the driver set any VM_FAULT_* flags? For
> instance, the driver might want to set the VM_FAULT_MAJOR flag to indicate
> that a heavy-weight page migration has happened on the page fault.
>
> If that is possible, can you please update the documentation and list the
> flags that are permitted in the callback's return value?
Yes you can.
Jérôme
Powered by blists - more mailing lists