mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jinjie Ruan <2118537295@qq.com>
To: babu.moger@amd.com, ben.horgan@arm.com, bp@alien8.de,
	catalin.marinas@arm.com, dave.hansen@linux.intel.com,
	Dave.Martin@arm.com, fenghuay@nvidia.com, gshan@redhat.com,
	hpa@zytor.com, james.morse@arm.com, jic23@kernel.org,
	mingo@redhat.com, reinette.chatre@intel.com,
	ruanjinjie@huawei.com, tan.shaopeng@fujitsu.com, tglx@kernel.org,
	tony.luck@intel.com, zengheng4@huawei.com, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 13/15] arm_mpam: Identify the non-aliasing controls
Date: Mon, 19 Oct 2026 16:27:57 +0800	[thread overview]
Message-ID: <tencent_B0F56D8514DC8CE331DC0A41DAC2842B6206@qq.com> (raw)
In-Reply-To: <tencent_57E8587BC53D6D65E212D1EAD6440A6AA605@qq.com>

This patch is part of the v10 series. For the main thread, see:

https://lore.kernel.org/all/tencent_28FE31D80A7A9AEEC43B22D0AD8894E30C06@qq.com/#t

在 2026/10/19 15:46, Jinjie Ruan 写道:
> From: Jinjie Ruan <ruanjinjie@huawei.com>
>
> A non-aliasing control can't be presented by writing the same value to
> several PARTIDs, because its value is additive. This is used later to
> decide whether a class's non-aliasing controls must be dropped before
> its PARTIDs can be used as separate monitoring groups.
>
> A control that aliases shares the resource, so writing the same value to
> each PARTID keeps its meaning. Several PARTIDs that map onto one
> internal PARTID are configured as one, so a class that implements
> narrowing does not have this problem.
>
> Cc: James Morse <james.morse@arm.com>
> Cc: Ben Horgan <ben.horgan@arm.com>
> Cc: Reinette Chatre <reinette.chatre@intel.com>
> Cc: Fenghua Yu <fenghuay@nvidia.com>
> Suggested-by: James Morse <james.morse@arm.com>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> ---
> v9->v10:
>   - Include mpam_feat_cmax_cassoc in the non-aliasing controls
> ---
>   drivers/resctrl/mpam_internal.h | 19 +++++++++++++++++++
>   1 file changed, 19 insertions(+)
>
> diff --git a/drivers/resctrl/mpam_internal.h b/drivers/resctrl/mpam_internal.h
> index 5a7590568a05..a4f2fdf7ac95 100644
> --- a/drivers/resctrl/mpam_internal.h
> +++ b/drivers/resctrl/mpam_internal.h
> @@ -221,6 +221,25 @@ struct mpam_props {
>   #define mpam_set_feature(_feat, x)	__set_bit(_feat, (x)->features)
>   #define mpam_clear_feature(_feat, x)	__clear_bit(_feat, (x)->features)
>   
> +/*
> + * A non-aliasing control (e.g. a cache capacity) can't be presented by
> + * writing the same value to several PARTIDs: its value is additive, two 50%
> + * values add up to 100%. An aliasing control (e.g. a cache portion bitmap)
> + * shares the resource, so the same value written to each PARTID keeps its
> + * meaning.
> + */
> +static inline bool
> +mpam_props_has_non_aliasing_controls(const struct mpam_props *props)
> +{
> +	return mpam_has_feature(mpam_feat_mbw_max, props) ||
> +	       mpam_has_feature(mpam_feat_mbw_min, props) ||
> +	       mpam_has_feature(mpam_feat_mbw_prop, props) ||
> +	       mpam_has_feature(mpam_feat_cmax_cmax, props) ||
> +	       mpam_has_feature(mpam_feat_cmax_cmin, props) ||
> +	       mpam_has_feature(mpam_feat_cmax_cassoc, props) ||
> +	       mpam_has_feature(mpam_feat_cmax_softlim, props);
> +}
> +
>   /* Workaround bits for msc->quirks */
>   enum mpam_device_quirks {
>   	T241_SCRUB_SHADOW_REGS,


      reply	other threads:[~2026-10-19  8:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19  7:46 Jinjie Ruan
2026-10-19  8:27 ` Jinjie Ruan [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=tencent_B0F56D8514DC8CE331DC0A41DAC2842B6206@qq.com \
    --to=2118537295@qq.com \
    --cc=Dave.Martin@arm.com \
    --cc=babu.moger@amd.com \
    --cc=ben.horgan@arm.com \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=fenghuay@nvidia.com \
    --cc=gshan@redhat.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=jic23@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=reinette.chatre@intel.com \
    --cc=ruanjinjie@huawei.com \
    --cc=tan.shaopeng@fujitsu.com \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=zengheng4@huawei.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®