mm/memblock: print memblock_remove
memblock_remove report is useful to see why MemTotal of /proc/meminfo between two kernels makes difference. Link: http://lkml.kernel.org/r/20180508104223.8028-1-minchan@kernel.org Signed-off-by: Minchan Kim <minchan@kernel.org> Reviewed-by: Andrew Morton <akpm@linux-foundation.org> Acked-by: Michal Hocko <mhocko@suse.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
d12c60f64c
commit
25cf23d7a9
|
@ -697,6 +697,11 @@ static int __init_memblock memblock_remove_range(struct memblock_type *type,
|
||||||
|
|
||||||
int __init_memblock memblock_remove(phys_addr_t base, phys_addr_t size)
|
int __init_memblock memblock_remove(phys_addr_t base, phys_addr_t size)
|
||||||
{
|
{
|
||||||
|
phys_addr_t end = base + size - 1;
|
||||||
|
|
||||||
|
memblock_dbg("memblock_remove: [%pa-%pa] %pS\n",
|
||||||
|
&base, &end, (void *)_RET_IP_);
|
||||||
|
|
||||||
return memblock_remove_range(&memblock.memory, base, size);
|
return memblock_remove_range(&memblock.memory, base, size);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue