From: Andrew Morton <akpm@linux-foundation.org>
To: Faiyaz Mohammed <faiyazm@codeaurora.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
david@redhat.com, guptap@codeaurora.org,
Mike Rapoport <rppt@kernel.org>
Subject: Re: [PATCH v4] mm: page_alloc: Add debug log in free_reserved_area for static memory
Date: Mon, 18 Oct 2021 11:00:02 -0700 [thread overview]
Message-ID: <20211018110002.596d03206aa849eec06d11f5@linux-foundation.org> (raw)
In-Reply-To: <1634540053-23304-1-git-send-email-faiyazm@codeaurora.org>
On Mon, 18 Oct 2021 12:24:13 +0530 Faiyaz Mohammed <faiyazm@codeaurora.org> wrote:
> For INITRD and initmem memory is reserved through "memblock_reserve"
> during boot up but it is free via "free_reserved_area" instead
> of "memblock_free".
> For example:
> [ 0.294848] Freeing initrd memory: 12K.
> [ 0.696688] Freeing unused kernel memory: 4096K.
>
> To get the start and end address of the above freed memory and to account
> proper memblock added pr_debug log in "free_reserved_area".
> After adding log:
> [ 0.294837] 0x00000083600000-0x00000083603000 free_initrd_mem+0x20/0x28
> [ 0.294848] Freeing initrd memory: 12K.
> [ 0.695246] 0x00000081600000-0x00000081a00000 free_initmem+0x70/0xc8
> [ 0.696688] Freeing unused kernel memory: 4096K.
The above log appears to have things backwards. I assume you meant
> [ 0.294848] Freeing initrd memory: 12K.
> [ 0.294837] 0x00000083600000-0x00000083603000 free_initrd_mem+0x20/0x28
> [ 0.696688] Freeing unused kernel memory: 4096K.
> [ 0.695246] 0x00000081600000-0x00000081a00000 free_initmem+0x70/0xc8
next prev parent reply other threads:[~2021-10-18 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 6:54 Faiyaz Mohammed
2021-10-18 18:00 ` Andrew Morton [this message]
2021-10-19 2:50 ` [mm] f859d2a494: kernel_BUG_at_arch/x86/mm/physaddr.c kernel test robot
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=20211018110002.596d03206aa849eec06d11f5@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=faiyazm@codeaurora.org \
--cc=guptap@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox