Re: [2/2] cxl: Fix force unmapping mmaps of contexts allocated through the kernel api

2015-08-30 Thread Michael Ellerman
On Thu, 2015-27-08 at 09:50:19 UTC, Ian Munsie wrote: > From: Ian Munsie > > The cxl user api uses the address_space associated with the file when we > need to force unmap all cxl mmap regions (e.g. on eeh, driver detach, > etc). Currently, contexts allocated through the kernel api do not do >

Re: [2/2] cxl: Fix force unmapping mmaps of contexts allocated through the kernel api

2015-08-30 Thread Michael Ellerman
On Thu, 2015-27-08 at 09:50:19 UTC, Ian Munsie wrote: From: Ian Munsie imun...@au1.ibm.com The cxl user api uses the address_space associated with the file when we need to force unmap all cxl mmap regions (e.g. on eeh, driver detach, etc). Currently, contexts allocated through the kernel api

[PATCH 2/2] cxl: Fix force unmapping mmaps of contexts allocated through the kernel api

2015-08-27 Thread Ian Munsie
From: Ian Munsie The cxl user api uses the address_space associated with the file when we need to force unmap all cxl mmap regions (e.g. on eeh, driver detach, etc). Currently, contexts allocated through the kernel api do not do this and instead skip the mmap invalidation, potentially allowing

[PATCH 2/2] cxl: Fix force unmapping mmaps of contexts allocated through the kernel api

2015-08-27 Thread Ian Munsie
From: Ian Munsie imun...@au1.ibm.com The cxl user api uses the address_space associated with the file when we need to force unmap all cxl mmap regions (e.g. on eeh, driver detach, etc). Currently, contexts allocated through the kernel api do not do this and instead skip the mmap invalidation,