mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Cheng <icheng@nvidia.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: tony.luck@intel.com, x86@kernel.org, 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, fenghuay@nvidia.com, ltrager@nvidia.com,
	"Chen Yu" <yu.c.chen@intel.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v4 1/3] selftests/resctrl: Skip L3_CAT when no exclusive cache portion exists
Date: Tue, 18 Aug 2026 18:54:22 +0800	[thread overview]
Message-ID: <aoQ4hFvcOkU-44Ot@MWDK4CY14F> (raw)
In-Reply-To: <1eb20140-66e6-4e2e-b6e9-5172cfa29bbc@intel.com>

On Wed, Aug 12, 2026 at 10:22:03AM +0800, Reinette Chatre wrote:
> Hi Richard,
> 
> On 7/21/26 8:59 PM, Richard Cheng wrote:
> > L3_CAT measures cache isolation, which requires at least one cache bit
> > that is not shared with non-CPU agents, i.e. cbm_mask & ~shareable_bits
> > must be non-zero. On MPAM, shareable_bits == cbm_mask is a legitimate
> > state, so there are situations in which no bit can be reported as
> > exclusive.
> > 
> > Previously get_mask_no_shareable() was invoked inside cat_run_test()
> > and silently returned -1, which surfaced as a test failure on arm64
> > MPAM systems.
> > 
> > Implement cat_feature_check() to perform the same check at feature-check
> > time. It prints a diagnostic and returns false so the test case is
> > skipped instead of failing.
> > 
> > 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>
> > ---
> 
> This patch is unchanged from v3. My comments against v3 still apply:
> https://lore.kernel.org/lkml/5d76e776-82d3-4f02-8384-a890349ae96c@intel.com/
> 
> As noted there, this issue does not just impact aarch64. Could you please
> split this patch from this series? When it is ready I would like to make a
> request for its inclusion in the next cycle.
> 
> Thank you.
> 
> Reinette

Hi Reinette,

Thanks for your patient and review.

Just to confirm that I understand correctly before I send v5.

I plan to
1. Split this patch out of the arm64 series and send it as a standalone v5 patch
2. Keep the code change the same, and udpate the commit message to make it clear that having no exclusive cache portion causes
   L3_CAT to fail, and simplify the desciprtion as you suggested
3. Change the in-code comment to platform-neutral wording

About the editted commit message, I plan to write it like the following

"""
selftests/resctrl: Skip L3_CAT when no exclusive cache portion exists

L3_CAT measures cache isolation, which requires at least one cache bit
that is not shared with non-CPU agents, i.e. cbm_mask & ~shareable_bits
must be non-zero. Some platforms legitimately report every cache bit as
shareable, leaving no exclusive cache portion and causing L3_CAT to fail.

Skip, rather than fail, the L3_CAT test when the platform has no
exclusive cache portion that the test can use.
"""

Does this match what you imagined ?

Best regards,
Richard Cheng.


  reply	other threads:[~2026-08-18 10:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22  3:59 [PATCH v4 0/3] selftests/resctrl: Fix resctrl selftests issues on aarch64 Richard Cheng
2026-07-22  3:59 ` [PATCH v4 1/3] selftests/resctrl: Skip L3_CAT when no exclusive cache portion exists Richard Cheng
2026-08-12 17:22   ` Reinette Chatre
2026-08-18 10:54     ` Richard Cheng [this message]
2026-08-18 16:30       ` Reinette Chatre
2026-07-22  3:59 ` [PATCH v4 2/3] selftests/resctrl: Implement cl_flush() and sb() for aarch64 Richard Cheng
2026-08-12 17:25   ` Reinette Chatre
2026-10-01  9:22   ` Richard Cheng
2026-07-22  3:59 ` [PATCH v4 3/3] selftests/resctrl: Recognise aarch64 as a vendor for L3_NONCONT_CAT Richard Cheng
2026-10-01  9:23   ` Richard Cheng

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=aoQ4hFvcOkU-44Ot@MWDK4CY14F \
    --to=icheng@nvidia.com \
    --cc=Dave.Martin@arm.com \
    --cc=babu.moger@amd.com \
    --cc=fenghuay@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=reinette.chatre@intel.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

all inboxes | Powered by JetHome®