From: sashiko-bot@kernel.org
To: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>,
"Mike Rapoport" <rppt@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Kees Cook" <kees@kernel.org>, "Alexander Graf" <graf@amazon.com>,
"Changyuan Lyu" <changyuanl@google.com>
Cc: "Tony Luck" <tony.luck@intel.com>,
"Pasha Tatashin" <pasha.tatashin@soleen.com>,
kexec@lists.infradead.org, "Pratyush Yadav" <pratyush@kernel.org>
Subject: Re: [RFC PATCH 1/2] memblock: factor out the KHO bootmem check from memblock_alloc_hugetlb()
Date: Wed, 21 Oct 2026 21:20:08 +0000 [thread overview]
Message-ID: <sashiko-outbox-180693@kernel.org> (raw)
In-Reply-To: <20261021211058.83483-2-azpijr@gmail.com>
> reserve_mem regions are preserved with KHO too, and need the same search
> that keeps HugeTLB pages out of KHO bootmem. Move it into a helper.
>
> No functional change intended.
>
> Signed-off-by: Jose A. Perez de Azpillaga <azpijr@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261021211058.83483-1-azpijr@gmail.com?part=1
next prev parent reply other threads:[~2026-10-21 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 21:10 [RFC PATCH 0/2] memblock: keep reserve_mem regions out of KHO bootmem Jose A. Perez de Azpillaga
2026-10-21 21:10 ` Jose A. Perez de Azpillaga
2026-10-21 21:10 ` [RFC PATCH 1/2] memblock: factor out the KHO bootmem check from memblock_alloc_hugetlb() Jose A. Perez de Azpillaga
2026-10-21 21:10 ` Jose A. Perez de Azpillaga
2026-10-21 21:20 ` sashiko-bot [this message]
2026-10-21 21:10 ` [RFC PATCH 2/2] memblock: don't allocate reserve_mem regions from KHO bootmem Jose A. Perez de Azpillaga
2026-10-21 21:10 ` Jose A. Perez de Azpillaga
2026-10-21 21:20 ` sashiko-bot
2026-10-22 13:37 ` [RFC PATCH 0/2] memblock: keep reserve_mem regions out of " Pratyush Yadav
2026-10-22 13:37 ` Pratyush Yadav
2026-10-22 20:16 ` Jose A. Perez de Azpillaga
2026-10-22 20:16 ` Jose A. Perez de Azpillaga
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=sashiko-outbox-180693@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=azpijr@gmail.com \
--cc=changyuanl@google.com \
--cc=graf@amazon.com \
--cc=kees@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tony.luck@intel.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.