mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sarthak Sharma <sarthak.sharma@arm.com>
To: Jaeyeon Lee <jaeyeon.lee.dev@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Shuah Khan <shuah@kernel.org>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
	"Liam R . Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: hugetlb-read-hwpoison: add setup of HugeTLB pages
Date: Mon, 5 Oct 2026 11:36:43 +0530	[thread overview]
Message-ID: <48012a21-dc2b-4445-a71c-0d517845d998@arm.com> (raw)
In-Reply-To: <20261004205458.119608-1-jaeyeon.lee.dev@gmail.com>



On 10/5/26 2:24 AM, Jaeyeon Lee wrote:
> Every test is expected to reserve the HugeTLB pages it needs.
> hugetlb-read-hwpoison was not converted, so on a system without
> pre-reserved huge pages the MAP_POPULATE mmap() fails with ENOMEM and
> every test case is skipped.
> 
> Reserve the pages with hugetlb_setup_default(). Each chunk size runs two
> HWPOISON tests and a poisoned huge page can't be reused, so reserve two
> pages per chunk size. The pool size is restored on exit. The poisoned
> pages remain allocated until reboot.
> 
> With the patch, all 12 cases pass on a system with no huge pages
> reserved (tested on Fedora, x86_64, CONFIG_MEMORY_FAILURE=y).
> 
> Assisted-by: LLM
> Signed-off-by: Jaeyeon Lee <jaeyeon.lee.dev@gmail.com>
> ---

Looks good to me. Before the patch, all 12 test cases were skipping with
ENOMEM. After the patch, all test cases passed.

Tested-by: Sarthak Sharma <sarthak.sharma@arm.com>
Reviewed-by: Sarthak Sharma <sarthak.sharma@arm.com>

>  tools/testing/selftests/mm/hugetlb-read-hwpoison.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/tools/testing/selftests/mm/hugetlb-read-hwpoison.c b/tools/testing/selftests/mm/hugetlb-read-hwpoison.c
> index 70b24e3660c4..31748a24448f 100644
> --- a/tools/testing/selftests/mm/hugetlb-read-hwpoison.c
> +++ b/tools/testing/selftests/mm/hugetlb-read-hwpoison.c
> @@ -13,6 +13,7 @@
>  #include <signal.h>
>  
>  #include "kselftest.h"
> +#include "vm_util.h"
>  
>  #define MAX_WRITE_READ_CHUNK_SIZE (getpagesize() * 16)
>  #define MAX(a, b) (((a) > (b)) ? (a) : (b))
> @@ -281,6 +282,13 @@ int main(void)
>  	size_t i;
>  
>  	ksft_print_header();
> +
> +	if (!hugetlb_available())
> +		ksft_exit_skip("HugeTLB is not available\n");
> +
> +	if (!hugetlb_setup_default(ARRAY_SIZE(wr_chunk_sizes) * 2))
> +		ksft_exit_skip("Not enough free huge pages\n");
> +
>  	ksft_set_plan(ARRAY_SIZE(wr_chunk_sizes) * 3);
>  
>  	signal(SIGBUS, sigbus_handler);


      reply	other threads:[~2026-10-05  6:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 20:54 Jaeyeon Lee
2026-10-05  6:06 ` Sarthak Sharma [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=48012a21-dc2b-4445-a71c-0d517845d998@arm.com \
    --to=sarthak.sharma@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=jaeyeon.lee.dev@gmail.com \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=shuah@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@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

all inboxes | Powered by JetHome®