Re: [Nouveau] [PATCH 1/2] mm: handle multiple owners of device private pages in migrate_vma

2020-03-16 Thread Christoph Hellwig
On Mon, Mar 16, 2020 at 03:17:07PM -0300, Jason Gunthorpe wrote: > On Mon, Mar 16, 2020 at 06:52:58PM +0100, Christoph Hellwig wrote: > > Add a new opaque owner field to struct dev_pagemap, which will allow > > the hmm and migrate_vma code to identify who owns ZONE_DEVICE memory, > > and refuse to

Re: [Nouveau] [PATCH 1/2] mm: handle multiple owners of device private pages in migrate_vma

2020-03-16 Thread Jason Gunthorpe
On Mon, Mar 16, 2020 at 06:52:58PM +0100, Christoph Hellwig wrote: > Add a new opaque owner field to struct dev_pagemap, which will allow > the hmm and migrate_vma code to identify who owns ZONE_DEVICE memory, > and refuse to work on mappings not owned by the calling entity. Using a pointer seems

[Nouveau] [PATCH 1/2] mm: handle multiple owners of device private pages in migrate_vma

2020-03-16 Thread Christoph Hellwig
Add a new opaque owner field to struct dev_pagemap, which will allow the hmm and migrate_vma code to identify who owns ZONE_DEVICE memory, and refuse to work on mappings not owned by the calling entity. Signed-off-by: Christoph Hellwig --- arch/powerpc/kvm/book3s_hv_uvmem.c | 4