The patch titled
Subject: mm/mm_init.c: extend init unavailable range doc info
has been added to the -mm mm-unstable branch. Its filename is
mm-mm_initc-extend-init-unavailable-range-doc-info.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-mm_initc-extend-init-unavailable-range-doc-info.patch
This patch will later appear in the mm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
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 via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days
------------------------------------------------------
From: Serge Semin <fancer.lancer@xxxxxxxxx>
Subject: mm/mm_init.c: extend init unavailable range doc info
Date: Wed, 22 Nov 2023 21:24:03 +0300
Besides of the already described reasons the pages backended memory holes
might be persistent due to having memory mapped IO spaces behind those
ranges in the framework of flatmem kernel config. 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.
Link: https://lkml.kernel.org/r/20231122182419.30633-6-fancer.lancer@xxxxxxxxx
Signed-off-by: Serge Semin <fancer.lancer@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/mm_init.c | 1 +
1 file changed, 1 insertion(+)
--- a/mm/mm_init.c~mm-mm_initc-extend-init-unavailable-range-doc-info
+++ a/mm/mm_init.c
@@ -796,6 +796,7 @@ overlap_memmap_init(unsigned long zone,
* - 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
+ * - memory mapped IO space
* - memory layouts defined with memmap= kernel parameter may not align
* nicely with memmap sections
*
_
Patches currently in -mm which might be from fancer.lancer@xxxxxxxxx are
mm-mm_initc-extend-init-unavailable-range-doc-info.patch
mm-mm_initc-append-newline-to-the-unavailable-ranges-log-message.patch
