From: Andrew Morton <akpm@linux-foundation.org>
To: Sayali Patil <sayalip@linux.ibm.com>
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 v7 00/13] selftests/mm: fix failures and robustness improvements
Date: Thu, 21 May 2026 14:54:49 -0700 [thread overview]
Message-ID: <20260521145449.ff6b050527ca494a7ba66e9c@linux-foundation.org> (raw)
In-Reply-To: <cover.1779296493.git.sayalip@linux.ibm.com>
On Thu, 21 May 2026 12:03:26 +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.
Thanks, I've re-added this series to mm.git's mm-new branch.
> I checked the AI review comments. Most of them appear to be relatively
> minor.
>
> I have sent one fixup patch ("selftests/mm: use ksft_exit_skip() instead
> of KSFT_SKIP in uffd-stress") for the comment in "selftests/mm: skip
> uffd-stress test when nr_pages_per_cpu is zero". The remaining comments
> were either already discussed earlier or can be addressed later if needed.
Cool, thanks for letting us know where we stand with the AI review.
It helps!
prev parent reply other threads:[~2026-05-21 21:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 6:33 [PATCH v7 00/13] selftests/mm: fix failures and robustness improvements Sayali Patil
2026-05-21 6:33 ` [PATCH v7 01/13] selftests/mm: restore default nr_hugepages value via exit trap in charge_reserved_hugetlb.sh Sayali Patil
2026-05-21 6:33 ` [PATCH v7 02/13] selftests/mm: fix hugetlb pathname construction " Sayali Patil
2026-05-21 6:47 ` [PATCH v7 03/13] selftests/mm: restore default nr_hugepages value via exit trap in hugetlb_reparenting_test.sh Sayali Patil
2026-05-21 6:47 ` [PATCH v7 04/13] selftests/mm: fix hugetlb pathname construction " Sayali Patil
2026-05-21 6:47 ` [PATCH v7 05/13] selftests/mm: fix cgroup task placement and drop memory.current checks " Sayali Patil
2026-05-21 6:47 ` [PATCH v7 06/13] selftests/mm: size tmpfs according to PMD page size in split_huge_page_test Sayali Patil
2026-05-21 6:47 ` [PATCH v7 07/13] selftests/mm: free dynamically allocated PMD-sized buffers " Sayali Patil
2026-05-21 6:47 ` [PATCH v7 08/13] selftest/mm: register existing mapping with userfaultfd in hugetlb-mremap Sayali Patil
2026-05-21 6:47 ` [PATCH v7 09/13] selftests/mm: ensure destination is hugetlb-backed " Sayali Patil
2026-05-21 6:47 ` [PATCH v7 10/13] selftests/mm: skip uffd-wp-mremap if UFFD write-protect is unsupported Sayali Patil
2026-05-21 6:47 ` [PATCH v7 11/13] selftests/mm: skip uffd-stress test when nr_pages_per_cpu is zero Sayali Patil
2026-05-21 9:13 ` Sayali Patil
2026-05-21 6:47 ` [PATCH v7 12/13] selftests/mm: move hwpoison setup into run_test() and silence modprobe output for memory-failure category Sayali Patil
2026-05-21 6:47 ` [PATCH v7 13/13] selftests/mm: clarify alternate unmapping in compaction_test Sayali Patil
2026-05-21 9:24 ` [PATCH v7 00/13] selftests/mm: fix failures and robustness improvements Sayali Patil
2026-05-21 21:54 ` Andrew Morton [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=20260521145449.ff6b050527ca494a7ba66e9c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--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=sayalip@linux.ibm.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