From: Wei Yang <richard.weiyang@gmail.com>
To: Jaewon Kim <jaewon31.kim@gmail.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
Jaewon Kim <jaewon31.kim@samsung.com>,
Mike Rapoport <rppt@kernel.org>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tkjos@google.com" <tkjos@google.com>,
Pintu Agarwal <pintu.ping@gmail.com>
Subject: Re: (2) [RESEND PATCH 00/10] memblock: introduce memsize showing reserved memory
Date: Thu, 30 May 2024 00:03:01 +0000 [thread overview]
Message-ID: <20240530000301.zvirmigx3pdw474w@master> (raw)
In-Reply-To: <CAJrd-UuiDq-o=r7tK=CG6Q3yeARQBEAtaov2yqO6e6tBwJZoqQ@mail.gmail.com>
On Wed, May 29, 2024 at 10:10:29PM +0900, Jaewon Kim wrote:
>(Sorry I might forget to change to be plain text)
>
>Oh good thing, I did not know this patch. Thanks.
>
>By the way, I've tried to get memblock/memory and kernel log from a
>device based on
>v6.6.17 kernel device, to see upstream patches above.
>memblok/memory does not show region for
memblock/memory only shows ranges put in "memory".
memblock/reserved shows ranges put in "reserved".
If we just put them in "reserved", it will not displayed in "memory".
>0x00000000_80000000..0x0x00000000_8195ffff.
>
> 0: 0x0000000081960000..0x00000000819fffff 0 NONE
>
>The kernel log shows information for 0x0000000080000000..0x00000000813fffff, but
>we don't see information for 0x0000000081400000..0x000000008195ffff
>from kernel log.
>
>(I removed the name.)
><6>[ 0.000000][ T0] OF: reserved mem:
>0x0000000080000000..0x0000000080dfffff (14336 KiB) nomap non-reusable
>AAA
><6>[ 0.000000][ T0] OF: reserved mem:
>0x0000000080e00000..0x00000000811fffff (4096 KiB) nomap non-reusable
>BBB
><6>[ 0.000000][ T0] OF: reserved mem:
>0x0000000081200000..0x00000000813fffff (2048 KiB) nomap non-reusable
>CCC
><6>[ 0.000000][ T0] OF: reserved mem:
>0x0000000081a00000..0x0000000081a3ffff (256 KiB) nomap non-reusable DD
>
I guess those ranges are only put into "reserved"? Have those ranges put in
"memory"? Would you mind point the code where those messages are printed?
>A smart parser should gather these kernel log and memblock/memory log
>and should show
>log like my memsize logic shows below.
>0x0000000081400000-0x0000000081960000 0x00560000 ( 5504 KB ) nomap
>unusable unknown
>
>Thank you
>Jaewon
>
>On Wed, May 29, 2024 at 8:35 PM Wei Yang <richard.weiyang@gmail.com> wrote:
>>
>> On Wed, May 29, 2024 at 06:51:19PM +0900, Jaewon Kim wrote:
>> ><!DOCTYPE html>
>> ><html>
>> ><head>
>> ...
>>
>> Would you mind sending it in pure text again?
>>
>> --
>> Wei Yang
>> Help you, Help me
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2024-05-30 0:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240521024009epcas1p10ed9f9b929203183a29f79508e79bb76@epcas1p1.samsung.com>
2024-05-21 2:39 ` [RESEND PATCH 00/10] memblock: introduce memsize showing reserved memory Jaewon Kim
2024-05-21 2:39 ` [RESEND PATCH 01/10] " Jaewon Kim
2024-05-21 2:39 ` [RESEND PATCH 02/10] memblock: detect hidden memory hole size Jaewon Kim
2024-05-21 2:39 ` [RESEND PATCH 03/10] memblock: handle overlapped reserved memory region Jaewon Kim
2024-05-21 2:39 ` [RESEND PATCH 04/10] memblock: take a region intersecting an unknown region Jaewon Kim
2024-05-21 2:39 ` [RESEND PATCH 05/10] memblock: track memblock changed at early param Jaewon Kim
2024-05-21 2:39 ` [RESEND PATCH 06/10] memblock: recognize late freed size by checking PageReserved Jaewon Kim
2024-05-21 2:39 ` [RESEND PATCH 07/10] memblock: track kernel size on memsize Jaewon Kim
2024-05-22 19:03 ` kernel test robot
2024-05-21 2:39 ` [RESEND PATCH 08/10] memblock: print memsize summary information Jaewon Kim
2024-05-21 2:39 ` [RESEND PATCH 09/10] memblock: print kernel internal size Jaewon Kim
2024-05-22 18:52 ` kernel test robot
2024-05-21 2:39 ` [RESEND PATCH 10/10] memblock: support memsize reusable to consider as reusable Jaewon Kim
2024-05-22 22:40 ` kernel test robot
2024-05-23 10:55 ` Jaewon Kim
2024-05-21 2:53 ` [RESEND PATCH 00/10] memblock: introduce memsize showing reserved memory Jaewon Kim
2024-05-21 7:31 ` Mike Rapoport
2024-05-21 10:17 ` Jaewon Kim
2024-05-22 8:16 ` (2) " Wei Yang
2024-05-22 8:47 ` Jaewon Kim
2024-05-23 8:55 ` Wei Yang
2024-05-23 9:23 ` 김재원
2024-05-23 14:34 ` (2) " Mike Rapoport
2024-05-24 9:07 ` Jaewon Kim
2024-05-26 13:55 ` Mike Rapoport
2024-05-27 1:30 ` Jaewon Kim
2024-05-27 1:35 ` Jaewon Kim
2024-05-27 16:22 ` Mike Rapoport
[not found] ` <CGME20240521024009epcas1p10ed9f9b929203183a29f79508e79bb76@epcms1p7>
[not found] ` <20240529095119epcms1p73f0e9ff756bcb2ee6a14db459128a644@epcms1p7>
2024-05-29 11:35 ` Wei Yang
2024-05-29 13:10 ` Jaewon Kim
2024-05-30 0:03 ` Wei Yang [this message]
2024-05-30 10:49 ` Jaewon Kim
2024-05-31 1:05 ` (2) " Wei Yang
2024-05-31 8:21 ` Jaewon Kim
2024-06-01 1:40 ` Wei Yang
2024-06-03 9:33 ` Jaewon Kim
2024-05-24 17:33 ` Pintu Agarwal
2024-05-22 8:20 ` Wei Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240530000301.zvirmigx3pdw474w@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jaewon31.kim@gmail.com \
--cc=jaewon31.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pintu.ping@gmail.com \
--cc=rppt@kernel.org \
--cc=tkjos@google.com \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.