From: Shaopeng Tan <tan.shaopeng@fujitsu.com>
To: fenghuay@nvidia.com, reinette.chatre@intel.com,
ben.horgan@arm.com, james.morse@arm.com, shuah@kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, tan.shaopeng@fujitsu.com
Subject: [RFC PATCH 5/5] kselftests/resctrl: Add support for CAT test on ARM
Date: Fri, 23 Jan 2026 13:40:31 +0900 [thread overview]
Message-ID: <20260123044034.141247-6-tan.shaopeng@fujitsu.com> (raw)
In-Reply-To: <20260123044034.141247-1-tan.shaopeng@fujitsu.com>
Currently, CAT test is limited to Intel architectures.
Add cache cleaning and enable result checking for Arm architectures.
Signed-off-by: Shaopeng Tan <tan.shaopeng@fujitsu.com>
---
tools/testing/selftests/resctrl/cat_test.c | 2 +-
tools/testing/selftests/resctrl/fill_buf.c | 4 ++++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/resctrl/cat_test.c b/tools/testing/selftests/resctrl/cat_test.c
index e1b30ab4cef5..58b1590695d1 100644
--- a/tools/testing/selftests/resctrl/cat_test.c
+++ b/tools/testing/selftests/resctrl/cat_test.c
@@ -113,7 +113,7 @@ static int check_results(struct resctrl_val_param *param, const char *cache_type
ret = show_results_info(sum_llc_perf_miss, bits,
alloc_size / 64,
MIN_DIFF_PERCENT_PER_BIT * (bits - 1),
- runs, get_vendor() == ARCH_INTEL,
+ runs, (get_vendor() == ARCH_INTEL || get_vendor() == ARCH_ARM),
&prev_avg_llc_val);
if (ret)
fail = 1;
diff --git a/tools/testing/selftests/resctrl/fill_buf.c b/tools/testing/selftests/resctrl/fill_buf.c
index 19a01a52dc1a..dbbf80d22f42 100644
--- a/tools/testing/selftests/resctrl/fill_buf.c
+++ b/tools/testing/selftests/resctrl/fill_buf.c
@@ -35,6 +35,10 @@ static void cl_flush(void *p)
#if defined(__i386) || defined(__x86_64)
asm volatile("clflush (%0)\n\t"
: : "r"(p) : "memory");
+#elif defined(__aarch64__)
+ __asm__ __volatile__("dc civac, %0\n\t"
+ : : "r" (p) : "memory");
+
#endif
}
--
2.47.3
next prev parent reply other threads:[~2026-01-23 4:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 4:40 [RFC PATCH 0/5] kselftest/resctrl: Enable CAT and NONCONT_CAT tests " Shaopeng Tan
2026-01-23 4:40 ` [RFC PATCH 1/5] kselftests/resctrl: Detect the ARM architecture Shaopeng Tan
2026-02-17 17:49 ` Reinette Chatre
2026-01-23 4:40 ` [RFC PATCH 2/5] kselftests/resctrl: enable noncont_cat for MPAM Shaopeng Tan
2026-02-17 17:52 ` Reinette Chatre
2026-01-23 4:40 ` [RFC PATCH 3/5] kselftests/resctrl: remove unnecessary exclude_idle Shaopeng Tan
2026-02-17 17:52 ` Reinette Chatre
2026-03-02 7:35 ` Shaopeng Tan (Fujitsu)
2026-01-23 4:40 ` [RFC PATCH 4/5] kselftests/resctrl: set shareable_mask to zero if all bits are shared between software and hardware Shaopeng Tan
2026-02-17 17:52 ` Reinette Chatre
2026-01-23 4:40 ` Shaopeng Tan [this message]
2026-01-27 20:47 ` [RFC PATCH 5/5] kselftests/resctrl: Add support for CAT test on ARM Ben Horgan
2026-01-27 20:40 ` [RFC PATCH 0/5] kselftest/resctrl: Enable CAT and NONCONT_CAT tests " Ben Horgan
2026-03-02 7:26 ` Shaopeng Tan (Fujitsu)
2026-03-03 17:10 ` Ben Horgan
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=20260123044034.141247-6-tan.shaopeng@fujitsu.com \
--to=tan.shaopeng@fujitsu.com \
--cc=ben.horgan@arm.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=reinette.chatre@intel.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®