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=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham 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 91F70C10F11 for ; Wed, 24 Apr 2019 10:50:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 66BE421773 for ; Wed, 24 Apr 2019 10:50:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728610AbfDXKuB (ORCPT ); Wed, 24 Apr 2019 06:50:01 -0400 Received: from foss.arm.com ([217.140.101.70]:41472 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726830AbfDXKuB (ORCPT ); Wed, 24 Apr 2019 06:50:01 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id CFA83A78; Wed, 24 Apr 2019 03:50:00 -0700 (PDT) Received: from [10.163.1.68] (unknown [10.163.1.68]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 179573F5AF; Wed, 24 Apr 2019 03:49:58 -0700 (PDT) Subject: Re: [PATCH] docs/vm: add documentation of memory models To: Mike Rapoport , Jonathan Corbet Cc: linux-doc@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org References: <1556101715-31966-1-git-send-email-rppt@linux.ibm.com> From: Anshuman Khandual Message-ID: Date: Wed, 24 Apr 2019 16:20:02 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1556101715-31966-1-git-send-email-rppt@linux.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/24/2019 03:58 PM, Mike Rapoport wrote: > +To use vmemmap, an architecture has to reserve a range of virtual > +addresses that will map the physical pages containing the memory > +map. and make sure that `vmemmap` points to that range. In addition, > +the architecture should implement :c:func:`vmemmap_populate` method > +that will allocate the physical memory and create page tables for the > +virtual memory map. If an architecture does not have any special > +requirements for the vmemmap mappings, it can use default > +:c:func:`vmemmap_populate_basepages` provided by the generic memory > +management. Just to complete it, could you also include struct vmem_altmap and how it can contribute towards the physical backing for vmemmap virtual mapping. Otherwise the write up looks complete.