Skip to contentSkip to conversation

mm: page_alloc: Add debug log in free_reserved_area for static memory

PATCH Superseded Faiyaz Mohammed 2 participants 10 messages Sep 28, 2021 – Oct 11, 2021

Subsystems (2)

v1 of 4 Superseded Latest is v4 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 mm: page_alloc: Add debug log in free_reserved_area for static memory

For INITRD and initmem memory is reserved through "memblock_reserve" during boot up but it is free via "free_reserved_area" instead of "memblock_free".
For example:

[    0.294848] Freeing initrd memory: 12K.
[    0.696688] Freeing unused kernel memory: 4096K.

To get the start and end address of the above freed memory and to account proper memblock added memblock_dbg log in "free_reserved_area". After adding log:

[    0.294837] memblock_free: [0x00000083600000-0x00000083603000] free_initrd_mem+0x20/0x28
[    0.294848] Freeing initrd memory: 12K.
[    0.695246] memblock_free: [0x00000081600000-0x00000081a00000] free_initmem+0x70/0xc8
[    0.696688] Freeing unused kernel memory: 4096K.
---
 mm/page_alloc.c | 5 +++++
 1 file changed, 5 insertions(+)
mm/page_alloc.c +5 -0
index b37435c..f85c3b2 100644
@@ -8129,6 +8129,11 @@ unsigned long free_reserved_area(void *start, void *end, int poison, const char
 		pr_info("Freeing %s memory: %ldK\n",
 			s, pages << (PAGE_SHIFT - 10));
 
+#ifdef CONFIG_HAVE_MEMBLOCK
+		memblock_dbg("memblock_free: [%#016llx-%#016llx] %pS\n",
+			__pa(start), __pa(end), (void *)_RET_IP_);
+#endif
+
 	return pages;
 }
 
Signature · 2 lines
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member of the Code Aurora Forum, hosted by The Linux Foundation
#1 lore raw
Quoted 25 lines · Faiyaz Mohammed

For INITRD and initmem memory is reserved through "memblock_reserve" during boot up but it is free via "free_reserved_area" instead of "memblock_free".
For example:

[    0.294848] Freeing initrd memory: 12K.
[    0.696688] Freeing unused kernel memory: 4096K.

To get the start and end address of the above freed memory and to account proper memblock added memblock_dbg log in "free_reserved_area". After adding log:

[    0.294837] memblock_free: [0x00000083600000-0x00000083603000] free_initrd_mem+0x20/0x28
[    0.294848] Freeing initrd memory: 12K.
[    0.695246] memblock_free: [0x00000081600000-0x00000081a00000] free_initmem+0x70/0xc8
[    0.696688] Freeing unused kernel memory: 4096K.
---
  mm/page_alloc.c | 5 +++++
  1 file changed, 5 insertions(+)
mm/page_alloc.c +0 -0
index b37435c..f85c3b2 100644

