diff options
| author | Serge Semin <fancer.lancer@gmail.com> | 2023-11-22 21:24:03 +0300 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2023-12-11 03:51:51 +0300 |
| commit | ecf5dd1ffe84ede52d8a6c9fb72d8aad04ff8160 (patch) | |
| tree | 788f2eedaf09b6b59f74bf1e267ab6045fa917ce /Kbuild | |
| parent | f7dd74ac239aad5ef7575ea03c45fd7956e00285 (diff) | |
| download | linux-ecf5dd1ffe84ede52d8a6c9fb72d8aad04ff8160.tar.xz | |
mm/mm_init.c: extend init unavailable range doc info
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.
[fancer.lancer@gmail.com: update per Mike]
Link: https://lkml.kernel.org/r/20231202111855.18392-1-fancer.lancer@gmail.com
Link: https://lkml.kernel.org/r/20231122182419.30633-6-fancer.lancer@gmail.com
Signed-off-by: Serge Semin <fancer.lancer@gmail.com>
Reviewed-by: Mike Rapoport (IBM) <rppt@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions