The patch titled Subject: mm/memblock: print memblock_remove has been added to the -mm tree. Its filename is mm-memblock-print-memblock_remove.patch This patch should soon appear at http://ozlabs.org/~akpm/mmots/broken-out/mm-memblock-print-memblock_remove.patch and later at http://ozlabs.org/~akpm/mmotm/broken-out/mm-memblock-print-memblock_remove.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Minchan Kim <minchan@xxxxxxxxxx> Subject: 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@xxxxxxxxxx Signed-off-by: Minchan Kim <minchan@xxxxxxxxxx> Cc: Michal Hocko <mhocko@xxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/memblock.c | 5 +++++ 1 file changed, 5 insertions(+) diff -puN mm/memblock.c~mm-memblock-print-memblock_remove mm/memblock.c --- a/mm/memblock.c~mm-memblock-print-memblock_remove +++ a/mm/memblock.c @@ -697,6 +697,11 @@ static int __init_memblock memblock_remo 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); } _ Patches currently in -mm which might be from minchan@xxxxxxxxxx are zram-correct-flag-name-of-zram_access.patch zram-mark-incompressible-page-as-zram_huge.patch zram-record-accessed-second.patch zram-introduce-zram-memory-tracking.patch zram-introduce-zram-memory-tracking-update.patch mm-memblock-print-memblock_remove.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html