From: David Hildenbrand <david@redhat.com>
To: Li Wang <liwang@redhat.com>,
akpm@linux-foundation.org, lorenzo.stoakes@oracle.com,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: Aruna Ramakrishna <aruna.ramakrishna@oracle.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Joey Gouly <joey.gouly@arm.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Keith Lucas <keith.lucas@oracle.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v2] ksm_tests: Skip hugepage test when Transparent Hugepages are disabled
Date: Tue, 24 Jun 2025 10:25:23 +0200 [thread overview]
Message-ID: <4b69c14f-1001-48a0-9c83-6d2284b5a04a@redhat.com> (raw)
In-Reply-To: <20250624032748.393836-1-liwang@redhat.com>
On 24.06.25 05:27, Li Wang wrote:
> Some systems (e.g. minimal or real-time kernels) may not enable
> Transparent Hugepages (THP), causing MADV_HUGEPAGE to return EINVAL.
> This patch introduces a runtime check using the existing THP sysfs
> interface and skips the hugepage merging test (`-H`) when THP is
> not available.
>
> To avoid those failures:
But we deliberately have in tools/testing/selftests/mm/config:
CONFIG_TRANSPARENT_HUGEPAGE=y
So isn't this rather a test setup issue? Meaning, the environment is
not well prepared.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-06-24 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 0:48 [PATCH] " Li Wang
2025-06-23 9:01 ` Lorenzo Stoakes
2025-06-24 3:27 ` [PATCH v2] " Li Wang
2025-06-24 8:25 ` David Hildenbrand [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=4b69c14f-1001-48a0-9c83-6d2284b5a04a@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aruna.ramakrishna@oracle.com \
--cc=bagasdotme@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=hannes@cmpxchg.org \
--cc=joey.gouly@arm.com \
--cc=keith.lucas@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwang@redhat.com \
--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
all inboxes | Powered by JetHome®