From: Muhammad Usama Anjum <usama.anjum@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: usama.anjum@arm.com, Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Shuah Khan <shuah@kernel.org>,
Andrey Konovalov <andreyknvl@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
Yeoreum Yun <yeoreum.yun@arm.com>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)"
<linux-arm-kernel@lists.infradead.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH 2/4] selftest/arm64: Treat KSM merge_across_nodes as optional
Date: Fri, 21 Aug 2026 11:57:43 +0100 [thread overview]
Message-ID: <a003db17-5f80-4e90-a366-f6b72e8a2533@arm.com> (raw)
In-Reply-To: <0ae60fab-49e3-4a8c-a007-a6439ae10991@sirena.org.uk>
On 20/08/2026 5:09 pm, Mark Brown wrote:
> On Thu, Aug 20, 2026 at 04:33:24PM +0100, Muhammad Usama Anjum wrote:
>> The MTE KSM test unconditionally saves, enables and restores the
>> merge_across_nodes sysfs attribute. The kernel only creates this
>> attribute when CONFIG_NUMA=y. A non-NUMA kernel consequently prints the
>> following message three times even though all KSM subtests pass:
>
>> static void mte_ksm_setup(void)
>> {
>> - ksm_sysfs[0] = read_sysfs(PATH_KSM "merge_across_nodes");
>> - write_sysfs(PATH_KSM "merge_across_nodes", 1);
>> + has_merge_across_nodes = !access(PATH_KSM "merge_across_nodes", F_OK);
>
> Don't we need the file to be readable and writable, not just extant?
Correct, I'll fix it.
> Looking quickly at the test I'm actually not spotting where it checks
> that it's running as root which I think it needs in general.
I'll add check for that as well.
--
Thanks,
Usama
next prev parent reply other threads:[~2026-08-21 10:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 15:33 [PATCH 0/4] selftest/arm64: Fix MTE test setup and TAP reporting Muhammad Usama Anjum
2026-08-20 15:33 ` [PATCH 1/4] selftest/arm64: Print TAP header Muhammad Usama Anjum
2026-08-20 15:43 ` Mark Brown
2026-08-20 15:33 ` [PATCH 2/4] selftest/arm64: Treat KSM merge_across_nodes as optional Muhammad Usama Anjum
2026-08-20 16:09 ` Mark Brown
2026-08-21 10:57 ` Muhammad Usama Anjum [this message]
2026-08-20 15:33 ` [PATCH 3/4] selftest/arm64: Fix MTE prctl TAP plan Muhammad Usama Anjum
2026-08-20 16:14 ` Mark Brown
2026-08-20 15:33 ` [PATCH 4/4] selftest/arm64: Add MTE test config fragment Muhammad Usama Anjum
2026-08-20 15:38 ` Mark Brown
2026-08-20 15:42 ` Muhammad Usama Anjum
2026-08-20 16:42 ` Mark Brown
2026-08-21 8:01 ` Muhammad Usama Anjum
2026-08-21 8:55 ` Catalin Marinas
2026-08-21 10:43 ` Muhammad Usama Anjum
2026-08-21 11:38 ` Mark Brown
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=a003db17-5f80-4e90-a366-f6b72e8a2533@arm.com \
--to=usama.anjum@arm.com \
--cc=akpm@linux-foundation.org \
--cc=amit.kachhap@arm.com \
--cc=andreyknvl@gmail.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=shuah@kernel.org \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.org \
--cc=yeoreum.yun@arm.com \
/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®