On Thu, 23 May 2024 at 20:06, Mike Rapoport <rppt@xxxxxxxxxx> wrote: > > On Tue, May 21, 2024 at 07:17:53PM +0900, Jaewon Kim wrote: > > >On Tue, May 21, 2024 at 11:53:29AM +0900, Jaewon Kim wrote: > > >> >--------- Original Message --------- > > >> >Sender : 김재원 <jaewon31.kim@xxxxxxxxxxx>System Performance Lab.(MX)/삼성전자 > > >> >Date : 2024-05-21 11:40 (GMT+9) > > >> >Title : [RESEND PATCH 00/10] memblock: introduce memsize showing reserved memory > > >> >? > > >> >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. Something similar, we have already proposed almost 10 years ago for memblock. That time I realised some of these reserved memory break-up becomes useful and handy when we are gathering reserved memory stats on a small embedded device where every bit of memory reserved is important and being questioned. You can get some information about Kernel reserved from dmesg | grep -i Memory (including the kernel init, text, data) and the cma-reserved as well. Here the cma-reserved was added by me. You can also get these Kernel reserved size info from vmlinux. size -t vmlinux
