From: Richard Cheng <icheng@nvidia.com>
To: tony.luck@intel.co, reinette.chatre@intel.com, shuah@kernel.org
Cc: Dave.Martin@arm.com, james.morse@arm.com, babu.moger@amd.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
fenghuay@nvidia.com, newtonl@nvidia.com, kristinc@nvidia.com,
kaihengf@nvidia.com, kobak@nvidia.com, sdonthineni@nvidia.com,
Richard Cheng <icheng@nvidia.com>
Subject: [PATCH 0/3] selftests/resctrl: increase L3 cache test coverage
Date: Mon, 8 Jun 2026 19:06:38 +0800 [thread overview]
Message-ID: <20260608110641.44457-1-icheng@nvidia.com> (raw)
The resctrl selftests check L3 cache isolation (L3_CAT) and occupancy
accuracy (CMT), but some basic L3 behaviour is untested: that an allocation
actually bounds a group's cache use, that invalid CBMs are rejected, and
that info/L3/bit_usage reports allocations correctly.
Add three self-contained tests for these. Each gates on the feature
it needs, so it runs wherever that feature exists and skips otherwise.
They were exercised on an arm64 MPAM platform.
Richard Cheng (3):
selftests/resctrl: Add L3_CAT_OCCUP test to verify CAT bounds
occupancy
selftests/resctrl: Add L3_CAT_VALIDATE to check invalid CBMs
selftests/resctrl: Add L3_BIT_USAGE to check bit_usage tracks
allocation
tools/testing/selftests/resctrl/cat_test.c | 433 ++++++++++++++++++
tools/testing/selftests/resctrl/cmt_test.c | 3 -
tools/testing/selftests/resctrl/resctrl.h | 6 +
.../testing/selftests/resctrl/resctrl_tests.c | 3 +
4 files changed, 442 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2026-06-08 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 11:06 Richard Cheng [this message]
2026-06-08 11:06 ` [PATCH 1/3] selftests/resctrl: Add L3_CAT_OCCUP test to verify CAT bounds occupancy Richard Cheng
2026-08-05 22:18 ` Reinette Chatre
2026-08-10 4:22 ` Richard Cheng
2026-06-08 11:06 ` [PATCH 2/3] selftests/resctrl: Add L3_CAT_VALIDATE to check invalid CBMs Richard Cheng
2026-08-05 22:35 ` Reinette Chatre
2026-06-08 11:06 ` [PATCH 3/3] selftests/resctrl: Add L3_BIT_USAGE to check bit_usage tracks allocation Richard Cheng
2026-08-05 22:37 ` Reinette Chatre
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=20260608110641.44457-1-icheng@nvidia.com \
--to=icheng@nvidia.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=kaihengf@nvidia.com \
--cc=kobak@nvidia.com \
--cc=kristinc@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=newtonl@nvidia.com \
--cc=reinette.chatre@intel.com \
--cc=sdonthineni@nvidia.com \
--cc=shuah@kernel.org \
--cc=tony.luck@intel.co \
/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®