mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: Ben Horgan <ben.horgan@arm.com>, <james.morse@arm.com>,
	<Dave.Martin@arm.com>, <fenghuay@nvidia.com>
Cc: <tony.luck@intel.com>, <yu.c.chen@intel.com>,
	<babu.moger@amd.com>, <fustini@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <patches@lists.linux.dev>
Subject: Re: [RFC PATCH v2 10/10] arm_mpam: resctrl: Update the comment on monitoring domain setup
Date: Tue, 3 Nov 2026 16:51:12 -0800	[thread overview]
Message-ID: <56d16560-51ca-4a73-a376-b897bb77e612@intel.com> (raw)
In-Reply-To: <c7f180d1-f81e-495e-91be-b76a4c4df21d@arm.com>

Hi Ben,

On 11/3/26 8:27 AM, Ben Horgan wrote:
> On 19/10/2026 23:07, Reinette Chatre wrote:
>> The comment in mpam_resctrl_setup_mon_domain() explains that the L3
>> component IDs need to be used for a monitoring domain because there may
>> be no control component for the L3. It also describes searching each
>> event's class for a component with overlapping CPUs.
>>
>> Neither matches the code. The monitoring domain has its own structure
>> and is set up independently of the control domain, so whether a control
>> component exists has no bearing on it. Each event's class must have a
>> component that contains the CPU, and all components of the domain must
>> cover the same CPUs, which is stricter than overlapping.
>>
>> Rewrite the comment to say where the domain's ID comes from and what is
>> required of the components that back the domain's events.
>>
>> No functional change.
>>
>> Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
>> ---
>> Note to maintainers: This comment update is kept as a separate patch to
>> make it easy to review. It can be folded into "arm_mpam: resctrl: Give
>> the monitoring domain its own structure" and "arm_mpam: resctrl: Require
>> monitoring components to cover the same CPUs" if preferred.
> 
> Yes, I think squashing those 3 patches together would be good.
> 
Done. Since "arm_mpam: resctrl: Require monitoring components to cover the same CPUs"
depends on "arm_mpam: resctrl: Require a component for each monitoring event" for
which you provided RB separately I re-ordered "arm_mpam: resctrl: Require a component
for each monitoring event" to be before "arm_mpam: resctrl: Give the monitoring domain
its own structure" to support this squash.

At this point the next version of this series looks like:
	arm_mpam: resctrl: Add a helper to find the component counting an event
	arm_mpam: resctrl: Use find_component() when allocating a domain
	arm_mpam: resctrl: Rename ctrl_comp in mpam_resctrl_alloc_domain()
	arm_mpam: resctrl: Do not fail CPU online when domain setup fails
	arm_mpam: resctrl: Split control and monitoring domain setup into helpers
	arm_mpam: resctrl: Require a component for each monitoring event
	arm_mpam: resctrl: Give the monitoring domain its own structure
	arm_mpam: resctrl: Rename struct mpam_resctrl_dom to mpam_resctrl_ctrl_dom

Thank you very much for your review. Unless something shows up I plan to send the
next version next week.

Reinette

  reply	other threads:[~2026-11-04  0:51 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 22:07 [RFC PATCH v2 00/10] arm_mpam: resctrl: Separate MPAM domains Reinette Chatre
2026-10-19 22:07 ` [RFC PATCH v2 01/10] arm_mpam: resctrl: Use find_component() when allocating a domain Reinette Chatre
2026-10-23  8:07   ` Jinjie Ruan
2026-10-23  8:07   ` Jinjie Ruan
2026-10-23 14:52     ` Reinette Chatre
2026-11-03 15:01   ` Ben Horgan
2026-11-03 17:48     ` Ben Horgan
2026-11-03 18:13       ` Reinette Chatre
2026-11-03 18:44         ` Ben Horgan
2026-10-19 22:07 ` [RFC PATCH v2 02/10] arm_mpam: resctrl: Rename ctrl_comp in mpam_resctrl_alloc_domain() Reinette Chatre
2026-10-23  8:08   ` Jinjie Ruan
2026-10-23 14:53     ` Reinette Chatre
2026-11-03 15:14   ` Ben Horgan
2026-10-19 22:07 ` [RFC PATCH v2 03/10] arm_mpam: resctrl: Do not fail CPU online when domain setup fails Reinette Chatre
2026-10-26  9:51   ` Jinjie Ruan
2026-11-03 15:38   ` Ben Horgan
2026-11-04  0:50     ` Reinette Chatre
2026-10-19 22:07 ` [RFC PATCH v2 04/10] arm_mpam: resctrl: Split control and monitoring domain setup into helpers Reinette Chatre
2026-10-26 11:49   ` Jinjie Ruan
2026-11-02  5:41   ` Shaopeng Tan (Fujitsu)
2026-11-02 17:20     ` Reinette Chatre
2026-11-03 16:00   ` Ben Horgan
2026-10-19 22:07 ` [RFC PATCH v2 05/10] arm_mpam: resctrl: Give the monitoring domain its own structure Reinette Chatre
2026-10-26 12:14   ` Jinjie Ruan
2026-10-26 16:55     ` Reinette Chatre
2026-10-27  1:12       ` Jinjie Ruan
2026-10-19 22:07 ` [RFC PATCH v2 06/10] arm_mpam: resctrl: Rename struct mpam_resctrl_dom to mpam_resctrl_ctrl_dom Reinette Chatre
2026-10-26 12:40   ` Jinjie Ruan
2026-10-19 22:07 ` [RFC PATCH v2 07/10] arm_mpam: resctrl: Warn when no monitoring component is found for a CPU Reinette Chatre
2026-10-26 13:14   ` Jinjie Ruan
2026-10-19 22:07 ` [RFC PATCH v2 08/10] arm_mpam: resctrl: Require a component for each monitoring event Reinette Chatre
2026-11-03 16:38   ` Ben Horgan
2026-10-19 22:07 ` [RFC PATCH v2 09/10] arm_mpam: resctrl: Require monitoring components to cover the same CPUs Reinette Chatre
2026-10-19 22:07 ` [RFC PATCH v2 10/10] arm_mpam: resctrl: Update the comment on monitoring domain setup Reinette Chatre
2026-11-03 16:27   ` Ben Horgan
2026-11-04  0:51     ` Reinette Chatre [this message]
2026-10-22 10:45 ` [RFC PATCH v2 00/10] arm_mpam: resctrl: Separate MPAM domains Ben Horgan
2026-10-22 15:43   ` Reinette Chatre
2026-10-27  3:42 ` Jinjie Ruan
2026-10-27 14:23   ` 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=56d16560-51ca-4a73-a376-b897bb77e612@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=Dave.Martin@arm.com \
    --cc=babu.moger@amd.com \
    --cc=ben.horgan@arm.com \
    --cc=fenghuay@nvidia.com \
    --cc=fustini@kernel.org \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=tony.luck@intel.com \
    --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®