From: Mukesh Pilaniya <mpilaniy@redhat.com>
To: "Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>
Cc: Alexander Graf <graf@amazon.com>,
Andrew Morton <akpm@linux-foundation.org>,
Chen Pei <cp0613@linux.alibaba.com>,
George Guo <guodongtai@kylinos.cn>,
Kexin Liu <liukexin@kylinos.cn>,
Sourabh Jain <sourabhjain@linux.ibm.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2 2/3] kho: skip zero-sized lowmem and global bootmem areas
Date: Thu, 12 Nov 2026 12:18:28 +0530 [thread overview]
Message-ID: <9b290d87-1413-4981-a296-9d37552e8913@redhat.com> (raw)
In-Reply-To: <20261104-kho-bootmem-sizing-v2-2-b0d1a834780f@kernel.org>
Hi Mike,
On 04/11/26 10:20 pm, Mike Rapoport (Microsoft) wrote:
> The lowmem and the global bootmem areas can have zero size, for example
> when none or all of the memory is below ARCH_LOW_ADDRESS_LIMIT, or when
> either of those areas is explicitly set to zero with kho_bootmem=.
>
> For a zero-sized allocation memblock returns an address without reserving
> anything, and that empty area is recorded in kho_bootmem. If there is no
> memory below ARCH_LOW_ADDRESS_LIMIT, allocation of the empty lowmem area
> fails and KHO gets disabled.
>
> Extract a helper that checks for zero size and allocates memory from
> memblock, and use it to skip empty areas the same way as empty per-node
> areas are skipped.
>
> Fixes: 3dc92c311498 ("kexec: add Kexec HandOver (KHO) generation helpers")
> Reported-by: Chen Pei <cp0613@linux.alibaba.com>
> Closes: https://lore.kernel.org/all/20261026131851.9942-1-cp0613@linux.alibaba.com
> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> kernel/liveupdate/kexec_handover.c | 66 +++++++++++++++++---------------------
> 1 file changed, 30 insertions(+), 36 deletions(-)
>
> diff --git a/kernel/liveupdate/kexec_handover.c b/kernel/liveupdate/kexec_handover.c
> index 2ac5d94f33fd4..5b1797d1289c8 100644
> --- a/kernel/liveupdate/kexec_handover.c
> +++ b/kernel/liveupdate/kexec_handover.c
> @@ -829,6 +829,26 @@ static int __init kho_bootmem_cmp(const void *_a, const void *_b)
> return cmp_int(a->addr, b->addr);
> }
>
> +static int __init kho_reserve_bootmem_area(phys_addr_t size, phys_addr_t end,
> + int nid)
> +{
> + phys_addr_t addr;
> +
> + if (!size)
> + return 0;
> +
> + addr = memblock_alloc_range_nid(size, BOOTMEM_ALIGNMENT_BYTES, 0, end,
> + nid, true);
The low memory and global areas are reserved with NUMA_NO_NODE, but
kho_reserve_bootmem_area passes exact_nid = true for them as well.
memblock only uses the flag for a valid node So Pass
numa_valid_node(nid) instant of true.
Reviewed-by: Mukesh Pilaniya <mpilaniy@redhat.com>
> + if (!addr)
> + return -ENOMEM;
> +
> + kho_bootmem[kho_bootmem_cnt].addr = addr;
> + kho_bootmem[kho_bootmem_cnt].size = size;
> + kho_bootmem_cnt++;
> +
> + return 0;
> +}
> +
> /**
> * kho_reserve_bootmem - Reserve a contiguous chunk of memory for kexec
> *
> @@ -840,8 +860,8 @@ static int __init kho_bootmem_cmp(const void *_a, const void *_b)
> */
> static void __init kho_reserve_bootmem(void)
> {
> - int nid, i = 0, max_nr_bootmem;
> - phys_addr_t addr, size;
> + int nid, max_nr_bootmem;
> + phys_addr_t size;
>
> if (!kho_enable)
> return;
> @@ -861,66 +881,40 @@ static void __init kho_reserve_bootmem(void)
> * reserve bootmem area in low memory for lowmem allocations in the
> * next kernel
> */
> - size = bootmem_size_lowmem;
> - addr = memblock_phys_alloc_range(size, BOOTMEM_ALIGNMENT_BYTES, 0,
> - ARCH_LOW_ADDRESS_LIMIT);
> - if (!addr) {
> + if (kho_reserve_bootmem_area(bootmem_size_lowmem, ARCH_LOW_ADDRESS_LIMIT,
> + NUMA_NO_NODE)) {
> pr_err("Failed to reserve lowmem bootmem\n");
> goto err_free_bootmem_desc;
> }
>
> - kho_bootmem[i].addr = addr;
> - kho_bootmem[i].size = size;
> - i++;
> -
> /* reserve large contiguous area for allocations without nid */
> - size = bootmem_size_global;
> - addr = memblock_phys_alloc(size, BOOTMEM_ALIGNMENT_BYTES);
> - if (!addr) {
> + if (kho_reserve_bootmem_area(bootmem_size_global,
> + MEMBLOCK_ALLOC_ACCESSIBLE, NUMA_NO_NODE)) {
> pr_err("Failed to reserve global bootmem\n");
> goto err_free_bootmem_areas;
> }
>
> - kho_bootmem[i].addr = addr;
> - kho_bootmem[i].size = size;
> - i++;
> -
> /*
> * Loop over nodes that have both memory and are online. Skip
> * memoryless nodes, as we can not allocate bootmem areas there.
> */
> for_each_node_state(nid, N_MEMORY) {
> - size = bootmem_size_node(nid);
> - if (!size)
> - continue;
> -
> - addr = memblock_alloc_range_nid(size, BOOTMEM_ALIGNMENT_BYTES,
> - 0, MEMBLOCK_ALLOC_ACCESSIBLE,
> - nid, true);
> - if (!addr) {
> + if (kho_reserve_bootmem_area(bootmem_size_node(nid),
> + MEMBLOCK_ALLOC_ACCESSIBLE, nid)) {
> pr_err("Failed to reserve nid %d bootmem\n", nid);
> goto err_free_bootmem_areas;
> }
> -
> - kho_bootmem[i].addr = addr;
> - kho_bootmem[i].size = size;
> - i++;
> }
>
> - /*
> - * Nodes that needed no bootmem were skipped, so fewer areas than
> - * initially estimated may have been reserved.
> - */
> - kho_bootmem_cnt = i;
> -
> sort(kho_bootmem, kho_bootmem_cnt, sizeof(*kho_bootmem),
> kho_bootmem_cmp, NULL);
>
> return;
>
> err_free_bootmem_areas:
> - for (i--; i >= 0; i--)
> + for (int i = kho_bootmem_cnt - 1; i >= 0; i--)
Check the First patch comment on this.
> memblock_phys_free(kho_bootmem[i].addr, kho_bootmem[i].size);
> + kho_bootmem_cnt = 0;
> err_free_bootmem_desc:
> memblock_free(kho_bootmem, max_nr_bootmem * sizeof(*kho_bootmem));
> err_disable_kho:
>
--
Regards,
Mukesh Pilaniya
next prev parent reply other threads:[~2026-11-12 6:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 16:50 [PATCH v2 0/3] kho: fix bootmem sizing Mike Rapoport (Microsoft)
2026-11-04 16:50 ` [PATCH v2 1/3] kho: walk bootmem areas in address order Mike Rapoport (Microsoft)
2026-11-04 18:57 ` Pasha Tatashin
2026-11-04 22:14 ` Jose A. Perez de Azpillaga
2026-11-10 16:52 ` Pratyush Yadav
2026-11-12 6:32 ` Mukesh Pilaniya
2026-11-04 16:50 ` [PATCH v2 2/3] kho: skip zero-sized lowmem and global bootmem areas Mike Rapoport (Microsoft)
2026-11-04 18:57 ` Pasha Tatashin
2026-11-04 22:17 ` Jose A. Perez de Azpillaga
2026-11-10 16:55 ` Pratyush Yadav
2026-11-12 6:48 ` Mukesh Pilaniya [this message]
2026-11-04 16:50 ` [PATCH v2 3/3] kho: fix bootmem sizing Mike Rapoport (Microsoft)
2026-11-04 18:57 ` Pasha Tatashin
2026-11-05 9:26 ` Mike Rapoport
2026-11-04 22:17 ` Jose A. Perez de Azpillaga
2026-11-10 16:54 ` Pratyush Yadav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9b290d87-1413-4981-a296-9d37552e8913@redhat.com \
--to=mpilaniy@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cp0613@linux.alibaba.com \
--cc=graf@amazon.com \
--cc=guodongtai@kylinos.cn \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liukexin@kylinos.cn \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=sourabhjain@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®