Skip to contentSkip to conversation

mm/mm_init.c: Extend init unavailable range doc info

PATCH In review Serge Semin 2 participants 2 messages Dec 2, 2023 – Dec 3, 2023

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 mm/mm_init.c: Extend init unavailable range doc info

Besides of the already described reasons the pages backended memory holes might present due to having non-memory regions covered by the contiguous flatmem mapping. Add such note to the init_unavailable_range() method kdoc in order to point out to one more reason of having the function executed for such regions.

---

Changelog v2:
- The holes in the memory are actually justified by having the flatmem mapping model. Change the patch and the log accordingly. (@Mike)

---
 mm/mm_init.c | 1 +
 1 file changed, 1 insertion(+)
mm/mm_init.c +1 -0
index 077bfe393b5e..824bf53e8253 100644
@@ -796,6 +796,7 @@ overlap_memmap_init(unsigned long zone, unsigned long *pfn)
  * - physical memory bank size is not necessarily the exact multiple of the
  *   arbitrary section size
  * - early reserved memory may not be listed in memblock.memory
+ * - non-memory regions covered by the contigious flatmem mapping
  * - memory layouts defined with memmap= kernel parameter may not align
  *   nicely with memmap sections
  *
Signature · 1 line
2.42.1
maintainer Reviewed-by on v2 1/1
#1 lore raw
Quoted 7 lines · Serge Semin

Besides of the already described reasons the pages backended memory holes might present due to having non-memory regions covered by the contiguous flatmem mapping. Add such note to the init_unavailable_range() method kdoc in order to point out to one more reason of having the function executed for such regions.

Quoted 26 lines

---

Changelog v2:
- The holes in the memory are actually justified by having the flatmem mapping model. Change the patch and the log accordingly. (@Mike)

---
 mm/mm_init.c | 1 +
 1 file changed, 1 insertion(+)
mm/mm_init.c +1 -0
index 077bfe393b5e..824bf53e8253 100644
@@ -796,6 +796,7 @@ overlap_memmap_init(unsigned long zone, unsigned long *pfn)
  * - physical memory bank size is not necessarily the exact multiple of the
  *   arbitrary section size
  * - early reserved memory may not be listed in memblock.memory
+ * - non-memory regions covered by the contigious flatmem mapping
  * - memory layouts defined with memmap= kernel parameter may not align
  *   nicely with memmap sections
  *
Signature · 1 line
2.42.1
Signature · 2 lines
Sincerely yours,
Mike.