linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	 Shuah Khan <shuah@kernel.org>
Cc: Nico Pache <npache@redhat.com>,
	linux-mm@kvack.org,  linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org,  Mark Brown <broonie@kernel.org>
Subject: [PATCH 0/2] selftests/mm: Allow execution on systems without huge pages
Date: Wed, 12 Feb 2025 17:44:24 +0000	[thread overview]
Message-ID: <20250212-kselftest-mm-no-hugepages-v1-0-44702f538522@kernel.org> (raw)

Currently the mm selftests refuse to run if we don't have huge page
support but there are plenty of tests that don't depend on this feature,
relax this requirement to allow coverage on relevant systems (eg, most
32 bit arm ones).

While doing this I noticed a bug with an existing check if we're running
THP tests, the fix overlaps with the above change so is sent as part of
a series.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (2):
      selftests/mm: Fix check for running THP tests
      selftests/mm: Allow tests to run with no huge pages support

 tools/testing/selftests/mm/run_vmtests.sh | 68 +++++++++++++++++++------------
 1 file changed, 43 insertions(+), 25 deletions(-)
---
base-commit: a64dcfb451e254085a7daee5fe51bf22959d52d3
change-id: 20250211-kselftest-mm-no-hugepages-ee5917a170eb

Best regards,
-- 
Mark Brown <broonie@kernel.org>



             reply	other threads:[~2025-02-12 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12 17:44 Mark Brown [this message]
2025-02-12 17:44 ` [PATCH 1/2] selftests/mm: Fix check for running THP tests Mark Brown
2025-02-17 21:32   ` Nico Pache
2025-02-12 17:44 ` [PATCH 2/2] selftests/mm: Allow tests to run with no huge pages support Mark Brown
2025-02-17 21:35   ` 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=20250212-kselftest-mm-no-hugepages-v1-0-44702f538522@kernel.org \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npache@redhat.com \
    --cc=shuah@kernel.org \
    /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