From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Yeoreum Yun <yeoreum.yun@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>, Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <liam@infradead.org>,
Nico Pache <nico.pache@linux.dev>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>,
Lance Yang <lance.yang@linux.dev>,
Usama Arif <usama.arif@linux.dev>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
Kevin Brodsky <kevin.brodsky@arm.com>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] kselftest: mm: prevent random failure of huge page split for khugepaged
Date: Wed, 2 Sep 2026 16:15:17 +0100 [thread overview]
Message-ID: <apg7FNLtFO3Ea5qC@gremlin> (raw)
In-Reply-To: <20260902-fix_split-v4-1-85f03905f7b1@arm.com>
On Wed, Sep 02, 2026 at 01:09:35PM +0100, Yeoreum Yun wrote:
> There're some random failure for split_huge_page_test when khugepaged
> collapses pages into pmd again which had split by the test.
>
> Prevent the khugepaged's collapses for split page by setting the
> mapped pmd-huge-page with MADV_NOHUGEPAGE before split.
Maybe worth saying that MADV_NOHUGEPAGE doesn't immediately split anything, just
prevents future khugepaged collapses?
>
> Suggested-by: Kevin Brodsky <kevin.brodsky@arm.com>
> Suggested-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
LGTM, thanks, with a few nits above/below (sorry! :P)
Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> ---
> tools/testing/selftests/mm/split_huge_page_test.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/tools/testing/selftests/mm/split_huge_page_test.c b/tools/testing/selftests/mm/split_huge_page_test.c
> index 86a603692826..4bbad892bc57 100644
> --- a/tools/testing/selftests/mm/split_huge_page_test.c
> +++ b/tools/testing/selftests/mm/split_huge_page_test.c
> @@ -168,6 +168,14 @@ static char *allocate_zero_filled_hugepage(size_t len)
> return result;
> }
>
> +static void madv_nohuge(void *addr, size_t len)
Maybe call it disable_khugepaged() to make it explicit that's what this is doing
rather than eliminating any THP pages in the range?
> +{
Maybe a comment here like:
/*
* Disables khugepaged from collapsing THPs in range, existing THP
* pages remain.
*/
> + if (!madvise(addr, len, MADV_NOHUGEPAGE))
> + return;
> +
> + ksft_exit_fail_msg("MADV_NOHUGEPAGE failed, err=%d\n", errno);
> +}
> +
> static void verify_rss_anon_split_huge_page_all_zeroes(char *one_page, int nr_hpages, size_t len)
> {
> unsigned long rss_anon_before, rss_anon_after;
> @@ -180,6 +188,9 @@ static void verify_rss_anon_split_huge_page_all_zeroes(char *one_page, int nr_hp
> if (!rss_anon_before)
> ksft_exit_fail_msg("No RssAnon is allocated before split\n");
>
> + /* Prevent khugepaged from collapsing the pages. */
> + madv_nohuge(one_page, len);
> +
> /* split all THPs */
> write_debugfs(PID_FMT, getpid(), (uint64_t)one_page,
> (uint64_t)one_page + len, 0);
> @@ -227,6 +238,9 @@ static void split_pmd_thp_to_order(int order)
> if (!check_huge_anon(one_page, 4 * pmd_pagesize, 4, pmd_pagesize))
> ksft_exit_fail_msg("No THP is allocated\n");
>
> + /* Prevent khugepaged from collapsing the pages. */
> + madv_nohuge(one_page, len);
> +
> /* split all THPs */
> write_debugfs(PID_FMT, getpid(), (uint64_t)one_page,
> (uint64_t)one_page + len, order);
> @@ -275,6 +289,9 @@ static void split_pte_mapped_thp(void)
> goto out;
> }
>
> + /* Prevent khugepaged from collapsing the pages. */
> + madv_nohuge(thp_area, thp_area_size);
> +
> /*
> * To challenge spitting code, we will mremap a single page of each
> * THP (page[i] of thp[i]) in the thp_area into page_area. This will
> @@ -542,6 +559,8 @@ static int create_pagecache_thp_and_fd(const char *testfile, size_t fd_size,
> ksft_test_result_skip("Pagecache folio split skipped\n");
> return -2;
> }
> + /* Prevent khugepaged from collapsing the pages. */
> + madv_nohuge(*addr, fd_size);
> return 0;
> err_out_close:
> close(*fd);
>
> --
> 2.43.0
>
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-09-02 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 12:09 [PATCH v4 0/3] kselftest: mm: fix some failure of split_huge_page_test Yeoreum Yun
2026-09-02 12:09 ` [PATCH v4 1/3] kselftest: mm: prevent random failure of huge page split for khugepaged Yeoreum Yun
2026-09-02 14:16 ` Zi Yan
2026-09-02 15:15 ` Lorenzo Stoakes (ARM) [this message]
2026-09-02 15:16 ` Lorenzo Stoakes (ARM)
2026-09-02 15:33 ` Yeoreum Yun
2026-09-02 12:09 ` [PATCH v4 2/3] kselftest: mm: replace usage of /proc/self/smaps for check_huge_xxx() helper Yeoreum Yun
2026-09-02 12:09 ` [PATCH v4 3/3] kselftest: mm: introduce alloc_isolated_mem() Yeoreum Yun
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=apg7FNLtFO3Ea5qC@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=kevin.brodsky@arm.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=nico.pache@linux.dev \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=yeoreum.yun@arm.com \
--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