mm/page_alloc.c unsigned long free_reserved_area(void *start, void *end, int poison, const char · line 8135

Quoted 7 lines
mm/page_alloc.c +4 -0
@@ -8129,6 +8129,11 @@ unsigned long free_reserved_area(void *start, void *end, int poison, const char
  		pr_info("Freeing %s memory: %ldK\n",
  			s, pages << (PAGE_SHIFT - 10));
 
+#ifdef CONFIG_HAVE_MEMBLOCK
+		memblock_dbg("memblock_free: [%#016llx-%#016llx] %pS\n",
+			__pa(start), __pa(end), (void *)_RET_IP_);
+#endif

IMHO, the "memblock_free" part is misleading. Something was allocated early via memblock, then we transitioned to the buddy, now we're freeing that early allocation via the buddy.

I would not expect memblock_dbg once memblock might not actually be alive anymore.

Signature · 3 lines
Thanks,

David / dhildenb
#2 lore raw
Quoted 32 lines · David Hildenbrand
Quoted 31 lines · Faiyaz Mohammed

For INITRD and initmem memory is reserved through "memblock_reserve" during boot up but it is free via "free_reserved_area" instead of "memblock_free".
For example:
[    0.294848] Freeing initrd memory: 12K.
[    0.696688] Freeing unused kernel memory: 4096K.

To get the start and end address of the above freed memory and to account proper memblock added memblock_dbg log in "free_reserved_area". After adding log:
[    0.294837] memblock_free: [0x00000083600000-0x00000083603000] free_initrd_mem+0x20/0x28
[    0.294848] Freeing initrd memory: 12K.
[    0.695246] memblock_free: [0x00000081600000-0x00000081a00000] free_initmem+0x70/0xc8
[    0.696688] Freeing unused kernel memory: 4096K.

---
  mm/page_alloc.c | 5 +++++

  1 file changed, 5 insertions(+)
mm/page_alloc.c +0 -0
index b37435c..f85c3b2 100644
@@ -8129,6 +8129,11 @@ unsigned long free_reserved_area(void *start,

void *end, int poison, const char
          pr_info("Freeing %s memory: %ldK\n",
              s, pages << (PAGE_SHIFT - 10));
  +#ifdef CONFIG_HAVE_MEMBLOCK

Quoted 8 lines
Quoted 3 lines

+        memblock_dbg("memblock_free: [%#016llx-%#016llx] %pS\n", +            __pa(start), __pa(end), (void *)_RET_IP_); +#endif

IMHO, the "memblock_free" part is misleading. Something was allocated early via memblock, then we transitioned to the buddy, now we're freeing that early allocation via the buddy.
Yes, we're freeing the early allocation via buddy, but for proper

memblock accounting we need this debug print.

Quoted 3 lines

I would not expect memblock_dbg once memblock might not actually be alive anymore.

Here we can add pr_info as well, but the intention is to get callsite and address info when the memblock=debug is pass through command line and it is for debugging purpose.

Thanks and regards,
Mohammed Faiyaz

#3 lore raw
Quoted 43 lines · Faiyaz Mohammed
Quoted 32 lines · David Hildenbrand
Quoted 31 lines · Faiyaz Mohammed

For INITRD and initmem memory is reserved through "memblock_reserve" during boot up but it is free via "free_reserved_area" instead of "memblock_free".
For example:
[    0.294848] Freeing initrd memory: 12K.
[    0.696688] Freeing unused kernel memory: 4096K.

To get the start and end address of the above freed memory and to account proper memblock added memblock_dbg log in "free_reserved_area". After adding log:
[    0.294837] memblock_free: [0x00000083600000-0x00000083603000] free_initrd_mem+0x20/0x28
[    0.294848] Freeing initrd memory: 12K.
[    0.695246] memblock_free: [0x00000081600000-0x00000081a00000] free_initmem+0x70/0xc8
[    0.696688] Freeing unused kernel memory: 4096K.

---
   mm/page_alloc.c | 5 +++++
   1 file changed, 5 insertions(+)
mm/page_alloc.c +0 -0
index b37435c..f85c3b2 100644
@@ -8129,6 +8129,11 @@ unsigned long free_reserved_area(void *start,

void *end, int poison, const char
          pr_info("Freeing %s memory: %ldK\n",
              s, pages << (PAGE_SHIFT - 10));
  +#ifdef CONFIG_HAVE_MEMBLOCK

Quoted 8 lines
Quoted 3 lines

+        memblock_dbg("memblock_free: [%#016llx-%#016llx] %pS\n", +            __pa(start), __pa(end), (void *)_RET_IP_); +#endif

IMHO, the "memblock_free" part is misleading. Something was allocated early via memblock, then we transitioned to the buddy, now we're freeing that early allocation via the buddy.
Yes, we're freeing the early allocation via buddy, but for proper

Quoted 2 lines

memblock accounting we need this debug print.

What do you mean with "accounting" ? These are debug statements.

Signature · 3 lines
Thanks,

David / dhildenb
#4 lore raw
Quoted 45 lines · David Hildenbrand
Quoted 44 lines · Faiyaz Mohammed
Quoted 41 lines · David Hildenbrand
Quoted 28 lines · Faiyaz Mohammed

For INITRD and initmem memory is reserved through "memblock_reserve" during boot up but it is free via "free_reserved_area" instead of "memblock_free".
For example:
[    0.294848] Freeing initrd memory: 12K.
[    0.696688] Freeing unused kernel memory: 4096K.

To get the start and end address of the above freed memory and to account
proper memblock added memblock_dbg log in "free_reserved_area". After adding log:
[    0.294837] memblock_free: [0x00000083600000-0x00000083603000] free_initrd_mem+0x20/0x28
[    0.294848] Freeing initrd memory: 12K.
[    0.695246] memblock_free: [0x00000081600000-0x00000081a00000] free_initmem+0x70/0xc8
[    0.696688] Freeing unused kernel memory: 4096K.

---
   mm/page_alloc.c | 5 +++++

   1 file changed, 5 insertions(+)
mm/page_alloc.c +0 -0
index b37435c..f85c3b2 100644
@@ -8129,6 +8129,11 @@ unsigned long free_reserved_area(void *start,
Quoted 7 lines

void *end, int poison, const char
           pr_info("Freeing %s memory: %ldK\n",
               s, pages << (PAGE_SHIFT - 10));
   +#ifdef CONFIG_HAVE_MEMBLOCK
+        memblock_dbg("memblock_free: [%#016llx-%#016llx] %pS\n", +            __pa(start), __pa(end), (void *)_RET_IP_); +#endif

IMHO, the "memblock_free" part is misleading. Something was allocated early via memblock, then we transitioned to the buddy, now we're freeing that early allocation via the buddy.
Yes, we're freeing the early allocation via buddy, but for proper

Quoted 6 lines
Quoted 2 lines

memblock accounting we need this debug print.

What do you mean with "accounting" ? These are debug statements.

Yes, these are debug statements, which help to know the a-b address belongs to x callsite. This info is required when memblock=debug is passed through command line and CONFIG_HAVE_MEMBLOCK is enabled.

Thanks,
Mohammed Faiyaz

#5 lore raw
Quoted 51 lines · Faiyaz Mohammed
Quoted 48 lines · David Hildenbrand
Quoted 46 lines · Faiyaz Mohammed
Quoted 33 lines · David Hildenbrand
Quoted 32 lines · Faiyaz Mohammed

For INITRD and initmem memory is reserved through "memblock_reserve" during boot up but it is free via "free_reserved_area" instead of "memblock_free".
For example:
[    0.294848] Freeing initrd memory: 12K.
[    0.696688] Freeing unused kernel memory: 4096K.

To get the start and end address of the above freed memory and to account
proper memblock added memblock_dbg log in "free_reserved_area". After adding log:
[    0.294837] memblock_free: [0x00000083600000-0x00000083603000] free_initrd_mem+0x20/0x28
[    0.294848] Freeing initrd memory: 12K.
[    0.695246] memblock_free: [0x00000081600000-0x00000081a00000] free_initmem+0x70/0xc8
[    0.696688] Freeing unused kernel memory: 4096K.

---
    mm/page_alloc.c | 5 +++++
    1 file changed, 5 insertions(+)
mm/page_alloc.c +0 -0
index b37435c..f85c3b2 100644
@@ -8129,6 +8129,11 @@ unsigned long free_reserved_area(void *start,

void *end, int poison, const char
           pr_info("Freeing %s memory: %ldK\n",
               s, pages << (PAGE_SHIFT - 10));
   +#ifdef CONFIG_HAVE_MEMBLOCK

Quoted 8 lines
Quoted 3 lines

+        memblock_dbg("memblock_free: [%#016llx-%#016llx] %pS\n", +            __pa(start), __pa(end), (void *)_RET_IP_); +#endif

IMHO, the "memblock_free" part is misleading. Something was allocated early via memblock, then we transitioned to the buddy, now we're freeing that early allocation via the buddy.
Yes, we're freeing the early allocation via buddy, but for proper

memblock accounting we need this debug print.

Quoted 6 lines
Quoted 3 lines

What do you mean with "accounting" ? These are debug statements.

Yes, these are debug statements, which help to know the a-b address belongs to x callsite. This info is required when memblock=debug is passed through command line and CONFIG_HAVE_MEMBLOCK is enabled.

The issue I'm having is talking in the name of memblock "memblock_dbg, memblock_free", when memblock might no longer be around. We have other places where we free early memblock allocations back to the buddy.

Signature · 3 lines
Thanks,

David / dhildenb
#6 lore raw

Hi,

Sorry for delayed response.

Quoted 56 lines · David Hildenbrand
Quoted 55 lines · Faiyaz Mohammed
Quoted 52 lines · David Hildenbrand
Quoted 45 lines · Faiyaz Mohammed
Quoted 34 lines · David Hildenbrand
Quoted 33 lines · Faiyaz Mohammed

For INITRD and initmem memory is reserved through "memblock_reserve" during boot up but it is free via "free_reserved_area" instead of "memblock_free".
For example:
[    0.294848] Freeing initrd memory: 12K.
[    0.696688] Freeing unused kernel memory: 4096K.

To get the start and end address of the above freed memory and to account
proper memblock added memblock_dbg log in "free_reserved_area". After adding log:
[    0.294837] memblock_free: [0x00000083600000-0x00000083603000] free_initrd_mem+0x20/0x28
[    0.294848] Freeing initrd memory: 12K.
[    0.695246] memblock_free: [0x00000081600000-0x00000081a00000] free_initmem+0x70/0xc8
[    0.696688] Freeing unused kernel memory: 4096K.

---
    mm/page_alloc.c | 5 +++++

    1 file changed, 5 insertions(+)
mm/page_alloc.c +0 -0
index b37435c..f85c3b2 100644
@@ -8129,6 +8129,11 @@ unsigned long free_reserved_area(void *start,

void *end, int poison, const char
            pr_info("Freeing %s memory: %ldK\n",
                s, pages << (PAGE_SHIFT - 10));
    +#ifdef CONFIG_HAVE_MEMBLOCK
+        memblock_dbg("memblock_free: [%#016llx-%#016llx] %pS\n",

Quoted 8 lines
Quoted 2 lines

+            __pa(start), __pa(end), (void *)_RET_IP_); +#endif

IMHO, the "memblock_free" part is misleading. Something was allocated early via memblock, then we transitioned to the buddy, now we're freeing
that early allocation via the buddy.
Yes, we're freeing the early allocation via buddy, but for proper

Quoted 2 lines

memblock accounting we need this debug print.

What do you mean with "accounting" ? These are debug statements.

Quoted 7 lines
Quoted 3 lines

Yes, these are debug statements, which help to know the a-b address belongs to x callsite. This info is required when memblock=debug is passed through command line and CONFIG_HAVE_MEMBLOCK is enabled.

The issue I'm having is talking in the name of memblock "memblock_dbg, memblock_free", when memblock might no longer be around. We have other places where we free early memblock allocations back to the buddy.

I didn't find place where we free early memblock allocation back to the buddy.

Why "memblock_dbg" print with "memblock_free" string?.
- After buddy took over, buddy will free memblock reserved memory through free_reserved_area and it will print the freed memory size, but the freed memory through buddy still be part of memblock.reserved.regions.
- To know the address ranges, added the "memblock_dbg" print along with "membloc_free" string.
- If it is misleading or confusing, we can remove the "memblock_free" string from the "memblock_dgb" print and we can just print the address range when "memlock=debug" pass through command line.

Thanks and regards,
Mohammed Faiyaz

#7 lore raw
Quoted 65 lines · Faiyaz Mohammed

Hi,

Sorry for delayed response.

Quoted 60 lines · David Hildenbrand
Quoted 58 lines · Faiyaz Mohammed
Quoted 46 lines · David Hildenbrand
Quoted 45 lines · Faiyaz Mohammed
Quoted 42 lines · David Hildenbrand
Quoted 28 lines · Faiyaz Mohammed

For INITRD and initmem memory is reserved through "memblock_reserve" during boot up but it is free via "free_reserved_area" instead of "memblock_free".
For example:
[    0.294848] Freeing initrd memory: 12K.
[    0.696688] Freeing unused kernel memory: 4096K.

To get the start and end address of the above freed memory and to account
proper memblock added memblock_dbg log in "free_reserved_area". After adding log:
[    0.294837] memblock_free: [0x00000083600000-0x00000083603000] free_initrd_mem+0x20/0x28
[    0.294848] Freeing initrd memory: 12K.
[    0.695246] memblock_free: [0x00000081600000-0x00000081a00000] free_initmem+0x70/0xc8
[    0.696688] Freeing unused kernel memory: 4096K.

---
     mm/page_alloc.c | 5 +++++
     1 file changed, 5 insertions(+)
mm/page_alloc.c +0 -0
index b37435c..f85c3b2 100644
@@ -8129,6 +8129,11 @@ unsigned long free_reserved_area(void *start,
Quoted 7 lines

void *end, int poison, const char
            pr_info("Freeing %s memory: %ldK\n",
                s, pages << (PAGE_SHIFT - 10)); +#ifdef CONFIG_HAVE_MEMBLOCK
+        memblock_dbg("memblock_free: [%#016llx-%#016llx] %pS\n", +            __pa(start), __pa(end), (void *)_RET_IP_); +#endif

IMHO, the "memblock_free" part is misleading. Something was allocated early via memblock, then we transitioned to the buddy, now we're freeing
that early allocation via the buddy.
Yes, we're freeing the early allocation via buddy, but for proper

Quoted 6 lines
Quoted 2 lines

memblock accounting we need this debug print.

What do you mean with "accounting" ? These are debug statements.

Yes, these are debug statements, which help to know the a-b address belongs to x callsite. This info is required when memblock=debug is passed through command line and CONFIG_HAVE_MEMBLOCK is enabled.

Quoted 5 lines
Quoted 3 lines

The issue I'm having is talking in the name of memblock "memblock_dbg, memblock_free", when memblock might no longer be around. We have other places where we free early memblock allocations back to the buddy.

I didn't find place where we free early memblock allocation back to the buddy.

One example I know is

section_deactivate()->free_map_bootmem()->vmemmap_free()-> ... free_pagetable()->free_reserved_page().

when we free the vmemmap allocated via memblock back to the buddy.

Quoted 10 lines

Why "memblock_dbg" print with "memblock_free" string?.
- After buddy took over, buddy will free memblock reserved memory through free_reserved_area and it will print the freed memory size, but the freed memory through buddy still be part of memblock.reserved.regions.
- To know the address ranges, added the "memblock_dbg" print along with "membloc_free" string.
- If it is misleading or confusing, we can remove the "memblock_free" string from the "memblock_dgb" print and we can just print the address range when "memlock=debug" pass through command line.

That would be better, but do we really have to depend on "memlock=debug"? Can't we do pr_debug() ?

Signature · 3 lines
Thanks,

David / dhildenb
#8 lore raw
Quoted 94 lines · David Hildenbrand
Quoted 68 lines · Faiyaz Mohammed

Hi,

Sorry for delayed response.

Quoted 63 lines · David Hildenbrand
Quoted 61 lines · Faiyaz Mohammed
Quoted 49 lines · David Hildenbrand
Quoted 48 lines · Faiyaz Mohammed
Quoted 45 lines · David Hildenbrand
Quoted 30 lines · Faiyaz Mohammed

For INITRD and initmem memory is reserved through "memblock_reserve"
during boot up but it is free via "free_reserved_area" instead of "memblock_free".
For example:
[    0.294848] Freeing initrd memory: 12K.
[    0.696688] Freeing unused kernel memory: 4096K.

To get the start and end address of the above freed memory and to account
proper memblock added memblock_dbg log in "free_reserved_area". After adding log:
[    0.294837] memblock_free: [0x00000083600000-0x00000083603000] free_initrd_mem+0x20/0x28
[    0.294848] Freeing initrd memory: 12K.
[    0.695246] memblock_free: [0x00000081600000-0x00000081a00000] free_initmem+0x70/0xc8
[    0.696688] Freeing unused kernel memory: 4096K.

---
     mm/page_alloc.c | 5 +++++

     1 file changed, 5 insertions(+)
mm/page_alloc.c +0 -0
index b37435c..f85c3b2 100644
@@ -8129,6 +8129,11 @@ unsigned long free_reserved_area(void
 *start,
Quoted 7 lines

void *end, int poison, const char
             pr_info("Freeing %s memory: %ldK\n",
                 s, pages << (PAGE_SHIFT - 10)); +#ifdef CONFIG_HAVE_MEMBLOCK
+        memblock_dbg("memblock_free: [%#016llx-%#016llx] %pS\n", +            __pa(start), __pa(end), (void *)_RET_IP_); +#endif

IMHO, the "memblock_free" part is misleading. Something was allocated
early via memblock, then we transitioned to the buddy, now we're freeing
that early allocation via the buddy.
Yes, we're freeing the early allocation via buddy, but for proper

Quoted 6 lines
Quoted 2 lines

memblock accounting we need this debug print.

What do you mean with "accounting" ? These are debug statements.

Yes, these are debug statements, which help to know the a-b address belongs to x callsite. This info is required when memblock=debug is passed through command line and CONFIG_HAVE_MEMBLOCK is enabled.

Quoted 5 lines
Quoted 3 lines

The issue I'm having is talking in the name of memblock "memblock_dbg, memblock_free", when memblock might no longer be around. We have other places where we free early memblock allocations back to the buddy.

I didn't find place where we free early memblock allocation back to the buddy.

One example I know is

section_deactivate()->free_map_bootmem()->vmemmap_free()-> ... free_pagetable()->free_reserved_page().

when we free the vmemmap allocated via memblock back to the buddy.

Quoted 11 lines

Why "memblock_dbg" print with "memblock_free" string?.
- After buddy took over, buddy will free memblock reserved memory through free_reserved_area and it will print the freed memory size, but the freed memory through buddy still be part of memblock.reserved.regions.
- To know the address ranges, added the "memblock_dbg" print along with "membloc_free" string.
- If it is misleading or confusing, we can remove the "memblock_free" string from the "memblock_dgb" print and we can just print the address range when "memlock=debug" pass through command line.

Quoted 2 lines

That would be better, but do we really have to depend on "memlock=debug"?

Yes, because we need that print when memblock=debug is pass through command line, like other memblock debug messages.

Thanks and regards,
Mohammed Faiyaz

#9 lore raw
In reply to David Hildenbrand
Quoted 94 lines · David Hildenbrand
Quoted 68 lines · Faiyaz Mohammed

Hi,

Sorry for delayed response.

Quoted 63 lines · David Hildenbrand
Quoted 61 lines · Faiyaz Mohammed
Quoted 49 lines · David Hildenbrand
Quoted 48 lines · Faiyaz Mohammed
Quoted 45 lines · David Hildenbrand
Quoted 30 lines · Faiyaz Mohammed

For INITRD and initmem memory is reserved through "memblock_reserve"
during boot up but it is free via "free_reserved_area" instead of "memblock_free".
For example:
[    0.294848] Freeing initrd memory: 12K.
[    0.696688] Freeing unused kernel memory: 4096K.

To get the start and end address of the above freed memory and to account
proper memblock added memblock_dbg log in "free_reserved_area". After adding log:
[    0.294837] memblock_free: [0x00000083600000-0x00000083603000] free_initrd_mem+0x20/0x28
[    0.294848] Freeing initrd memory: 12K.
[    0.695246] memblock_free: [0x00000081600000-0x00000081a00000] free_initmem+0x70/0xc8
[    0.696688] Freeing unused kernel memory: 4096K.

---
     mm/page_alloc.c | 5 +++++

     1 file changed, 5 insertions(+)
mm/page_alloc.c +0 -0
index b37435c..f85c3b2 100644
@@ -8129,6 +8129,11 @@ unsigned long free_reserved_area(void
 *start,
Quoted 7 lines

void *end, int poison, const char
             pr_info("Freeing %s memory: %ldK\n",
                 s, pages << (PAGE_SHIFT - 10)); +#ifdef CONFIG_HAVE_MEMBLOCK
+        memblock_dbg("memblock_free: [%#016llx-%#016llx] %pS\n", +            __pa(start), __pa(end), (void *)_RET_IP_); +#endif

IMHO, the "memblock_free" part is misleading. Something was allocated
early via memblock, then we transitioned to the buddy, now we're freeing
that early allocation via the buddy.
Yes, we're freeing the early allocation via buddy, but for proper

Quoted 6 lines
Quoted 2 lines

memblock accounting we need this debug print.

What do you mean with "accounting" ? These are debug statements.

Yes, these are debug statements, which help to know the a-b address belongs to x callsite. This info is required when memblock=debug is passed through command line and CONFIG_HAVE_MEMBLOCK is enabled.

Quoted 5 lines
Quoted 3 lines

The issue I'm having is talking in the name of memblock "memblock_dbg, memblock_free", when memblock might no longer be around. We have other places where we free early memblock allocations back to the buddy.

I didn't find place where we free early memblock allocation back to the buddy.

One example I know is

section_deactivate()->free_map_bootmem()->vmemmap_free()-> ... free_pagetable()->free_reserved_page().

when we free the vmemmap allocated via memblock back to the buddy.

Quoted 11 lines

Why "memblock_dbg" print with "memblock_free" string?.
- After buddy took over, buddy will free memblock reserved memory through free_reserved_area and it will print the freed memory size, but the freed memory through buddy still be part of memblock.reserved.regions.
- To know the address ranges, added the "memblock_dbg" print along with "membloc_free" string.
- If it is misleading or confusing, we can remove the "memblock_free" string from the "memblock_dgb" print and we can just print the address range when "memlock=debug" pass through command line.

Quoted 3 lines

That would be better, but do we really have to depend on "memlock=debug"? Can't we do pr_debug() ?

Yes, I think we can do pr_debug. I will update the patch and push again.

Thanks and regards,
Mohammed Faiyaz