From: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: linux-s390 <linux-s390@vger.kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Subject: Re: [PATCH] s390/mm: Allow hugepage migration for s390
Date: Wed, 11 Nov 2026 18:21:49 +0100 [thread overview]
Message-ID: <20261111182149.7ffa706b@thinkpad-T15> (raw)
In-Reply-To: <acdfe7cd-1f50-4a10-b9cf-5a4318fd582e-agordeev@linux.ibm.com>
On Wed, 11 Nov 2026 17:09:45 +0100
Alexander Gordeev <agordeev@linux.ibm.com> wrote:
[...]
> > @@ -241,3 +241,15 @@ unsigned int __init arch_hugetlb_cma_order(void)
> >
> > return 0;
> > }
> > +
> > +bool __init arch_hugetlb_valid_size(unsigned long size)
> > +{
> > + return __hugetlb_valid_size(size);
> > +}
> > +
> > +#ifdef CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION
>
> Could you please use IS_ENABLED() instead?
Does the benefit mentioned in Documentation/process/coding-style.rst
for usage "within code" also apply in such a case, i.e. not within
code?
Or are there other benefits or coding style requirements? Just wondering,
because I never saw that in such a case where a whole function is behind
such an #ifdef.
>
> > +bool arch_hugetlb_migration_supported(struct hstate *h)
> > +{
> > + return __hugetlb_valid_size(huge_page_size(h));
> > +}
> > +#endif
>
> Otherwise, LGTM.
>
> Thanks!
next prev parent reply other threads:[~2026-11-11 17:21 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
2026-11-11 16:09 ` Alexander Gordeev
2026-11-11 17:21 ` Gerald Schaefer [this message]
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=20261111182149.7ffa706b@thinkpad-T15 \
--to=gerald.schaefer@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-s390@vger.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