From: sashiko-bot@kernel.org
To: "Gerald Schaefer" <gerald.schaefer@linux.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>
Cc: "Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH] s390/mm: Allow hugepage migration for s390
Date: Fri, 06 Nov 2026 17:28:48 +0000 [thread overview]
Message-ID: <sashiko-outbox-201931@kernel.org> (raw)
In-Reply-To: <20261106170844.4079771-1-gerald.schaefer@linux.ibm.com>
> After hugetlbfs PTE_MARKER support for s390 introduced region-third
> and segment table swap entries, it is possible to also allow hugepage
> migration for s390.
>
> This fixes the problem that hugetlbfs pages could not be allocated
> from ZONE_MOVABLE memory, which is often used in combination with
> memory hotplug. Therefore, without support for hugepage migration,
> a large portion of system memory could be unavailable for hugetlbfs
> page allocations.
>
> Besides selecting ARCH_ENABLE_HUGEPAGE_MIGRATION, this only requires
> definition of arch_hugetlb_migration_supported(), which can make use
> of the existing arch_hugetlb_valid_size() function, similar to other
> architectures.
>
> Signed-off-by: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261106170844.4079771-1-gerald.schaefer@linux.ibm.com?part=1
next prev parent reply other threads:[~2026-11-06 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 17:08 [PATCH] s390/mm: Allow hugepage migration for s390 Gerald Schaefer
2026-11-06 17:28 ` sashiko-bot [this message]
2026-11-11 16:09 ` Alexander Gordeev
2026-11-11 17:21 ` Gerald Schaefer
2026-11-11 17:33 ` Gerald Schaefer
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-201931@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.