From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Jason Gunthorpe Subject: Re: add a not device managed memremap_pages v2 Date: Fri, 16 Aug 2019 12:34:01 +0000 Message-ID: <20190816123356.GE5412@mellanox.com> References: <20190816065434.2129-1-hch@lst.de> In-Reply-To: <20190816065434.2129-1-hch@lst.de> Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: owner-linux-mm@kvack.org To: Christoph Hellwig Cc: Dan Williams , Bharata B Rao , Andrew Morton , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , "linux-nvdimm@lists.01.org" List-ID: On Fri, Aug 16, 2019 at 08:54:30AM +0200, Christoph Hellwig wrote: > Hi Dan and Jason, >=20 > 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. >=20 > This series adds non-device managed versions of the > devm_request_free_mem_region and devm_memremap_pages functions for > his use case. >=20 > 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