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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 38B4FC433EF for ; Fri, 25 Mar 2022 07:46:41 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 774B56B0071; Fri, 25 Mar 2022 03:46:40 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 723BA8D0001; Fri, 25 Mar 2022 03:46:40 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 5EB8D6B0074; Fri, 25 Mar 2022 03:46:40 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0175.hostedemail.com [216.40.44.175]) by kanga.kvack.org (Postfix) with ESMTP id 4FBED6B0071 for ; Fri, 25 Mar 2022 03:46:40 -0400 (EDT) Received: from smtpin30.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id DDEAB86311 for ; Fri, 25 Mar 2022 07:46:39 +0000 (UTC) X-FDA: 79282126518.30.80EB701 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf10.hostedemail.com (Postfix) with ESMTP id 61243C002A for ; Fri, 25 Mar 2022 07:46:39 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id B58FA61A1E; Fri, 25 Mar 2022 07:46:38 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id DA036C340E9; Fri, 25 Mar 2022 07:46:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648194398; bh=mhnz9m6G+ghJ/c67sYiI4HzhlXpK6Em9Vo4Mqbapwuw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=EvQGqDqqnUSxKTt2t0t4cWF1xH287iAC8iM8/isfkxlA0f+qsJH/EkrE1wOFuhBWc 2sRBpIYRJximcGYj3lJBeuD3wcR0c4lqI+MnS53WmYC6JOKImEVCMzWofRpuo4O3kx LYH+aOUGiWRy6L0xwhq48RVSyJfQagn312WjdW9yiYrt4DWlMnFZLah1Y1lS4AMXem YYSCByZf6uDud6Jt/jnW8bWVab0LoF/97uqljKBaTaWvNFR0+TaDujhsjuaGl0rhZK p++qDnbWvoSd6Thd0a85Swa0zuG685IXpE6M8Eu6aw6WG/CcALKLdpx+89H56yslvT kWIeJmH2v0Sew== Date: Fri, 25 Mar 2022 10:46:30 +0300 From: Mike Rapoport To: Jaewon Kim Cc: vbabka@suse.cz, akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, ytk.lee@samsung.com, jaewon31.kim@gmail.com Subject: Re: [PATCH 0/8] memblock: introduce memsize showing reserved memory Message-ID: References: <20220324070158.22969-1-jaewon31.kim@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220324070158.22969-1-jaewon31.kim@samsung.com> X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: 61243C002A X-Stat-Signature: gf1no38fux8hgt7m9sgtfz3m4gma1kr8 Authentication-Results: imf10.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=EvQGqDqq; dmarc=pass (policy=none) header.from=kernel.org; spf=pass (imf10.hostedemail.com: domain of rppt@kernel.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=rppt@kernel.org X-Rspam-User: X-HE-Tag: 1648194399-276272 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: Hi, On Thu, Mar 24, 2022 at 04:01:50PM +0900, Jaewon Kim wrote: > Some of memory regions can be reserved for a specific purpose. They are > usually defined through reserved-memory in device tree. If only size > without address is specified in device tree, the address of the region > will be determined at boot time. > > We may find the address of the memory regions through booting log, but > it does not show all. And it could be hard to catch the very beginning > log. The memblock_dump_all shows all memblock status but it does not > show region name and its information is difficult to summarize. > > This patch introduce a debugfs node, memblock/memsize, to see reserved > memory easily. > > Here's an example > > $ cat debugfs/memblock/memsize > 0x0f9000000-0x0fb000000 0x02000000 ( 32768 KB ) map reusable linux,cma > 0x0b1900000-0x0b1b00000 0x00200000 ( 2048 KB ) nomap unusable test1 > 0x0b0200000-0x0b0400000 0x00200000 ( 2048 KB ) map unusable test2 > (snipped) > > Reserved : 746924 KB > .kernel : 137027 KB > .text : 28158 KB > .rwdata : 3238 KB > .rodata : 13468 KB > .bss : 12570 KB > .etc : 79593 KB > .unusable : 609897 KB > System : 3447380 KB > .common : 3152468 KB > .reusable : 294912 KB > Total : 4194304 KB ( 4096.00 MB ) Most of this information information is already available at various places, like the existing memblock debugfs, /proc/iomem and DT sysfs. I don't see why we need yet another debugfs file to expose it. > Jaewon Kim (8): > memblock: introduce memsize showing reserved memory > memblock: detect hidden memory hole size > memblock: handle overlapped reserved memory region > memblock: track memblock changed at early param > memblock: track kernel size on memsize > memblock: recognize late free by checking PageReserved > memblock: print memsize summary information > memblock: print kernel internal size > > drivers/of/fdt.c | 10 + > drivers/of/of_reserved_mem.c | 7 +- > include/linux/memblock.h | 21 ++ > include/linux/mm.h | 3 + > init/main.c | 13 +- > kernel/dma/contiguous.c | 9 +- > mm/Kconfig | 7 + > mm/memblock.c | 434 ++++++++++++++++++++++++++++++++++- > mm/page_alloc.c | 15 +- > 9 files changed, 506 insertions(+), 13 deletions(-) > > -- > 2.17.1 > -- Sincerely yours, Mike.