Re: [PATCH v3 0/5] kho: fix bootmem sizing

From: Mike Rapoport

Date: Tue Nov 17 2026 - 08:01:41 EST


From: Mike Rapoport (Microsoft) <rppt@xxxxxxxxxx>

On Thu, 12 Nov 2026 12:38:52 +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.
>
> [...]

Applied to liveupdate-7.5 branch of liveupdate/linux.git tree, thanks!

[1/5] kho: reject zero bootmem scale
commit: caeb2173b83441d991171dbbaa59455dae5399ea
[2/5] kho: walk bootmem areas in address order
commit: f117bbae706f44c7dd1e811d89057d1dc7886554
[3/5] kho: skip zero-sized lowmem and global bootmem areas
commit: 1010dc3150fc835695df7b21cb9d56016477fab8
[4/5] kho: fix bootmem sizing
commit: ee4505fe8c4490827244668dab3659c100f4e7cd
[5/5] kho: docs: update description of bootmem regions
commit: 5b27be339c42a7540eeca5c179e7e0bbdb7a4cdb

tree: https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux
branch: liveupdate-7.5

--
Sincerely yours,
Mike.