public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 3/7] fs/resctrl: Disallow the software controller when MBM counters are assignable
Date: Fri, 27 Mar 2026 09:14:34 -0700	[thread overview]
Message-ID: <aa8fe867-eae2-43ce-b824-92299428bd1f@intel.com> (raw)
In-Reply-To: <20260326172551.1553871-4-ben.horgan@arm.com>

Hi Ben,

On 3/26/26 10:25 AM, Ben Horgan wrote:
> The software controller requires that for each MBA control there is one MBM

Could you please elaborate the "for each MBA control" distinction here?

> counter per monitor group that is assigned to the event backing the
> software controller, as per mba_MBps_event. When mbm_event mode is in use,
> it is not guaranteed that any particular event will have an assigned
> counter.
> 
> Currently, only AMD systems support counter assignment, but the MBA delay
> is non-linear and so the software controller is never supported anyway. On
> MPAM systems, the MBA delay is linear and so the software controller could
> be supported. The MPAM driver, unless a need arises, will not support the
> 'default' mbm_assign_mode and will always use the 'mbm_event' mode for
> memory bandwidth monitoring.
> 
> Rather than develop a way to guarantee the counter assignment requirements
> needed by the software controller, take the pragmatic approach. Don't allow
> the software controller to be used at the same time as 'mbm_event' mode. As
> MPAM is the only relevant architecture and it will use 'mbm_event' mode
> whenever there are assignable MBM counters, for simplicity's sake, don't
> allow the software controller when the MBM counters are assignable.
> 
> Implement this by failing the mount if the user requests the software
> controller, the mba_MBps option, and the MBM counters are assignable.
> 
> Signed-off-by: Ben Horgan <ben.horgan@arm.com>
> ---
>  fs/resctrl/rdtgroup.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/resctrl/rdtgroup.c b/fs/resctrl/rdtgroup.c
> index fa5712db3778..7ef316b24a41 100644
> --- a/fs/resctrl/rdtgroup.c
> +++ b/fs/resctrl/rdtgroup.c
> @@ -2528,7 +2528,8 @@ static bool supports_mba_mbps(void)
>  
>  	return (resctrl_is_mbm_enabled() &&
>  		r->alloc_capable && is_mba_linear() &&
> -		r->ctrl_scope == rmbm->mon_scope);
> +		r->ctrl_scope == rmbm->mon_scope &&
> +		!rmbm->mon.mbm_cntr_assignable);
>  }
>  
>  /*
> @@ -2943,7 +2944,7 @@ static int rdt_parse_param(struct fs_context *fc, struct fs_parameter *param)
>  		ctx->enable_cdpl2 = true;
>  		return 0;
>  	case Opt_mba_mbps:
> -		msg = "mba_MBps requires MBM and linear scale MBA at L3 scope";
> +		msg = "mba_MBps requires dedicated MBM counters and linear scale MBA at L3 scope";

This looks like the original. I was expecting:
https://lore.kernel.org/lkml/cac437e2-8139-4833-9cbd-55d626062730@arm.com/ ?

>  		if (!supports_mba_mbps())
>  			return invalfc(fc, msg);
>  		ctx->enable_mba_mbps = true;

Reinette

  reply	other threads:[~2026-03-27 16:14 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 [this message]
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
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=aa8fe867-eae2-43ce-b824-92299428bd1f@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