From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f71.google.com (mail-oi0-f71.google.com [209.85.218.71]) by kanga.kvack.org (Postfix) with ESMTP id 6816E6B0006 for ; Thu, 7 Jun 2018 14:39:46 -0400 (EDT) Received: by mail-oi0-f71.google.com with SMTP id n63-v6so6159201oig.21 for ; Thu, 07 Jun 2018 11:39:46 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id u28-v6sor14464428ote.11.2018.06.07.11.39.45 for (Google Transport Security); Thu, 07 Jun 2018 11:39:45 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20180607141640.GA4518@redhat.com> References: <20180605184811.GC4423@redhat.com> <20180606000822.GE4423@redhat.com> <20180607141640.GA4518@redhat.com> From: Dan Williams Date: Thu, 7 Jun 2018 11:39:44 -0700 Message-ID: Subject: Re: [PATCH 0/5] mm: rework hmm to use devm_memremap_pages Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Jerome Glisse Cc: Dave Airlie , Andrew Morton , Logan Gunthorpe , Christoph Hellwig , Michal Hocko , Linux MM , Linux Kernel Mailing List On Thu, Jun 7, 2018 at 7:16 AM, Jerome Glisse wrote: [..] > HMM is self contain interface but i doubt i can convince you of that. I agree that HMM is self contained... after it completely subverts the core-mm. It's that deep understanding and working around of core memory management infrastructure that makes devm_memremap_pages() and derivatives EXPORT_SYMBOL_GPL ("considered an internal implementation issue, and not really an interface").