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 0C0F2C433EF for ; Tue, 29 Mar 2022 02:46:31 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 634A28D0003; Mon, 28 Mar 2022 22:46:31 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 5E8408D0001; Mon, 28 Mar 2022 22:46:31 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 484D48D0003; Mon, 28 Mar 2022 22:46:31 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.28]) by kanga.kvack.org (Postfix) with ESMTP id 39A758D0001 for ; Mon, 28 Mar 2022 22:46:31 -0400 (EDT) Received: from smtpin09.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay11.hostedemail.com (Postfix) with ESMTP id 0A621807B9 for ; Tue, 29 Mar 2022 02:46:31 +0000 (UTC) X-FDA: 79295885382.09.85125A1 Received: from mailout4.samsung.com (mailout4.samsung.com [203.254.224.34]) by imf22.hostedemail.com (Postfix) with ESMTP id 68DDDC0003 for ; Tue, 29 Mar 2022 02:46:29 +0000 (UTC) Received: from epcas1p1.samsung.com (unknown [182.195.41.45]) by mailout4.samsung.com (KnoxPortal) with ESMTP id 20220329024626epoutp042fe617845683219662ef3cad5becee7e~gugMjCbux1457714577epoutp04c for ; Tue, 29 Mar 2022 02:46:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout4.samsung.com 20220329024626epoutp042fe617845683219662ef3cad5becee7e~gugMjCbux1457714577epoutp04c DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1648521986; bh=Jb0zVmXE6FZXq1tlAr4YAjL1vUog6bxPPj7i8N6C7MI=; h=Subject:Reply-To:From:To:CC:In-Reply-To:Date:References:From; b=I2uy2rU3LvZ93uIQ/KckuVybhE+uY5dYpXE32/MV/MoS4rSCTbUovh61TNsu+3nuP yJyk5yargmtBF3PkN24wFzKuUlAHUfmGX0qjTN9BLJ/a3+eFex/Vu4uRydXu51oUSr frYMP6xCqgCPWfXk0SzCTFoOdKbioJbWleGyk7wM= Received: from epsnrtp2.localdomain (unknown [182.195.42.163]) by epcas1p4.samsung.com (KnoxPortal) with ESMTP id 20220329024625epcas1p43212b4fb9e4759d1232d065af0dcf4fa~gugMPIIzR0984209842epcas1p45; Tue, 29 Mar 2022 02:46:25 +0000 (GMT) Received: from epsmges1p2.samsung.com (unknown [182.195.38.250]) by epsnrtp2.localdomain (Postfix) with ESMTP id 4KSDTr31Pmz4x9Pt; Tue, 29 Mar 2022 02:46:24 +0000 (GMT) X-AuditID: b6c32a36-203ff70000002055-2f-624272fc68a2 Received: from epcas1p1.samsung.com ( [182.195.41.45]) by epsmges1p2.samsung.com (Symantec Messaging Gateway) with SMTP id 64.69.08277.CF272426; Tue, 29 Mar 2022 11:46:20 +0900 (KST) Mime-Version: 1.0 Subject: RE: [PATCH 0/8] memblock: introduce memsize showing reserved memory Reply-To: jaewon31.kim@samsung.com From: Jaewon Kim To: Mike Rapoport , Jaewon Kim CC: "vbabka@suse.cz" , "akpm@linux-foundation.org" , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , YongTaek Lee , "jaewon31.kim@gmail.com" X-Priority: 3 X-Content-Kind-Code: NORMAL In-Reply-To: X-Drm-Type: N,general X-Msg-Generator: Mail X-Msg-Type: PERSONAL X-Reply-Demand: N Message-ID: <20220329024620epcms1p7633018e83f54e532761008a60da5254f@epcms1p7> Date: Tue, 29 Mar 2022 11:46:20 +0900 X-CMS-MailID: 20220329024620epcms1p7633018e83f54e532761008a60da5254f Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Sendblock-Type: SVC_REQ_APPROVE X-CPGSPASS: Y X-CPGSPASS: Y CMS-TYPE: 101P X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOJsWRmVeSWpSXmKPExsWy7bCmru6fIqckgylLDS3mrF/DZvHykKZF 9+aZjBa9718xWVzeNYfN4t6a/6wWR9ZvZ7KY3djHaPF4PbcDp8fOWXfZPTat6mTz2PRpErvH iRm/WTz6tqxi9Diz4Ai7x+dNcgHsUdk2GamJKalFCql5yfkpmXnptkrewfHO8aZmBoa6hpYW 5koKeYm5qbZKLj4Bum6ZOUCHKSmUJeaUAoUCEouLlfTtbIryS0tSFTLyi0tslVILUnIKzAr0 ihNzi0vz0vXyUkusDA0MjEyBChOyM54eXspSsJy/4u6Tp8wNjDN5uhg5OSQETCSmTD/P1sXI xSEksINR4u7MS8xdjBwcvAKCEn93CIPUCAv4SLxvmsUOYgsJKEmc/XGFHSKuK9HUvZoFxGYT 0JZ4v2ASK0iriICXxJ23HiAjmQWWMklsuNHEDLGLV2JG+1MWCFtaYvvyrYwgNqeAlsSO/Z1Q cVGJm6vfssPY74/NZ4SwRSRa752FmiMo8eDnbqi4lMS57uNMIHslBCIkXuxRhwjnSLzfOYcV wjaXeLahBWwkr4CvRN/Ss2wgNouAqsTuuQehVrlI3Fh7CWwks4C8xPa3c8ChwCygKbF+lz5E iaLEzt9zGWE+adj4mx2dzSzAJ/Huaw8rTHzHvCdMELaaRMuzr1BxGYm//56xTmBUmoUI51lI Fs9CWLyAkXkVo1hqQXFuemqxYYERPGqT83M3MYJTqJbZDsZJbz/oHWJk4mA8xCjBwawkwit7 1j5JiDclsbIqtSg/vqg0J7X4EKMp0MsTmaVEk/OBSTyvJN7QxNLAxMzIxMLY0thMSZx31bTT iUIC6YklqdmpqQWpRTB9TBycUg1MZZV1psIW2ZXVQpHrH2u3rT/0q9eu8XyMl5Od2pR/k+em 7TH8tnxutX/99M3uV75eWC6nf/zvxz52zQn3/vinpa+M8p1pePZR0teiTRkKJkfeG0+oqYi+ q3/79FeGE2a/mBXS3p7jnvA3N66kKju+nrU9tW6potOzwj+zXCYd4Oz+1nuxYcM/yT+Bjcvk +hQWe9X1iNzaGLT1UDaHY/2KHwKbd8kw7BU+8fjNL1fmu55F6jefljL56N7eteDEql3JX+ak TeJXbu4tZ9g19clmX5GrGke2LOgruHDKeU3BFul3pyd86Y+VFks8Zh5qkWP8ZMnqlHiji0K+ 8llshesYZu/xEFzo4Zz8xKHc9CyTEktxRqKhFnNRcSIAZ9gvfCoEAAA= DLP-Filter: Pass X-CFilter-Loop: Reflected X-CMS-RootMailID: 20220324065919epcas1p4c79da5f6ec4fa0311409ca24a38785d8 References: <20220324070158.22969-1-jaewon31.kim@samsung.com> <20220325083846epcms1p372559472ceb511cc45d39c110563063a@epcms1p3> <20220327135347epcms1p13faf0f2b7d98d3b59b25e903678d9c48@epcms1p1> X-Rspam-User: Authentication-Results: imf22.hostedemail.com; dkim=pass header.d=samsung.com header.s=mail20170921 header.b=I2uy2rU3; spf=pass (imf22.hostedemail.com: domain of jaewon31.kim@samsung.com designates 203.254.224.34 as permitted sender) smtp.mailfrom=jaewon31.kim@samsung.com; dmarc=pass (policy=none) header.from=samsung.com X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: 68DDDC0003 X-Stat-Signature: d6c981acwxgtaiykrm6hxz1jt5775udt X-HE-Tag: 1648521989-225474 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: >> > >> >--------- Original Message --------- >> >Sender : Mike Rapoport >> >Date : 2022-03-27 16:40 (GMT+9) >> >Title : Re: [PATCH 0/8] memblock: introduce memsize showing reserved memory >> > >> > >> >I'm still not following. The reserved region sizes are available in the >> >existing memblock debugfs. >> >Why the names are important? What is the value of having names for *some* >> >of the reserved regions? >> >> Hi >> >> There are many memory regions in memblock debugfs memory/reserved, and some might >> be splited or merged with other region. Among regions in debugfs, we can't find >> the one we defined in device tree. Especially it is difficult to find the region we >> described size only without start address. >> >> On mobile environment, memory is used by not only CPU but also GPU, Camera, Secure >> world, Audio, ETC. To support them, there are many reserved regions described in >> device tree. So the name is quite important to recognize a region. And with thename >> we can compare reserved memory map with other map. > >You still didn't describe your use case. What is the problem your patches >are trying to solve? Why is it important to know what is the use of particular >reserved region? > >You propose complex mechanism that seems to fit very particular scenario >and sprinkle some calls to this mechanism at random places because you need >to "compare reserved memory map with other map". > >Does not sound convincing to me, sorry. As I said serveral times, I want a simple knob showing all reserved memory status. The current debugfs, device tree do not show all those information I want. I think you also know that. i.e. late freed pages, splited or merged memblock, address defined at boot time, kernel size, ETC. Anyway I think I touched too many points to do this. Let me drop this. > >> Thank you >> Jaewon Kim > >-- >Sincerely yours, >Mike. >