From: Reinette Chatre <reinette.chatre@intel.com>
To: Richard Cheng <icheng@nvidia.com>, <tony.luck@intel.com>,
<x86@kernel.org>, <fenghuay@nvidia.com>
Cc: <Dave.Martin@arm.com>, <james.morse@arm.com>,
<babu.moger@amd.com>, <shuah@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<newtonl@nvidia.com>, <kristinc@nvidia.com>, <kobak@nvidia.com>,
<kaihengf@nvidia.com>, <ltrager@nvidia.com>,
<yu.c.chen@intel.com>, <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v5] selftests/resctrl: Skip L3_CAT when no exclusive cache portion exists
Date: Fri, 21 Aug 2026 14:23:11 -0700 [thread overview]
Message-ID: <0f77e477-936a-4208-b752-6b07b0feca08@intel.com> (raw)
In-Reply-To: <20260821003908.12977-1-icheng@nvidia.com>
Hi Richard,
On 8/20/26 5:39 PM, Richard Cheng wrote:
> L3_CAT requires an exclusive cache portion to test cache allocation.
> This means that the cache portion used by the test can't overlap with
> cache portions into which other agents may allocate.
>
> Some platforms legitimately report every cache portion as shareable,
> leaving no exclusive cache portion for the test and causing L3_CAT to
> fail.
>
> Skip the L3_CAT when the platform has no exclusive cache portion that
> the test can use.
>
> Tested-by: Chen Yu <yu.c.chen@intel.com>
> Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> Signed-off-by: Richard Cheng <icheng@nvidia.com>
> ---
Thank you very much.
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Reinette
prev parent reply other threads:[~2026-08-21 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 0:39 [PATCH v5] selftests/resctrl: Skip L3_CAT when no exclusive cache portion exists Richard Cheng
2026-08-21 21:23 ` Reinette Chatre [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=0f77e477-936a-4208-b752-6b07b0feca08@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=fenghuay@nvidia.com \
--cc=icheng@nvidia.com \
--cc=ilpo.jarvinen@linux.intel.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=ltrager@nvidia.com \
--cc=newtonl@nvidia.com \
--cc=shuah@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.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