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=-9.0 required=3.0 tests=BAYES_00,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable 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 A88BFC11F67 for ; Wed, 14 Jul 2021 13:51:08 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 3C74561374 for ; Wed, 14 Jul 2021 13:51:08 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3C74561374 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 7DBB36B0036; Wed, 14 Jul 2021 09:51:08 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 7B2966B0071; Wed, 14 Jul 2021 09:51:08 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 679C36B0083; Wed, 14 Jul 2021 09:51:08 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0161.hostedemail.com [216.40.44.161]) by kanga.kvack.org (Postfix) with ESMTP id 43B5C6B0036 for ; Wed, 14 Jul 2021 09:51:08 -0400 (EDT) Received: from smtpin23.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 2173F185831D8 for ; Wed, 14 Jul 2021 13:51:07 +0000 (UTC) X-FDA: 78361329774.23.8DD7C2E Received: from mail-io1-f43.google.com (mail-io1-f43.google.com [209.85.166.43]) by imf24.hostedemail.com (Postfix) with ESMTP id D7953B0000AE for ; Wed, 14 Jul 2021 13:51:06 +0000 (UTC) Received: by mail-io1-f43.google.com with SMTP id h6so2150024iok.6 for ; Wed, 14 Jul 2021 06:51:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=50++kkpNpej8/NTD9q8DshcKL4G56n58bwfZ59/K0OU=; b=AXHvm29D4FgLqwZWICWyAZV3OsX7wt1JjbdZfvdCtSLcYYkrxmW77hIxng+ZHzlbTz NBFPNUe/g1A2PwyY96Q3g6WHHevUHfaXJseR5pYCb95NVp/4k3yb+s+fh5Az2v/WQaKZ THWe/uHIpuA4CCIQBZrW4R8Ner6KdEh873LQ4yOP7oD8ZQtJtS+POc7o6x1Jm2mDa54y CLQVqjm45/jHlldf/I/YFT1r1tmbiff9bCadST+BVWaJFud5PL87iVUyaS1yKUWOiSWZ C6Ie2p2KaFbgbo1gptT4WfDrKMbEmtbP5ycdsEmhKh7hlV3yCLGyrcSRCeXNGs26SE61 hLFw== X-Gm-Message-State: AOAM5311aTy282bkovED0AGENpDg4MZclMblp0+QA8ueh6kVZQorMTpo VKxJPA8bNGWyq8YOYy/uZg== X-Google-Smtp-Source: ABdhPJz5/RWe5S4IxADEtcsCGrwyKwDJjXmmQQVnQ78apEZMiVvJE4pVvZlqoWl7Or2AdYCn9IOTUQ== X-Received: by 2002:a02:7093:: with SMTP id f141mr8988326jac.24.1626270666077; Wed, 14 Jul 2021 06:51:06 -0700 (PDT) Received: from robh.at.kernel.org ([64.188.179.248]) by smtp.gmail.com with ESMTPSA id s2sm1323967ilq.45.2021.07.14.06.51.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 14 Jul 2021 06:51:05 -0700 (PDT) Received: (nullmailer pid 2459772 invoked by uid 1000); Wed, 14 Jul 2021 13:51:01 -0000 Date: Wed, 14 Jul 2021 07:51:01 -0600 From: Rob Herring To: Geert Uytterhoeven Cc: Russell King , Nicolas Pitre , Ard Biesheuvel , Linus Walleij , Catalin Marinas , Will Deacon , Nick Kossifidis , Paul Walmsley , Palmer Dabbelt , Albert Ou , Frank Rowand , Dave Young , Mike Rapoport , Baoquan He , Vivek Goyal , Andrew Morton , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-riscv@lists.infradead.org, kexec@lists.infradead.org, linux-mm@kvack.org, linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 02/10] memblock: Add variables for usable memory limitation Message-ID: <20210714135101.GB2441138@robh.at.kernel.org> References: <04c4d231fb03a3810d72a45c8a5bc2272c5975f3.1626266516.git.geert+renesas@glider.be> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <04c4d231fb03a3810d72a45c8a5bc2272c5975f3.1626266516.git.geert+renesas@glider.be> X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: D7953B0000AE X-Stat-Signature: kgmu8sk49of9rdiijy8tu1cdypdme3t6 Authentication-Results: imf24.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=kernel.org (policy=none); spf=pass (imf24.hostedemail.com: domain of robherring2@gmail.com designates 209.85.166.43 as permitted sender) smtp.mailfrom=robherring2@gmail.com X-HE-Tag: 1626270666-726221 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, Jul 14, 2021 at 02:50:12PM +0200, Geert Uytterhoeven wrote: > Add two global variables (cap_mem_addr and cap_mem_size) for storing a > base address and size, describing a limited region in which memory may > be considered available for use by the kernel. If enabled, memory > outside of this range is not available for use. > > These variables can by filled by firmware-specific code, and used in > calls to memblock_cap_memory_range() by architecture-specific code. > An example user is the parser of the "linux,usable-memory-range" > property in the DT "/chosen" node. > > Signed-off-by: Geert Uytterhoeven > --- > This is similar to how the initial ramdisk (phys_initrd_{start,size}) > and ELF core headers (elfcorehdr_{addr,size})) are handled. > > Does there exist a suitable place in the common memblock code to call > "memblock_cap_memory_range(cap_mem_addr, cap_mem_size)", or does this > have to be done in architecture-specific code? Can't you just call it from early_init_dt_scan_usablemem? If the property is present, you want to call it. If the property is not present, nothing happens. Rob