Faiyaz Mohammed f2f8d7326a UPSTREAM: mm: memblock: add more debug logs ...

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@codeaurora.org>
Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
Bug: 187741816
(cherry picked from commit b5cf2d6c814829b623ccedce88d94e7bfe35cb2c
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)

Change-Id: I7fb49411513a151f0c9dbb8774f489a59e776ac0
Signed-off-by: Vijayanand Jitta <vjitta@codeaurora.org>

2021-05-21 09:08:08 +05:30

57 KiB

Raw Blame History

View Raw