From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Kevin Brodsky <kevin.brodsky@arm.com>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Dev Jain <dev.jain@arm.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Mark Brown <broonie@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v3 6/9] selftests/mm: introduce helper to read every page
Date: Thu, 22 Jan 2026 23:20:37 +0100 [thread overview]
Message-ID: <a4c83b16-3307-497d-9690-0e31672f3202@kernel.org> (raw)
In-Reply-To: <20260122170224.4056513-7-kevin.brodsky@arm.com>
On 1/22/26 18:02, Kevin Brodsky wrote:
> FORCE_READ(*addr) ensures that the compiler will emit a load from
> addr. Several tests need to trigger such a load for a range of
> pages, ensuring that every page is faulted in, if it wasn't already.
>
> Introduce a new helper force_read_pages() that does exactly that and
> replace existing loops with a call to it.
>
> The step size (regular/huge page size) is preserved for all loops,
> except in split_huge_page_test. Reading every byte is unnecessary;
> we now read every huge page, matching the following call to
> check_huge_file().
>
> Reviewed-by: Dev Jain <dev.jain@arm.com>
> Signed-off-by: Kevin Brodsky <kevin.brodsky@arm.com>
> ---
> tools/testing/selftests/mm/hugetlb-madvise.c | 9 +--------
> tools/testing/selftests/mm/pfnmap.c | 9 +++------
> tools/testing/selftests/mm/split_huge_page_test.c | 6 +-----
> tools/testing/selftests/mm/vm_util.h | 7 +++++++
> 4 files changed, 12 insertions(+), 19 deletions(-)
>
> diff --git a/tools/testing/selftests/mm/hugetlb-madvise.c b/tools/testing/selftests/mm/hugetlb-madvise.c
> index 05d9d2805ae4..5b12041fa310 100644
> --- a/tools/testing/selftests/mm/hugetlb-madvise.c
> +++ b/tools/testing/selftests/mm/hugetlb-madvise.c
> @@ -47,14 +47,7 @@ void write_fault_pages(void *addr, unsigned long nr_pages)
>
> void read_fault_pages(void *addr, unsigned long nr_pages)
> {
> - unsigned long i;
> -
> - for (i = 0; i < nr_pages; i++) {
> - unsigned long *addr2 =
> - ((unsigned long *)(addr + (i * huge_page_size)));
> - /* Prevent the compiler from optimizing out the entire loop: */
> - FORCE_READ(*addr2);
> - }
> + force_read_pages(addr, nr_pages, huge_page_size);
> }
Likely we could get rid of read_fault_pages() completely and simply let
the callers call force_read_pages() now?
Acked-by: David Hildenbrand (Red Hat) <david@kernel.org>
--
Cheers
David
next prev parent reply other threads:[~2026-01-22 22:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 17:02 [PATCH v3 0/9] Various mm kselftests improvements/fixes Kevin Brodsky
2026-01-22 17:02 ` [PATCH v3 1/9] selftests/mm: default KDIR to build directory Kevin Brodsky
2026-01-22 17:02 ` [PATCH v3 2/9] selftests/mm: remove flaky header check Kevin Brodsky
2026-01-22 17:02 ` [PATCH v3 3/9] selftests/mm: pass down full CC and CFLAGS to check_config.sh Kevin Brodsky
2026-01-22 17:02 ` [PATCH v3 4/9] selftests/mm: fix usage of FORCE_READ() in cow tests Kevin Brodsky
2026-01-22 17:02 ` [PATCH v3 5/9] selftests/mm: check that FORCE_READ() succeeded Kevin Brodsky
2026-01-22 17:36 ` Usama Anjum
2026-01-23 8:20 ` Kevin Brodsky
2026-01-22 22:18 ` David Hildenbrand (Red Hat)
2026-01-23 8:17 ` Kevin Brodsky
2026-01-22 17:02 ` [PATCH v3 6/9] selftests/mm: introduce helper to read every page Kevin Brodsky
2026-01-22 17:39 ` Muhammad Usama Anjum
2026-01-22 22:20 ` David Hildenbrand (Red Hat) [this message]
2026-01-23 8:25 ` Kevin Brodsky
2026-01-22 17:02 ` [PATCH v3 7/9] selftests/mm: fix faulting-in code in pagemap_ioctl test Kevin Brodsky
2026-01-22 17:43 ` Muhammad Usama Anjum
2026-01-22 17:02 ` [PATCH v3 8/9] selftests/mm: fix exit code in pagemap_ioctl Kevin Brodsky
2026-01-22 17:02 ` [PATCH v3 9/9] selftests/mm: report SKIP in pfnmap if a check fails Kevin Brodsky
2026-01-22 22:23 ` David Hildenbrand (Red Hat)
2026-01-22 18:25 ` [PATCH v3 0/9] Various mm kselftests improvements/fixes Andrew Morton
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=a4c83b16-3307-497d-9690-0e31672f3202@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=dev.jain@arm.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=ryan.roberts@arm.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