Re: [PATCH v3 0/5] kho: fix bootmem sizing
From: Mike Rapoport
Date: Sun Nov 15 2026 - 14:22:06 EST
On Thu, Nov 12, 2026 at 12:38:52PM +0200, Mike Rapoport (Microsoft) wrote:
> There were several reports about issues with KHO bootmem sizing.
>
> The bootmem areas are sized from overlapping views of the memory reserved
> in memblock, so on NUMA systems memory allocated on a node is accounted
> twice and with CONFIG_NUMA=n the lowmem and the global areas are accounted
> once again in the area of node 0. Besides, the lowmem and the global areas
> are reserved even when they are empty.
>
> ---
> Mike Rapoport (Microsoft) (5):
> kho: reject zero bootmem scale
> kho: walk bootmem areas in address order
> kho: skip zero-sized lowmem and global bootmem areas
> kho: fix bootmem sizing
> kho: docs: update description of bootmem regions
>
> Documentation/core-api/kho/index.rst | 31 +++--
> kernel/liveupdate/kexec_handover.c | 225 +++++++++++++++++++++--------------
> 2 files changed, 158 insertions(+), 98 deletions(-)
> ---
> base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
> change-id: 20261103-kho-bootmem-sizing-5d6aed47a243
I took this version to the liveupdate tree.
--
Sincerely yours,
Mike.