From: Aboorva Devarajan <aboorvad@linux.ibm.com>
To: Wei Yang <richard.weiyang@gmail.com>, akpm@linux-foundation.org
Cc: Liam.Howlett@oracle.com, lorenzo.stoakes@oracle.com,
shuah@kernel.org, pfalcato@suse.de, david@redhat.com,
ziy@nvidia.com, baolin.wang@linux.alibaba.com, npache@redhat.com,
ryan.roberts@arm.com, dev.jain@arm.com, baohua@kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, donettom@linux.ibm.com,
ritesh.list@gmail.com
Subject: Re: [PATCH v4 4/7] mm/selftests: Fix split_huge_page_test failure on systems with 64KB page size
Date: Tue, 19 Aug 2025 13:27:19 +0530 [thread overview]
Message-ID: <588d7bc1af412052da01ada1e316dc3452e35435.camel@linux.ibm.com> (raw)
In-Reply-To: <20250816143129.u2rdwpwvfhsdptvx@master>
On Sat, 2025-08-16 at 14:31 +0000, Wei Yang wrote:
> On Sat, Aug 16, 2025 at 09:31:10AM +0530, Aboorva Devarajan wrote:
> > From: Donet Tom <donettom@linux.ibm.com>
> >
> > The split_huge_page_test fails on systems with a 64KB base page
> > size.
> > This is because the order of a 2MB huge page is different:
> >
> > On 64KB systems, the order is 5.
> >
> > On 4KB systems, it's 9.
> >
> > The test currently assumes a maximum huge page order of 9, which is
> > only
> > valid for 4KB base page systems. On systems with 64KB pages,
> > attempting
> > to split huge pages beyond their actual order (5) causes the test
> > to fail.
> >
> > In this patch, we calculate the huge page order based on the
> > system's base
> > page size. With this change, the tests now run successfully on both
> > 64KB
> > and 4KB page size systems.
> >
> > Fixes: fa6c02315f745 ("mm: huge_memory: a new debugfs interface for
> > splitting THP tests")
> > Co-developed-by: Aboorva Devarajan <aboorvad@linux.ibm.com>
> > Signed-off-by: Aboorva Devarajan <aboorvad@linux.ibm.com>
> > Reviewed-by: Dev Jain <dev.jain@arm.com>
> > Reviewed-by: Zi Yan <ziy@nvidia.com>
> > Signed-off-by: Donet Tom <donettom@linux.ibm.com>
>
> Reviewed-by: Wei Yang <richard.weiyang@gmail.com>
>
> Nit below:
>
> > ---
> > tools/testing/selftests/mm/cow.c | 5 -----
> > .../selftests/mm/split_huge_page_test.c | 22 ++++++++++++----
> > ---
> > tools/testing/selftests/mm/uffd-wp-mremap.c | 5 -----
> > tools/testing/selftests/mm/vm_util.h | 5 +++++
> > 4 files changed, 19 insertions(+), 18 deletions(-)
> >
> > diff --git a/tools/testing/selftests/mm/cow.c
> > b/tools/testing/selftests/mm/cow.c
> > index 90ee5779662f..e742d9313798 100644
> > --- a/tools/testing/selftests/mm/cow.c
> > +++ b/tools/testing/selftests/mm/cow.c
> > @@ -41,11 +41,6 @@ static size_t hugetlbsizes[10];
> > static int gup_fd;
> > static bool has_huge_zeropage;
> >
> > -static int sz2ord(size_t size)
> > -{
> > - return __builtin_ctzll(size / pagesize);
> > -}
> > -
> > static int detect_thp_sizes(size_t sizes[], int max)
> > {
> > int count = 0;
> > diff --git a/tools/testing/selftests/mm/split_huge_page_test.c
> > b/tools/testing/selftests/mm/split_huge_page_test.c
> > index eadbeb820d71..7cbeaebc9d71 100644
> > --- a/tools/testing/selftests/mm/split_huge_page_test.c
> > +++ b/tools/testing/selftests/mm/split_huge_page_test.c
> > @@ -523,6 +523,9 @@ int main(int argc, char **argv)
> > const char *fs_loc;
> > bool created_tmp;
> > int offset;
> > + unsigned int max_order;
> > + unsigned int nr_pages;
> > + unsigned int tests;
> >
> > ksft_print_header();
> >
> > @@ -534,35 +537,38 @@ int main(int argc, char **argv)
> > if (argc > 1)
> > optional_xfs_path = argv[1];
> >
> > - ksft_set_plan(1+8+1+9+9+8*4+2);
> > -
> > pagesize = getpagesize();
> > pageshift = ffs(pagesize) - 1;
> > pmd_pagesize = read_pmd_pagesize();
> > if (!pmd_pagesize)
> > ksft_exit_fail_msg("Reading PMD pagesize
> > failed\n");
> >
> > + nr_pages = pmd_pagesize / pagesize;
> > + max_order = sz2ord(pmd_pagesize);
> ^
> extra space here
Hi Wei,
Thanks for the review. I’ve sent a fixup patch for this:
https://lore.kernel.org/all/20250819041239.167537-1-aboorvad@linux.ibm.com/
Andrew,
Could you please apply the above fixup patch?
Regards,
Aboorva
>
> > + tests = 2 + (max_order - 1) + (2 * max_order) + (max_order
> > - 1) * 4 + 2;
> > + ksft_set_plan(tests);
> > +
> > fd_size = 2 * pmd_pagesize;
> >
> > split_pmd_zero_pages();
> >
next prev parent reply other threads:[~2025-08-19 7:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 4:01 [PATCH v4 0/7] selftests/mm: Fix false positives and skip unsupported tests Aboorva Devarajan
2025-08-16 4:01 ` [PATCH v4 1/7] mm/selftests: Fix incorrect pointer being passed to mark_range() Aboorva Devarajan
2025-08-16 14:05 ` Wei Yang
2025-08-16 4:01 ` [PATCH v4 2/7] selftests/mm: Add support to test 4PB VA on PPC64 Aboorva Devarajan
2025-08-16 14:06 ` Wei Yang
2025-08-16 4:01 ` [PATCH v4 3/7] selftest/mm: Fix ksm_funtional_test failures Aboorva Devarajan
2025-08-16 14:07 ` Wei Yang
2025-08-16 4:01 ` [PATCH v4 4/7] mm/selftests: Fix split_huge_page_test failure on systems with 64KB page size Aboorva Devarajan
2025-08-16 14:31 ` Wei Yang
2025-08-17 7:27 ` Giant Sand Fans
2025-08-17 7:42 ` Giant Sand Fans
2025-08-17 8:07 ` David Hildenbrand
2025-08-18 2:21 ` Wei Yang
2025-08-19 7:57 ` Aboorva Devarajan [this message]
2025-08-19 4:12 ` [Fixup PATCH] mm/selftests: Fix formattig in split_huge_page_test Aboorva Devarajan
2025-08-19 7:25 ` David Hildenbrand
2025-08-19 7:28 ` David Hildenbrand
2025-08-19 7:39 ` Aboorva Devarajan
2025-08-16 4:01 ` [PATCH v4 5/7] selftests/mm: fix child process exit codes in ksm_functional_tests Aboorva Devarajan
2025-08-16 14:43 ` Wei Yang
2025-08-19 1:48 ` Aboorva Devarajan
2025-08-16 4:01 ` [PATCH v4 6/7] selftests/mm: skip thuge-gen test if system is not setup properly Aboorva Devarajan
2025-08-16 14:46 ` Wei Yang
2025-08-16 4:01 ` [PATCH v4 7/7] selftests/mm: skip hugepage-mremap test if userfaultfd unavailable Aboorva Devarajan
2025-08-16 14:46 ` Wei Yang
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=588d7bc1af412052da01ada1e316dc3452e35435.camel@linux.ibm.com \
--to=aboorvad@linux.ibm.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=donettom@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=pfalcato@suse.de \
--cc=richard.weiyang@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).