From: Zi Yan <ziy@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: Usama Arif <usamaarif642@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
david@redhat.com, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, corbet@lwn.net, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, hannes@cmpxchg.org,
baohua@kernel.org, shakeel.butt@linux.dev, riel@surriel.com,
laoar.shao@gmail.com, dev.jain@arm.com,
baolin.wang@linux.alibaba.com, npache@redhat.com,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
ryan.roberts@arm.com, vbabka@suse.cz, jannh@google.com,
Arnd Bergmann <arnd@arndb.de>,
sj@kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, kernel-team@meta.com,
Aishwarya.TCV@arm.com
Subject: Re: [PATCH v5 6/7] selftests: prctl: introduce tests for disabling THPs completely
Date: Fri, 05 Sep 2025 13:55:53 -0400 [thread overview]
Message-ID: <5F7011AF-8CC2-45E0-A226-273261856FF0@nvidia.com> (raw)
In-Reply-To: <c8249725-e91d-4c51-b9bb-40305e61e20d@sirena.org.uk>
On 5 Sep 2025, at 13:43, Mark Brown wrote:
> On Fri, Aug 15, 2025 at 02:54:58PM +0100, Usama Arif wrote:
>> The test will set the global system THP setting to never, madvise
>> or always depending on the fixture variant and the 2M setting to
>> inherit before it starts (and reset to original at teardown).
>> The fixture setup will also test if PR_SET_THP_DISABLE prctl call can
>> be made to disable all THPs and skip if it fails.
>
> I don't think this is an issue in this patch but with it we're seeing
> build failures in -next on arm64 with:
>
> make KBUILD_BUILD_USER=KernelCI FORMAT=.xz ARCH=arm64 HOSTCC=gcc CROSS_COMPILE=aarch64-linux-gnu- CROSS_COMPILE_COMPAT=arm-linux-gnueabihf- CC="ccache aarch64-linux-gnu-gcc" O=/tmp/kci/linux/build -C/tmp/kci/linux -j98 kselftest-gen_tar
>
> ...
>
> CC prctl_thp_disable
> prctl_thp_disable.c: In function ‘test_mmap_thp’:
> prctl_thp_disable.c:64:39: error: ‘MADV_COLLAPSE’ undeclared (first use in this function); did you mean ‘MADV_COLD’?
> 64 | madvise(mem, pmdsize, MADV_COLLAPSE);
> | ^~~~~~~~~~~~~
> | MADV_COLD
>
> since the headers_install copy of asm-generic/mman-common.h doesn't
> appear to being picked up with the above build invocation (most others
> are fine). I'm not clear why, it looks like an appropriate -isystem
> ends up getting passed to the compiler:
>
> aarch64-linux-gnu-gcc -Wall -O2 -I /linux/tools/testing/selftests/../../.. -isystem /tmp/kci/linux/build/usr/include -isystem /linux/tools/testing/selftests/../../../tools/include/uapi -U_FORTIFY_SOURCE -D_GNU_SOURCE= prctl_thp_disable.c vm_util.c thp_settings.c -lrt -lpthread -lm -o /tmp/kci/linux/build/kselftest/mm/prctl_thp_disable
>
> but the header there is getting ignored AFAICT. Probably the problem is
> fairly obvious and I'm just being slow - I'm not quite 100% at the
> minute.
prctl_thp_disable.c uses “#include <sys/mman.h>” but asm-generic/mman-common.h
is included in asm/mman.h. And sys/mman.h gets MADV_COLLAPSE from
bits/mman-linux.h. Maybe that is why?
>
> Thanks to Aishwarya for confirming which patch triggered the issue.
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2025-09-05 17:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 13:54 [PATCH v5 0/7] prctl: extend PR_SET_THP_DISABLE to only provide THPs when advised Usama Arif
2025-08-15 13:54 ` [PATCH v5 1/7] prctl: extend PR_SET_THP_DISABLE to optionally exclude VM_HUGEPAGE Usama Arif
2025-08-15 13:54 ` [PATCH v5 2/7] mm/huge_memory: convert "tva_flags" to "enum tva_type" Usama Arif
2025-08-15 13:54 ` [PATCH v5 3/7] mm/huge_memory: respect MADV_COLLAPSE with PR_THP_DISABLE_EXCEPT_ADVISED Usama Arif
2025-08-15 13:54 ` [PATCH v5 4/7] docs: transhuge: document process level THP controls Usama Arif
2025-08-15 13:54 ` [PATCH v5 5/7] selftest/mm: Extract sz2ord function into vm_util.h Usama Arif
2025-08-16 6:15 ` Andrew Morton
2025-08-16 6:24 ` David Hildenbrand
2025-08-15 13:54 ` [PATCH v5 6/7] selftests: prctl: introduce tests for disabling THPs completely Usama Arif
2025-08-18 9:36 ` David Hildenbrand
2025-08-18 10:43 ` Usama Arif
2025-08-18 10:41 ` Usama Arif
2025-09-05 17:43 ` Mark Brown
2025-09-05 17:55 ` Zi Yan [this message]
2025-09-05 18:02 ` Mark Brown
2025-09-05 19:40 ` Usama Arif
2025-09-05 19:44 ` Usama Arif
2025-09-08 15:38 ` Mark Brown
2025-09-08 15:40 ` Usama Arif
2025-08-15 13:54 ` [PATCH v5 7/7] selftests: prctl: introduce tests for disabling THPs except for madvise Usama Arif
2025-08-18 10:42 ` Usama Arif
2025-08-18 13:06 ` David Hildenbrand
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=5F7011AF-8CC2-45E0-A226-273261856FF0@nvidia.com \
--to=ziy@nvidia.com \
--cc=Aishwarya.TCV@arm.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=jannh@google.com \
--cc=kernel-team@meta.com \
--cc=laoar.shao@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=npache@redhat.com \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=sj@kernel.org \
--cc=surenb@google.com \
--cc=usamaarif642@gmail.com \
--cc=vbabka@suse.cz \
/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