linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	David Hildenbrand <david@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Shuah Khan <shuah@kernel.org>,
	Mario Casquero <mcasquer@redhat.com>,
	Breno Leitao <leitao@debian.org>
Subject: [PATCH v1 0/2] selftests/mm: hugetlb_fault_after_madv improvements
Date: Thu, 26 Sep 2024 17:20:42 +0200	[thread overview]
Message-ID: <20240926152044.2205129-1-david@redhat.com> (raw)

Mario brought to my attention that the hugetlb_fault_after_madv test
is currently always skipped on s390x.

Let's adjust the test to be independent of the default hugetlb page size
and while at it, also improve the test output.

Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Shuah Khan <shuah@kernel.org>
Cc: Mario Casquero <mcasquer@redhat.com>
Cc: Breno Leitao <leitao@debian.org>

David Hildenbrand (2):
  selftests/mm: hugetlb_fault_after_madv: use default hguetlb page size
  selftests/mm: hugetlb_fault_after_madv: improve test output

 .../selftests/mm/hugetlb_fault_after_madv.c   | 48 ++++++++++++++++---
 1 file changed, 42 insertions(+), 6 deletions(-)

-- 
2.46.1



             reply	other threads:[~2024-09-26 15:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 15:20 David Hildenbrand [this message]
2024-09-26 15:20 ` [PATCH v1 1/2] selftests/mm: hugetlb_fault_after_madv: use default hguetlb page size David Hildenbrand
2024-09-26 15:22   ` David Hildenbrand
2024-09-26 16:03   ` Shuah Khan
2024-09-30 10:01   ` Breno Leitao
2024-09-26 15:20 ` [PATCH v1 2/2] selftests/mm: hugetlb_fault_after_madv: improve test output David Hildenbrand
2024-09-30 10:05   ` Breno Leitao
2024-09-30 10:55     ` David Hildenbrand
2024-10-01 10:31 ` [PATCH v1 0/2] selftests/mm: hugetlb_fault_after_madv improvements Mario Casquero

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=20240926152044.2205129-1-david@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mcasquer@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