diff options
| author | Faiyaz Mohammed <[email protected]> | 2020-11-16 04:44:04 +0000 |
|---|---|---|
| committer | Mike Rapoport <[email protected]> | 2020-11-16 07:32:39 +0000 |
| commit | b5cf2d6c814829b623ccedce88d94e7bfe35cb2c (patch) | |
| tree | adb5dff3f0c4ad3be626ab06f00f57243147416b /fs/ext4/fast_commit.c | |
| parent | Linux 5.10-rc4 (diff) | |
| download | kernel-b5cf2d6c814829b623ccedce88d94e7bfe35cb2c.tar.gz kernel-b5cf2d6c814829b623ccedce88d94e7bfe35cb2c.zip | |
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 <[email protected]>
Signed-off-by: Mike Rapoport <[email protected]>
Diffstat (limited to 'fs/ext4/fast_commit.c')
0 files changed, 0 insertions, 0 deletions