[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190820132622.GC29225@mellanox.com>
Date: Tue, 20 Aug 2019 13:26:29 +0000
From: Jason Gunthorpe <jgg@...lanox.com>
To: Christoph Hellwig <hch@....de>
CC: Dan Williams <dan.j.williams@...el.com>,
Bharata B Rao <bharata@...ux.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>
Subject: Re: add a not device managed memremap_pages v3
On Sun, Aug 18, 2019 at 11:05:53AM +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 v2:
> - improved changelogs that the the v2 changes into account
>
> Changes since v1:
> - don't overload devm_request_free_mem_region
> - export the memremap_pages and munmap_pages as kvmppc can be a module
Looks good, I fixed up the patch with Dan's note and reviewed them as
well.
Applied to hmm.git as requested
Thanks,
Jason
Powered by blists - more mailing lists