From: Sayali Patil <sayalip@linux.ibm.com>
To: 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,
Miaohe Lin <linmiaohe@huawei.com>,
Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Subject: Re: [PATCH v6 00/14] selftests/mm: fix failures and robustness improvements
Date: Wed, 13 May 2026 12:10:08 +0530 [thread overview]
Message-ID: <826cbbca-c980-4a33-bdd8-d9025951648d@linux.ibm.com> (raw)
In-Reply-To: <20260512202439.e71f233281428ff596dab0b6@linux-foundation.org>
Hi Andrew,
Sure, I will rebase the series on top of the current mm-new branch and
resend an updated version. It appears that Mike’s changes have modified
many selftests, so I will adjust the series accordingly and ensure it
applies cleanly.
Thanks,
Sayali
On 13/05/26 08:54, Andrew Morton wrote:
> On Mon, 4 May 2026 13:54:37 +0530 Sayali Patil <sayalip@linux.ibm.com> wrote:
>
>> 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.
>
> Sorry, bitrot. Mike's monster series "make MM selftests more CI
> friendly" has moved a lot of this code around then altered it. Can you
> please redo against mm.git's mm-new branch?
>
> Thanks.
>
>
prev parent reply other threads:[~2026-05-13 6:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 8:24 [PATCH v6 00/14] selftests/mm: fix failures and robustness improvements Sayali Patil
2026-05-04 8:24 ` [PATCH v6 01/14] selftests/mm: restore default nr_hugepages value via exit trap in charge_reserved_hugetlb.sh Sayali Patil
2026-05-04 8:24 ` [PATCH v6 02/14] selftests/mm: fix hugetlb pathname construction " Sayali Patil
2026-05-04 8:24 ` [PATCH v6 03/14] selftests/mm: restore default nr_hugepages value via exit trap in hugetlb_reparenting_test.sh Sayali Patil
2026-05-04 8:24 ` [PATCH v6 04/14] selftests/mm: fix hugetlb pathname construction " Sayali Patil
2026-05-04 8:24 ` [PATCH v6 05/14] selftests/mm: fix cgroup task placement and drop memory.current checks " Sayali Patil
2026-05-04 8:24 ` [PATCH v6 06/14] selftests/mm: size tmpfs according to PMD page size in split_huge_page_test Sayali Patil
2026-05-04 8:24 ` [PATCH v6 07/14] selftests/mm: free dynamically allocated PMD-sized buffers " Sayali Patil
2026-05-04 8:24 ` [PATCH v6 08/14] selftest/mm: align memory size to huge page size in hugepage-mremap test Sayali Patil
2026-05-04 8:24 ` [PATCH v6 09/14] selftest/mm: register existing mapping with userfaultfd in hugepage-mremap Sayali Patil
2026-05-04 8:24 ` [PATCH v6 10/14] selftests/mm: ensure destination is hugetlb-backed " Sayali Patil
2026-05-04 8:24 ` [PATCH v6 11/14] selftests/mm: skip uffd-wp-mremap if UFFD write-protect is unsupported Sayali Patil
2026-05-04 8:24 ` [PATCH v6 12/14] selftests/mm: skip uffd-stress test when nr_pages_per_cpu is zero Sayali Patil
2026-05-04 8:24 ` [PATCH v6 13/14] selftests/mm: move hwpoison setup into run_test() and silence modprobe output for memory-failure category Sayali Patil
2026-05-04 8:24 ` [PATCH v6 14/14] selftests/mm: clarify alternate unmapping in compaction_test Sayali Patil
2026-05-13 3:10 ` [PATCH v6 00/14] selftests/mm: fix failures and robustness improvements Andrew Morton
2026-05-13 3:24 ` Andrew Morton
2026-05-13 6:40 ` Sayali Patil [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=826cbbca-c980-4a33-bdd8-d9025951648d@linux.ibm.com \
--to=sayalip@linux.ibm.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=linmiaohe@huawei.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=shuah@kernel.org \
--cc=venkat88@linux.ibm.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