linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Samiullah Khawaja <skhawaja@google.com>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Alexander Graf <graf@amazon.com>,
	 Mike Rapoport <rppt@kernel.org>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	kexec@lists.infradead.org,  linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	 David Matlack <dmatlack@google.com>,
	Jason Miu <jasonmiu@google.com>
Subject: Re: [PATCH] kho: print which scratch buffer failed to be reserved
Date: Thu, 22 Jan 2026 11:48:44 -0800	[thread overview]
Message-ID: <CAAywjhTfAU-NH7+Wevp_UxquuJdUNuKvnv_Hzh6GDcFFxC1Bpg@mail.gmail.com> (raw)
In-Reply-To: <20260116165416.1262531-1-pratyush@kernel.org>

On Fri, Jan 16, 2026 at 8:54 AM Pratyush Yadav <pratyush@kernel.org> wrote:
>
> From: "Pratyush Yadav (Google)" <pratyush@kernel.org>
>
> When scratch area fails to reserve, KHO prints a message indicating
> that. But it doesn't say which scratch failed to allocate. This can be
> useful information for debugging. Even more so when the failure is hard
> to reproduce.
>
> Along with the current message, also print which exact scratch area
> failed to be reserved.
>
> Signed-off-by: Pratyush Yadav (Google) <pratyush@kernel.org>
> ---
>  kernel/liveupdate/kexec_handover.c | 16 ++++++++++++----
>  1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/liveupdate/kexec_handover.c b/kernel/liveupdate/kexec_handover.c
> index 49bf2cecab12..636bd96780ae 100644
> --- a/kernel/liveupdate/kexec_handover.c
> +++ b/kernel/liveupdate/kexec_handover.c
> @@ -651,8 +651,10 @@ static void __init kho_reserve_scratch(void)
>         kho_scratch_cnt = num_online_nodes() + 2;
>         size = kho_scratch_cnt * sizeof(*kho_scratch);
>         kho_scratch = memblock_alloc(size, PAGE_SIZE);
> -       if (!kho_scratch)
> +       if (!kho_scratch) {
> +               pr_err("Failed to reserve scratch array\n");
>                 goto err_disable_kho;
> +       }
>
>         /*
>          * reserve scratch area in low memory for lowmem allocations in the
> @@ -661,8 +663,10 @@ static void __init kho_reserve_scratch(void)
>         size = scratch_size_lowmem;
>         addr = memblock_phys_alloc_range(size, CMA_MIN_ALIGNMENT_BYTES, 0,
>                                          ARCH_LOW_ADDRESS_LIMIT);
> -       if (!addr)
> +       if (!addr) {
> +               pr_err("Failed to reserve lowmem scratch buffer\n");
>                 goto err_free_scratch_desc;
> +       }
>
>         kho_scratch[i].addr = addr;
>         kho_scratch[i].size = size;
> @@ -671,8 +675,10 @@ static void __init kho_reserve_scratch(void)
>         /* reserve large contiguous area for allocations without nid */
>         size = scratch_size_global;
>         addr = memblock_phys_alloc(size, CMA_MIN_ALIGNMENT_BYTES);
> -       if (!addr)
> +       if (!addr) {
> +               pr_err("Failed to reserve global scratch buffer\n");
>                 goto err_free_scratch_areas;
> +       }
>
>         kho_scratch[i].addr = addr;
>         kho_scratch[i].size = size;
> @@ -683,8 +689,10 @@ static void __init kho_reserve_scratch(void)
>                 addr = memblock_alloc_range_nid(size, CMA_MIN_ALIGNMENT_BYTES,
>                                                 0, MEMBLOCK_ALLOC_ACCESSIBLE,
>                                                 nid, true);
> -               if (!addr)
> +               if (!addr) {
> +                       pr_err("Failed to reserve nid %d scratch buffer\n", nid);
>                         goto err_free_scratch_areas;
> +               }
>
>                 kho_scratch[i].addr = addr;
>                 kho_scratch[i].size = size;
>
> base-commit: c37fac0551448c68e36f14782acaf662c7a1775e
> --
> 2.52.0.457.g6b5491de43-goog
>

Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Samiullah Khawaja <skhawaja@google.com>

Tested on my test machine while investigating the scratch space
allocation failure.


      parent reply	other threads:[~2026-01-22 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 16:54 Pratyush Yadav
2026-01-18 12:17 ` Mike Rapoport
2026-01-22 19:35 ` Pasha Tatashin
2026-01-22 19:48 ` Samiullah Khawaja [this message]

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=CAAywjhTfAU-NH7+Wevp_UxquuJdUNuKvnv_Hzh6GDcFFxC1Bpg@mail.gmail.com \
    --to=skhawaja@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmatlack@google.com \
    --cc=graf@amazon.com \
    --cc=jasonmiu@google.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=rppt@kernel.org \
    /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