[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201116074555.GA4758@kernel.org>
Date: Mon, 16 Nov 2020 09:45:55 +0200
From: Mike Rapoport <rppt@...nel.org>
To: Faiyaz Mohammed <faiyazm@...eaurora.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
vinmenon@...eaurora.org
Subject: Re: [PATCH v2] mm: memblock: add more debug logs
On Mon, Nov 16, 2020 at 10:14:04AM +0530, Faiyaz Mohammed wrote:
> It is useful to know the exact caller of memblock_phys_alloc_range() to
> track early memory reservations during development.
>
> Currently, when memblock debugging is enabled, the allocations done with
> memblock_phys_alloc_range() are only reported at memblock_reserve():
>
> [ 0.000000] memblock_reserve: [0x000000023fc6b000-0x000000023fc6bfff] memblock_alloc_range_nid+0xc0/0x188
>
> Add memblock_dbg() to memblock_phys_alloc_range() to get details about
> its usage.
>
> For example:
>
> [ 0.000000] memblock_phys_alloc_range: 4096 bytes align=0x1000 from=0x0000000000000000 max_addr=0x0000000000000000 early_pgtable_alloc+0x24/0x178
> [ 0.000000] memblock_reserve: [0x000000023fc6b000-0x000000023fc6bfff] memblock_alloc_range_nid+0xc0/0x188
>
> Signed-off-by: Faiyaz Mohammed <faiyazm@...eaurora.org>
Applied, thanks!
Powered by blists - more mailing lists