All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	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 1/2] kho: skip zero-sized lowmem and global bootmem areas
Date: Wed, 4 Nov 2026 18:50:04 +0200	[thread overview]
Message-ID: <autiPITgQl7nhFER@kernel.org> (raw)
In-Reply-To: <autM3_pSLuOGZQCh@google.com>

On Wed, Nov 04, 2026 at 10:32:14AM -0500, Pasha Tatashin wrote:
> On 11-04 13:22, Mike Rapoport wrote:
> > On Tue, Nov 03, 2026 at 02:48:36PM -0500, Pasha Tatashin wrote:
> > > > @@ -852,56 +873,32 @@ 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(&i, bootmem_size_lowmem,
> > > > +				     ARCH_LOW_ADDRESS_LIMIT, NUMA_NO_NODE)) {
> > > >  		pr_err("Failed to reserve lowmem bootmem\n");
> > > 
> > > You are adding a helper that returns an error code and then ignoring it 
> > > at all call sites. Even though it can only return -ENOMEM right now, 
> > > dropping the return value is not good practice.
> > 
> > I don't think error code is important here.
> 
> Perhaps, but it is just not elegant to add a function that returns an 
> error, call that function from three places, and ignore that error every 
> time.

Because it's not important what the error was. 
 
> What is wrong with:
> 
> err = kho_reserve_bootmem_area(...);
> if (err) {
>         pr_err("Failed to reserve lowmem bootmem: %pe\n", ERR_PTR(err));
>         ...
> }

More churn for no value?

> -- 
> Pasha

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2026-11-04 16:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 11:49 [PATCH 0/2] kho: fix bootmem sizing Mike Rapoport (Microsoft)
2026-11-03 11:49 ` [PATCH 1/2] kho: skip zero-sized lowmem and global bootmem areas Mike Rapoport (Microsoft)
2026-11-03 14:14   ` Pratyush Yadav
2026-11-03 18:32     ` Mike Rapoport
2026-11-04 12:09       ` Pratyush Yadav
2026-11-03 19:48   ` Pasha Tatashin
2026-11-04 11:22     ` Mike Rapoport
2026-11-04 15:32       ` Pasha Tatashin
2026-11-04 16:50         ` Mike Rapoport [this message]
2026-11-03 11:49 ` [PATCH 2/2] kho: fix bootmem sizing Mike Rapoport (Microsoft)
2026-11-03 16:01   ` Pratyush Yadav
2026-11-03 18:36     ` Mike Rapoport
2026-11-04 12:13       ` 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=autiPITgQl7nhFER@kernel.org \
    --to=rppt@kernel.org \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.