linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nico Pache <npache@redhat.com>
To: linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: ben@decadent.org.uk, shuah@kernel.org, akpm@linux-foundation.org,
	usama.anjum@collabora.com
Subject: [PATCH v2 0/3] selftests/mm: Improve Hugepage Test Handling in MM Selftests
Date: Wed,  6 Mar 2024 15:37:11 -0700	[thread overview]
Message-ID: <20240306223714.320681-1-npache@redhat.com> (raw)

This series addresses issues related to hugepage requirements in the MM
selftests, ensuring tests are skipped rather than failing when the
necessary hugepage count is not met.

This adjustment allows for a more graceful handling for systems with
insufficient hugepages, preventing unnecessary test failures and improving
the overall robustness of the test suite.

Nico Pache (3):
  selftests/mm: Dont fail testsuite due to a lack of hugepages
  selftests/mm: Skip uffd hugetlb tests with insufficient hugepages
  selftests/mm: Skip the hugetlb-madvise tests on unmet hugepage
    requirements

Changes from v1:
  - Added checks to skip tests when hugepage requirements are not met, rather
    than exiting with a failure.

 tools/testing/selftests/mm/hugetlb-madvise.c | 2 +-
 tools/testing/selftests/mm/run_vmtests.sh    | 1 -
 tools/testing/selftests/mm/uffd-stress.c     | 6 ++++++
 3 files changed, 7 insertions(+), 2 deletions(-)

-- 
2.44.0



             reply	other threads:[~2024-03-06 22:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 22:37 Nico Pache [this message]
2024-03-06 22:37 ` [PATCH v2 1/3] selftests/mm: Dont fail testsuite due to a lack of hugepages Nico Pache
2024-03-06 22:37 ` [PATCH v2 2/3] selftests/mm: Skip uffd hugetlb tests with insufficient hugepages Nico Pache
2024-03-06 22:37 ` [PATCH v2 3/3] selftests/mm: Skip the hugetlb-madvise tests on unmet hugepage requirements Nico Pache

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=20240306223714.320681-1-npache@redhat.com \
    --to=npache@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ben@decadent.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shuah@kernel.org \
    --cc=usama.anjum@collabora.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;
as well as URLs for NNTP newsgroup(s).