From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Zi Yan <ziy@nvidia.com>
Cc: akpm@linux-foundation.org, david@redhat.com,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, shuah@kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] selftests: khugepaged: fix the shmem collapse failure
Date: Fri, 13 Jun 2025 09:41:14 +0800 [thread overview]
Message-ID: <28221305-14de-4e46-a9f4-8bf90c7b32c0@linux.alibaba.com> (raw)
In-Reply-To: <AFC17CA1-DF5A-48F0-8E63-E139005F5880@nvidia.com>
On 2025/6/12 23:46, Zi Yan wrote:
> On 11 Jun 2025, at 23:54, Baolin Wang wrote:
>
>> When running the khugepaged selftest for shmem (./khugepaged all:shmem),
>> I encountered the following test failures:
>> "
>> Run test: collapse_full (khugepaged:shmem)
>> Collapse multiple fully populated PTE table.... Fail
>> ...
>> Run test: collapse_single_pte_entry (khugepaged:shmem)
>> Collapse PTE table with single PTE entry present.... Fail
>> ...
>> Run test: collapse_full_of_compound (khugepaged:shmem)
>> Allocate huge page... OK
>> Split huge page leaving single PTE page table full of compound pages... OK
>> Collapse PTE table full of compound pages.... Fail
>> "
>>
>> The reason for the failure is that, it will set MADV_NOHUGEPAGE to prevent
>> khugepaged from continuing to scan shmem VMA after khugepaged finishes
>> scanning in the wait_for_scan() function. Moreover, shmem requires a refault
>> to establish PMD mappings.
>>
>> However, after commit 2b0f922323cc, PMD mappings are prevented if the VMA is
>
> Can you add the title of the commit? It is easier to understand the context.
>
> 2b0f922323cc ("mm: don't install PMD mappings when THPs are disabled by the hw/process/vma")
Sure.
>
>> set with MADV_NOHUGEPAGE flag, so shmem cannot establish PMD mappings during
>> refault.
>>
>> To fix this issue, we can set the MADV_NOHUGEPAGE flag after the shmem refault.
>> With this fix, the shmem test case passes.
>>
>> Fixes: 2b0f922323cc ("mm: don't install PMD mappings when THPs are disabled by the hw/process/vma")
>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>> ---
>> tools/testing/selftests/mm/khugepaged.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/tools/testing/selftests/mm/khugepaged.c b/tools/testing/selftests/mm/khugepaged.c
>> index 8a4d34cce36b..d462f62d8116 100644
>> --- a/tools/testing/selftests/mm/khugepaged.c
>> +++ b/tools/testing/selftests/mm/khugepaged.c
>> @@ -561,8 +561,6 @@ static bool wait_for_scan(const char *msg, char *p, int nr_hpages,
>> usleep(TICK);
>> }
>>
>> - madvise(p, nr_hpages * hpage_pmd_size, MADV_NOHUGEPAGE);
>> -
>> return timeout == -1;
>> }
>>
> I assume you are going to just remove this madvise based on your discussion
> with David. With that, feel free to add Reviewed-by: Zi Yan <ziy@nvidia.com>
Thanks.
next prev parent reply other threads:[~2025-06-13 1:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 3:54 [PATCH 1/2] selftests: khugepaged: fix the shmem collapse failure Baolin Wang
2025-06-12 3:54 ` [PATCH 2/2] selftests: mm: add shmem collpase as a default test item Baolin Wang
2025-06-12 4:20 ` Bird, Tim
2025-06-12 5:33 ` Baolin Wang
2025-06-12 5:14 ` Dev Jain
2025-06-12 10:24 ` David Hildenbrand
2025-06-12 15:47 ` Zi Yan
2025-06-12 5:10 ` [PATCH 1/2] selftests: khugepaged: fix the shmem collapse failure Dev Jain
2025-06-12 5:18 ` Baolin Wang
2025-06-12 10:08 ` David Hildenbrand
2025-06-12 11:37 ` Baolin Wang
2025-06-12 11:45 ` David Hildenbrand
2025-06-12 12:14 ` Baolin Wang
2025-06-12 15:46 ` Zi Yan
2025-06-12 15:48 ` David Hildenbrand
2025-06-13 1:41 ` Baolin Wang [this message]
2025-06-20 6:13 ` Mario Casquero
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=28221305-14de-4e46-a9f4-8bf90c7b32c0@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=david@redhat.com \
--cc=dev.jain@arm.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=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