From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:e::133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 132EA202BB9AB for ; Thu, 15 Aug 2019 23:56:38 -0700 (PDT) From: Christoph Hellwig Subject: add a not device managed memremap_pages v2 Date: Fri, 16 Aug 2019 08:54:30 +0200 Message-Id: <20190816065434.2129-1-hch@lst.de> MIME-Version: 1.0 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Dan Williams , Jason Gunthorpe Cc: linux-mm@kvack.org, Andrew Morton , linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org, Bharata B Rao List-ID: 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 _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm