[PATCH v2 1/3] kho: walk bootmem areas in address order
Pasha Tatashin
pasha.tatashin at soleen.com
Wed Nov 4 10:57:03 PST 2026
On Wed, 04 Nov 2026 18:50:09 +0200, Mike Rapoport (Microsoft) <rppt at kernel.org> wrote:
> kexec_add_buffer() users may depend on the order in which memory holes are
> searched. For instance, arm64 places the kernel bottom-up and then
> requires the DTB to be above the kernel.
>
> kho_walk_bootmem() walks the bootmem areas in the order they were
> reserved, so if the kernel lands in a small area at the top of the memory
> there is no room left for the DTB and kexec fails. For example, on an
> arm64 VM with 2G of RAM and kho_bootmem=8M,64M,64M, the lowmem area is
> reserved first at the top of the memory, the kernel image takes most of
> it and kexec fails with
>
> [...]
Reviewed-by: Pasha Tatashin <pasha.tatashin at soleen.com>
--
Pasha
More information about the kexec
mailing list