From: Reinette Chatre <reinette.chatre@intel.com>
To: Chen Yu <chen.yu@linux.dev>
Cc: Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
"Thomas Gleixner" <tglx@linutronix.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Peter Newman <peternewman@google.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dave Martin <Dave.Martin@arm.com>,
Ben Horgan <ben.horgan@arm.com>,
James Morse <james.morse@arm.com>,
Babu Moger <babu.moger@amd.com>,
Drew Fustini <fustini@kernel.org>,
Fenghua Yu <fenghuay@nvidia.com>, Chen Yu <yu.c.chen@intel.com>
Subject: Re: [RFC v2] arm,x86,fs/resctrl: Generic schema description Proof of Concept
Date: Thu, 13 Aug 2026 08:19:38 -0700 [thread overview]
Message-ID: <5e07c57d-b971-4c7a-bdfe-3b9c6f299b8b@intel.com> (raw)
In-Reply-To: <an3NrBncH_hC5cih@three-body>
Hi Chenyu,
On 8/13/26 6:59 AM, Chen Yu wrote:
> On Tue, Aug 11, 2026 at 11:49:12AM +0800, Chen, Yu C wrote:
>>> I find "region-aware controllers at the same level as legacy controller" together with
>>> "per controller enable/disable" conflicting since it creates impression that user space can
>>> enable/disable the controllers independently while there is a required dependency among the
>>> different controllers based on whether hardware has region-aware MBA enabled or not. Even
>>> here there would be a requirement to communicate to userspace which controllers could be
>>> enabled/disabled together ... which is the same as the emulated list, no?
>>
>> I see. So we actually need a single option (control_mode) to switch between
>> modes (legacy vs.
>> native, mutually exclusive), rather than giving each controller its own
>> independent enable/disable
>> toggle. The emulated list is one way to implement control_mode, ensuring
>> "legacy" and "native"
>> are mutually exclusive.
>>
>
> While adjusting the region aware code on this emulation part, a minor issue is found
> in commit ("fs/resctrl: Support emulated controls")
>
> diff --git a/fs/resctrl/rdtgroup.c b/fs/resctrl/rdtgroup.c
> index cac4b3293cef..ab7d3fa3f337 100644
> --- a/fs/resctrl/rdtgroup.c
> +++ b/fs/resctrl/rdtgroup.c
> @@ -124,7 +124,7 @@ void rdt_staged_configs_clear(void)
> if (list_empty(&ctrl->emulated_by))
> continue;
> list_for_each_entry(em_ctrl, &ctrl->emulated_by, entry) {
> - list_for_each_entry_rcu(dom, &ctrl->domains, hdr.list, lockdep_is_cpus_held())
> + list_for_each_entry_rcu(dom, &em_ctrl->domains, hdr.list, lockdep_is_cpus_held())
> memset(dom->staged_config, 0, sizeof(dom->staged_config));
> }
> }
Thank you very much. Squashed and available in branch resctrl/controls_rfc_v2.2
Reinette
next prev parent reply other threads:[~2026-08-13 15:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 5:26 Reinette Chatre
2026-08-05 16:59 ` Ben Horgan
2026-08-05 23:57 ` Reinette Chatre
2026-08-06 17:04 ` Luck, Tony
2026-08-06 17:11 ` Reinette Chatre
2026-08-07 14:14 ` Moger, Babu
2026-08-07 15:35 ` Reinette Chatre
2026-08-07 18:33 ` Moger, Babu
2026-08-07 22:53 ` Reinette Chatre
2026-08-10 18:52 ` Babu Moger
2026-08-11 4:06 ` Reinette Chatre
2026-08-11 14:59 ` Babu Moger
2026-08-11 15:30 ` Reinette Chatre
2026-08-11 16:09 ` Babu Moger
2026-08-07 15:35 ` Chen, Yu C
2026-08-07 17:57 ` Moger, Babu
2026-08-10 2:05 ` Chen, Yu C
2026-08-10 15:53 ` Reinette Chatre
2026-08-10 17:23 ` Chen, Yu C
2026-08-10 18:09 ` Reinette Chatre
2026-08-11 3:49 ` Chen, Yu C
2026-08-13 13:59 ` Chen Yu
2026-08-13 15:19 ` Reinette Chatre [this message]
2026-08-10 2:55 ` Fenghua Yu
2026-08-10 3:02 ` Chen, Yu C
2026-08-10 3:25 ` Fenghua Yu
2026-08-10 5:24 ` Chen, Yu C
2026-08-10 15:53 ` 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=5e07c57d-b971-4c7a-bdfe-3b9c6f299b8b@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=chen.yu@linux.dev \
--cc=dave.hansen@linux.intel.com \
--cc=fenghuay@nvidia.com \
--cc=fustini@kernel.org \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peternewman@google.com \
--cc=tglx@linutronix.de \
--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®