From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: Sayali Patil <sayalip@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Shuah Khan <shuah@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Ritesh Harjani <ritesh.list@gmail.com>,
David Hildenbrand <david@kernel.org>, Zi Yan <ziy@nvidia.com>,
Michal Hocko <mhocko@kernel.org>,
Oscar Salvador <osalvador@suse.de>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Dev Jain <dev.jain@arm.com>,
Liam.Howlett@oracle.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 00/13] selftests/mm: fix failures and robustness improvements
Date: Tue, 17 Mar 2026 11:30:25 +0530 [thread overview]
Message-ID: <cf815c21-138e-44c8-986d-d8496503ee32@linux.ibm.com> (raw)
In-Reply-To: <1f944b56-acb6-44ee-8cc2-6031fcedaeaa@linux.ibm.com>
On 13/03/26 7:46 pm, Sayali Patil wrote:
>
> On 13/03/26 03:35, Andrew Morton wrote:
>> On Thu, 12 Mar 2026 17:55:27 +0530 Sayali Patil
>> <sayalip@linux.ibm.com> wrote:
>>
>>> Hi all,
>>>
>>> Powerpc systems with a 64K base page size exposed several issues while
>>> running mm selftests. Some tests assume specific hugetlb
>>> configurations,
>>> use incorrect interfaces, or fail instead of skipping when the required
>>> kernel features are not available.
>>>
>>> This series fixes these issues and improves test robustness.
Hello Sayali,
I still see, below test failure. Apart from this, everyting else is
working as expected.
# # ------------------------------------------------
# # running ./hugetlb_reparenting_test.sh -cgroup-v2
# # ------------------------------------------------
# # cleanup
# #
# # Test charge, rmdir, uncharge
# # mkdir
# # write
# # Writing to this path: /mnt/huge/test
# # Writing this size: 26843545600
# # Populating.
# # Not writing to memory.
# # Using method=0
# # Shared mapping.
# # RESERVE mapping.
# # Allocating using HUGETLBFS.
# #
# # rmdir
# # uncharge
# # cleanup
# # done
# #
# #
# # Test child only hugetlb usage
# # setup
# # write
# # Writing to this path: /mnt/huge/test2
# # Writing this size: 26843545600
# # Populating.
# # Not writing to memory.
# # Using method=0
# # Shared mapping.
# # RESERVE mapping.
# # Allocating using HUGETLBFS.
# #
# # Assert memory charged correctly for child only use.
# # actual = 11 MB
# # expected = 0 MB
# # FAIL
# # cleanup
# # [FAIL]
# not ok 12 hugetlb_reparenting_test.sh -cgroup-v2 # exit=1
Regards,
Venkat.
>> Thanks, I updated mm.git's mm-new branch to this version.
>>
>>> ---
>>> v1->v2
>>> - For "selftests/mm: ensure destination is hugetlb-backed in
>>> hugepage-mremap":
>>> update FLAGS definition to MAP_HUGETLB | MAP_SHARED |
>>> MAP_POPULATE and
>>> used it for mmap() calls as suggested during review.
>> That was a really small change (below). It's better to wait a while
>> (half to one week) before resending an entire series. So as to
>> hopefully accumulate more changes.
>>
>>
>>
>> --- a/tools/testing/selftests/mm/hugepage-mremap.c~b
>> +++ a/tools/testing/selftests/mm/hugepage-mremap.c
>> @@ -31,7 +31,7 @@
>> #define MB_TO_BYTES(x) (x * 1024 * 1024)
>> #define PROTECTION (PROT_READ | PROT_WRITE | PROT_EXEC)
>> -#define FLAGS (MAP_SHARED | MAP_ANONYMOUS)
>> +#define FLAGS (MAP_HUGETLB | MAP_SHARED | MAP_POPULATE)
>> static void check_bytes(char *addr)
>> {
>> @@ -121,23 +121,20 @@ int main(int argc, char *argv[])
>> /* mmap to a PUD aligned address to hopefully trigger pmd
>> sharing. */
>> unsigned long suggested_addr = 0x7eaa40000000;
>> - void *haddr = mmap((void *)suggested_addr, length, PROTECTION,
>> - MAP_HUGETLB | MAP_SHARED | MAP_POPULATE, fd, 0);
>> + void *haddr = mmap((void *)suggested_addr, length, PROTECTION,
>> FLAGS, fd, 0);
>> ksft_print_msg("Map haddr: Returned address is %p\n", haddr);
>> if (haddr == MAP_FAILED)
>> ksft_exit_fail_msg("mmap1: %s\n", strerror(errno));
>> /* mmap again to a dummy address to hopefully trigger pmd
>> sharing. */
>> suggested_addr = 0x7daa40000000;
>> - void *daddr = mmap((void *)suggested_addr, length, PROTECTION,
>> - MAP_HUGETLB | MAP_SHARED | MAP_POPULATE, fd, 0);
>> + void *daddr = mmap((void *)suggested_addr, length, PROTECTION,
>> FLAGS, fd, 0);
>> ksft_print_msg("Map daddr: Returned address is %p\n", daddr);
>> if (daddr == MAP_FAILED)
>> ksft_exit_fail_msg("mmap3: %s\n", strerror(errno));
>> suggested_addr = 0x7faa40000000;
>> - void *vaddr = mmap((void *)suggested_addr, length, PROTECTION,
>> - MAP_HUGETLB | MAP_SHARED | MAP_POPULATE, fd, 0);
>> + void *vaddr = mmap((void *)suggested_addr, length, PROTECTION,
>> FLAGS, fd, 0);
>> ksft_print_msg("Map vaddr: Returned address is %p\n", vaddr);
>> if (vaddr == MAP_FAILED)
>> ksft_exit_fail_msg("mmap2: %s\n", strerror(errno));
>> _
>>
>>
> Thanks for the guidance. I'll make sure to follow this approach from
> next time.
>
prev parent reply other threads:[~2026-03-17 6:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 12:25 Sayali Patil
2026-03-12 12:25 ` [PATCH v2 01/13] selftests/mm: restore default nr_hugepages value during cleanup in charge_reserved_hugetlb.sh Sayali Patil
2026-03-12 12:43 ` David Hildenbrand (Arm)
2026-03-12 12:25 ` [PATCH v2 02/13] selftests/mm: fix hugetlb pathname construction " Sayali Patil
2026-03-12 12:25 ` [PATCH v2 03/13] selftests/mm: fix hugetlb pathname construction in hugetlb_reparenting_test.sh Sayali Patil
2026-03-12 12:25 ` [PATCH v2 04/13] selftest/mm: fix cgroup task placement and tolerance " Sayali Patil
2026-03-12 12:25 ` [PATCH v2 05/13] selftests/mm: size tmpfs according to PMD page size in split_huge_page_test Sayali Patil
2026-03-12 12:46 ` David Hildenbrand (Arm)
2026-03-12 12:25 ` [PATCH v2 06/13] selftest/mm: adjust hugepage-mremap test size for large huge pages Sayali Patil
2026-03-12 12:25 ` [PATCH v2 07/13] selftest/mm: register existing mapping with userfaultfd in hugepage-mremap Sayali Patil
2026-03-12 12:25 ` [PATCH v2 08/13] selftests/mm: ensure destination is hugetlb-backed " Sayali Patil
2026-03-12 12:25 ` [PATCH v2 09/13] selftests/mm: skip uffd-wp-mremap if UFFD write-protect is unsupported Sayali Patil
2026-03-12 12:50 ` David Hildenbrand (Arm)
2026-03-13 14:26 ` Sayali Patil
2026-03-24 23:56 ` Andrew Morton
2026-03-26 18:01 ` Sayali Patil
2026-03-26 18:38 ` Andrew Morton
2026-03-12 12:25 ` [PATCH v2 10/13] selftests/mm: skip uffd-stress test when nr_pages_per_cpu is zero Sayali Patil
2026-03-12 12:25 ` [PATCH v2 11/13] selftests/mm: fix double increment in linked list cleanup in compaction_test Sayali Patil
2026-03-12 12:51 ` David Hildenbrand (Arm)
2026-03-12 12:25 ` [PATCH v2 12/13] selftests/mm: move hwpoison setup into run_test() and silence modprobe output for memory-failure category Sayali Patil
2026-03-12 12:25 ` [PATCH v2 13/13] selftests/cgroup: extend test_hugetlb_memcg.c to support all huge page sizes Sayali Patil
2026-03-12 22:05 ` [PATCH v2 00/13] selftests/mm: fix failures and robustness improvements Andrew Morton
2026-03-13 14:16 ` Sayali Patil
2026-03-17 6:00 ` Venkat Rao Bagalkote [this message]
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=cf815c21-138e-44c8-986d-d8496503ee32@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
--cc=ritesh.list@gmail.com \
--cc=sayalip@linux.ibm.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