[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190816235927.GB11384@iweiny-DESK2.sc.intel.com>
Date: Fri, 16 Aug 2019 16:59:27 -0700
From: Ira Weiny <ira.weiny@...el.com>
To: Christoph Hellwig <hch@....de>
Cc: Dan Williams <dan.j.williams@...el.com>,
Jason Gunthorpe <jgg@...lanox.com>, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>,
linux-nvdimm@...ts.01.org, linux-kernel@...r.kernel.org,
Bharata B Rao <bharata@...ux.ibm.com>
Subject: 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 <ira.weiny@...el.com>
> _______________________________________________
> Linux-nvdimm mailing list
> Linux-nvdimm@...ts.01.org
> https://lists.01.org/mailman/listinfo/linux-nvdimm
Powered by blists - more mailing lists