Re: add a not device managed memremap_pages v2
On Fri, Aug 16, 2019 at 08:54:30AM +0200, Christoph Hellwig wrote: > Hi Dan and Jason, > > Bharata has been working on secure page management for kvmppc guests, > and one I thing I noticed is that he had to fake up a struct device > just so that it could be passed to the devm_memremap_pages > instrastructure for device private memory. > > This series adds non-device managed versions of the > devm_request_free_mem_region and devm_memremap_pages functions for > his use case. > > Changes since v1: > - don't overload devm_request_free_mem_region > - export the memremap_pages and munmap_pages as kvmppc can be a module Except for the questions from Andrew this does not look to change anything so: Reviewed-by: Ira Weiny > ___ > Linux-nvdimm mailing list > linux-nvd...@lists.01.org > https://lists.01.org/mailman/listinfo/linux-nvdimm
Re: add a not device managed memremap_pages v2
On Fri, Aug 16, 2019 at 02:36:07PM +0200, Christoph Hellwig wrote: > > > Changes since v1: > > > - don't overload devm_request_free_mem_region > > > - export the memremap_pages and munmap_pages as kvmppc can be a module > > > > What tree do we want this to go through? Dan are you running a pgmap > > tree still? Do we know of any conflicts? > > The last changes in this area went through the hmm tree. There are > now known conflicts, and the kvmppc drivers that needs this already > has a dependency on the hmm tree for the migrate_vma_* changes. OK by me, Dan can you ack or review? Thanks Jason
Re: add a not device managed memremap_pages v2
> > Changes since v1: > > - don't overload devm_request_free_mem_region > > - export the memremap_pages and munmap_pages as kvmppc can be a module > > What tree do we want this to go through? Dan are you running a pgmap > tree still? Do we know of any conflicts? The last changes in this area went through the hmm tree. There are now known conflicts, and the kvmppc drivers that needs this already has a dependency on the hmm tree for the migrate_vma_* changes.
Re: add a not device managed memremap_pages v2
On Fri, Aug 16, 2019 at 08:54:30AM +0200, Christoph Hellwig wrote: > Hi Dan and Jason, > > Bharata has been working on secure page management for kvmppc guests, > and one I thing I noticed is that he had to fake up a struct device > just so that it could be passed to the devm_memremap_pages > instrastructure for device private memory. > > This series adds non-device managed versions of the > devm_request_free_mem_region and devm_memremap_pages functions for > his use case. > > Changes since v1: > - don't overload devm_request_free_mem_region > - export the memremap_pages and munmap_pages as kvmppc can be a module What tree do we want this to go through? Dan are you running a pgmap tree still? Do we know of any conflicts? Thanks, Jason
Re: add a not device managed memremap_pages v2
On Fri, Aug 16, 2019 at 08:54:30AM +0200, Christoph Hellwig wrote: > Hi Dan and Jason, > > Bharata has been working on secure page management for kvmppc guests, > and one I thing I noticed is that he had to fake up a struct device > just so that it could be passed to the devm_memremap_pages > instrastructure for device private memory. > > This series adds non-device managed versions of the > devm_request_free_mem_region and devm_memremap_pages functions for > his use case. Tested this series with my patches that add secure page management for kvmppc guests. These patches along with migrate_vma-cleanup series are good-to-have to support secure guests on ultravisor enabled POWER platforms. Regards, Bharata.
