From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (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 4FAF92021C1B7 for ; Sun, 18 Aug 2019 02:06:16 -0700 (PDT) Date: Sun, 18 Aug 2019 11:04:37 +0200 From: Christoph Hellwig Subject: Re: [PATCH 4/4] memremap: provide a not device managed memremap_pages Message-ID: <20190818090437.GB20462@lst.de> References: <20190816065434.2129-1-hch@lst.de> <20190816065434.2129-5-hch@lst.de> <20190816140057.c1ab8b41b9bfff65b7ea83ba@linux-foundation.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20190816140057.c1ab8b41b9bfff65b7ea83ba@linux-foundation.org> 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: Andrew Morton Cc: linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org, Bharata B Rao , linux-mm@kvack.org, Jason Gunthorpe , Christoph Hellwig List-ID: On Fri, Aug 16, 2019 at 02:00:57PM -0700, Andrew Morton wrote: > On Fri, 16 Aug 2019 08:54:34 +0200 Christoph Hellwig wrote: > > > The kvmppc ultravisor code wants a device private memory pool that is > > system wide and not attached to a device. Instead of faking up one > > provide a low-level memremap_pages for it. Note that this function is > > not exported, and doesn't have a cleanup routine associated with it to > > discourage use from more driver like users. > > Confused. Which function is "not exported"? Leftover from v1 and dropped now. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E384AC3A589 for ; Sun, 18 Aug 2019 09:04:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BD1152086C for ; Sun, 18 Aug 2019 09:04:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726638AbfHRJEl (ORCPT ); Sun, 18 Aug 2019 05:04:41 -0400 Received: from verein.lst.de ([213.95.11.211]:39060 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726208AbfHRJEl (ORCPT ); Sun, 18 Aug 2019 05:04:41 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 974F1227A81; Sun, 18 Aug 2019 11:04:37 +0200 (CEST) Date: Sun, 18 Aug 2019 11:04:37 +0200 From: Christoph Hellwig To: Andrew Morton Cc: Christoph Hellwig , Dan Williams , Jason Gunthorpe , Bharata B Rao , linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org Subject: Re: [PATCH 4/4] memremap: provide a not device managed memremap_pages Message-ID: <20190818090437.GB20462@lst.de> References: <20190816065434.2129-1-hch@lst.de> <20190816065434.2129-5-hch@lst.de> <20190816140057.c1ab8b41b9bfff65b7ea83ba@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190816140057.c1ab8b41b9bfff65b7ea83ba@linux-foundation.org> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 16, 2019 at 02:00:57PM -0700, Andrew Morton wrote: > On Fri, 16 Aug 2019 08:54:34 +0200 Christoph Hellwig wrote: > > > The kvmppc ultravisor code wants a device private memory pool that is > > system wide and not attached to a device. Instead of faking up one > > provide a low-level memremap_pages for it. Note that this function is > > not exported, and doesn't have a cleanup routine associated with it to > > discourage use from more driver like users. > > Confused. Which function is "not exported"? Leftover from v1 and dropped now.