From: Christoph Hellwig <hch@lst.de> To: Dan Williams <dan.j.williams@intel.com>, Jason Gunthorpe <jgg@mellanox.com> Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>, linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org, Bharata B Rao <bharata@linux.ibm.com> Subject: add a not device managed memremap_pages v2 Date: Fri, 16 Aug 2019 08:54:30 +0200 [thread overview] Message-ID: <20190816065434.2129-1-hch@lst.de> (raw) 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
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de> To: Dan Williams <dan.j.williams@intel.com>, Jason Gunthorpe <jgg@mellanox.com> Cc: Bharata B Rao <bharata@linux.ibm.com>, Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org Subject: add a not device managed memremap_pages v2 Date: Fri, 16 Aug 2019 08:54:30 +0200 [thread overview] Message-ID: <20190816065434.2129-1-hch@lst.de> (raw) 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
next reply other threads:[~2019-08-16 6:56 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-16 6:54 Christoph Hellwig [this message] 2019-08-16 6:54 ` add a not device managed memremap_pages v2 Christoph Hellwig 2019-08-16 6:54 ` [PATCH 1/4] resource: add a not device managed request_free_mem_region variant Christoph Hellwig 2019-08-16 6:54 ` Christoph Hellwig 2019-08-16 21:01 ` Andrew Morton 2019-08-16 21:01 ` Andrew Morton 2019-08-18 9:03 ` Christoph Hellwig 2019-08-18 9:03 ` Christoph Hellwig 2019-08-16 6:54 ` [PATCH 2/4] memremap: remove the dev field in struct dev_pagemap Christoph Hellwig 2019-08-16 6:54 ` Christoph Hellwig 2019-08-16 6:54 ` [PATCH 3/4] memremap: don't use a separate devm action for devmap_managed_enable_get Christoph Hellwig 2019-08-16 6:54 ` Christoph Hellwig 2019-08-16 6:54 ` [PATCH 4/4] memremap: provide a not device managed memremap_pages Christoph Hellwig 2019-08-16 6:54 ` Christoph Hellwig 2019-08-16 21:00 ` Andrew Morton 2019-08-16 21:00 ` Andrew Morton 2019-08-18 9:04 ` Christoph Hellwig 2019-08-18 9:04 ` Christoph Hellwig 2019-08-16 10:48 ` add a not device managed memremap_pages v2 Bharata B Rao 2019-08-16 12:34 ` Jason Gunthorpe 2019-08-16 12:36 ` Christoph Hellwig 2019-08-16 12:40 ` Jason Gunthorpe 2019-08-16 12:40 ` Jason Gunthorpe 2019-08-16 23:59 ` Ira Weiny 2019-08-16 23:59 ` Ira Weiny
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190816065434.2129-1-hch@lst.de \ --to=hch@lst.de \ --cc=akpm@linux-foundation.org \ --cc=bharata@linux.ibm.com \ --cc=dan.j.williams@intel.com \ --cc=jgg@mellanox.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-nvdimm@lists.01.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.