From: Reinette Chatre <reinette.chatre@intel.com>
To: Ben Horgan <ben.horgan@arm.com>, <linux-kernel@vger.kernel.org>
Cc: <tony.luck@intel.com>, <Dave.Martin@arm.com>,
<james.morse@arm.com>, <babu.moger@amd.com>, <tglx@kernel.org>,
<mingo@redhat.com>, <bp@alien8.de>, <dave.hansen@linux.intel.com>,
<x86@kernel.org>, <hpa@zytor.com>, <fenghuay@nvidia.com>,
<tan.shaopeng@fujitsu.com>
Subject: Re: [PATCH v4 4/7] x86,fs/resctrl: Add monitor property 'mbm_cntr_assign_fixed'
Date: Fri, 27 Mar 2026 09:15:22 -0700 [thread overview]
Message-ID: <8dc03230-4247-4de2-a253-59a1706eeb99@intel.com> (raw)
In-Reply-To: <20260326172551.1553871-5-ben.horgan@arm.com>
Hi Ben,
Now that the patch no longer touches x86 code the subject prefix can just
be "fs/resctrl:".
On 3/26/26 10:25 AM, Ben Horgan wrote:
> Commit
>
> 3b497c3f4f04 ("fs/resctrl: Introduce the interface to display monitoring modes")
>
> introduced CONFIG_RESCTRL_ASSIGN_FIXED but left adding the Kconfig
> entry until it was necessary. The counter assignment mode is fixed in
> MPAM, even when there are assignable counters, and so addressing this
> is needed to support MPAM.
>
> To avoid the burden of another Kconfig entry, replace
> CONFIG_RESCTRL_ASSIGN_FIXED with a new property in 'struct resctrl_mon',
> 'mbm_cntr_assign_fixed'.
Can append "to be set by architecture."
>
> To enable better user reporting check the new property in
> resctrl_mbm_assign_mode_write().
How about:
Do not request the architecture to change the counter assignment
mode if it does not support doing so. Provide insight to user space
about why such a request fails.
>
> Signed-off-by: Ben Horgan <ben.horgan@arm.com>
> ---
> Changes since v2:
> Change to a resctrl_mon property rather than a arch hook
> Update the commit message to mention the property
> ---
> fs/resctrl/monitor.c | 8 +++++++-
> include/linux/resctrl.h | 2 ++
> 2 files changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/fs/resctrl/monitor.c b/fs/resctrl/monitor.c
> index 8fec3dea33c3..6afa2af26ff7 100644
> --- a/fs/resctrl/monitor.c
> +++ b/fs/resctrl/monitor.c
> @@ -1454,7 +1454,7 @@ int resctrl_mbm_assign_mode_show(struct kernfs_open_file *of,
> else
> seq_puts(s, "[default]\n");
>
> - if (!IS_ENABLED(CONFIG_RESCTRL_ASSIGN_FIXED)) {
> + if (!r->mon.mbm_cntr_assign_fixed) {
> if (enabled)
> seq_puts(s, "default\n");
> else
> @@ -1505,6 +1505,12 @@ ssize_t resctrl_mbm_assign_mode_write(struct kernfs_open_file *of, char *buf,
> }
>
> if (enable != resctrl_arch_mbm_cntr_assign_enabled(r)) {
> + if (r->mon.mbm_cntr_assign_fixed) {
> + ret = -EINVAL;
> + rdt_last_cmd_puts("Counter assignment mode is not configurable\n");
> + goto out_unlock;
> + }
> +
> ret = resctrl_arch_mbm_cntr_assign_set(r, enable);
> if (ret)
> goto out_unlock;
> diff --git a/include/linux/resctrl.h b/include/linux/resctrl.h
> index 06e8c72e8660..a986daf5f2ef 100644
> --- a/include/linux/resctrl.h
> +++ b/include/linux/resctrl.h
> @@ -294,6 +294,7 @@ enum resctrl_schema_fmt {
> * @mbm_assign_on_mkdir: True if counters should automatically be assigned to MBM
> * events of monitor groups created via mkdir.
> * @mbm_cntr_configurable: True if assignable counters are configurable.
> + * @mbm_cntr_assign_fixed: True if the counter assignment mode is fix.
"is fix" -> "is fixed"?
> */
> struct resctrl_mon {
> u32 num_rmid;
> @@ -302,6 +303,7 @@ struct resctrl_mon {
> bool mbm_cntr_assignable;
> bool mbm_assign_on_mkdir;
> bool mbm_cntr_configurable;
> + bool mbm_cntr_assign_fixed;
> };
>
> /**
Reinette
next prev parent reply other threads:[~2026-03-27 16:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 17:25 [PATCH v4 0/7] x86,fs/resctrl: Pave the way for MPAM counter assignment Ben Horgan
2026-03-26 17:25 ` [PATCH v4 1/7] fs/resctrl: Tidy up the error path in resctrl_mkdir_event_configs() Ben Horgan
2026-03-27 16:06 ` Reinette Chatre
2026-03-26 17:25 ` [PATCH v4 2/7] x86,fs/resctrl: Make 'event_filter' files read only if they're not configurable Ben Horgan
2026-03-27 16:13 ` Reinette Chatre
2026-03-27 17:15 ` Ben Horgan
2026-03-26 17:25 ` [PATCH v4 3/7] fs/resctrl: Disallow the software controller when MBM counters are assignable Ben Horgan
2026-03-27 16:14 ` Reinette Chatre
2026-03-27 17:24 ` Ben Horgan
2026-03-26 17:25 ` [PATCH v4 4/7] x86,fs/resctrl: Add monitor property 'mbm_cntr_assign_fixed' Ben Horgan
2026-03-27 16:15 ` Reinette Chatre [this message]
2026-03-26 17:25 ` [PATCH v4 5/7] fs/resctrl: Continue counter allocation after failure Ben Horgan
2026-03-27 16:21 ` Reinette Chatre
2026-04-14 14:42 ` Ben Horgan
2026-04-15 14:27 ` Reinette Chatre
2026-04-15 14:46 ` Ben Horgan
2026-04-15 15:38 ` Reinette Chatre
2026-04-15 16:31 ` Ben Horgan
2026-04-15 17:28 ` Reinette Chatre
2026-04-16 8:32 ` Ben Horgan
2026-03-26 17:25 ` [PATCH v4 6/7] fs/resctrl: Document that automatic counter assignment is best effort Ben Horgan
2026-03-27 16:24 ` Reinette Chatre
2026-04-14 14:55 ` Ben Horgan
2026-03-26 17:25 ` [PATCH v4 7/7] fs/resctrl: Document tasks file behaviour for task id 0 and idle tasks Ben Horgan
2026-03-27 16:40 ` 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=8dc03230-4247-4de2-a253-59a1706eeb99@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghuay@nvidia.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tan.shaopeng@fujitsu.com \
--cc=tglx@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@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