* [RFC v3] arm,x86,fs/resctrl: Generic schema description Proof of Concept
@ 2026-11-20 5:04 Reinette Chatre
2026-11-20 19:48 ` Fenghua Yu
0 siblings, 1 reply; 3+ messages in thread
From: Reinette Chatre @ 2026-11-20 5:04 UTC (permalink / raw)
To: Tony Luck, Ben Horgan, James Morse, Dave Martin, Babu Moger,
Drew Fustini, Fenghua Yu, Chen Yu, Jinjie Ruan
Cc: Borislav Petkov, Thomas Gleixner, Dave Hansen, Peter Newman, x86,
linux-kernel, reinette.chatre
Hi Everybody,
I believe that discussions around resctrl's upcoming support for multiple
controls are starting to settle. This RFC aims to capture all the remaining
items in implementation as well as documentation. Please point out to me if
there is anything I missed.
RFC v3 of this PoC can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git branch resctrl/controls_rfc_v3
Please refer to the documentation patch for an overview of the planned interface
changes as well as user space contracts/expectations:
https://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git/commit/?h=resctrl/controls_rfc_v3&id=95ff9ff7430095cb7264946c944c750315db73d9
Remaining opens:
---------------
- Ben: I do have a question about the formula used to determine the size of
a scalar cache control. Please see patch changelog of:
https://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git/commit/?h=resctrl/controls_rfc_v3&id=8695aab0997d5aa60e104374fae9701f51156c18
- MPAM only compile tested.
- The same x86 "SAMPLE" code as RFC v2 to demonstrate emulated controls.
- Add relationships between controls. For example, cannot set "MIN" control
value to be larger than "MAX. Unclear how to do this in resctrl fs when
considering that the relationship may span between emulated and backing
controls. This is potentially something that needs to be managed by architecture
and thus potentially without a consistent failure to user space.
Changes since RFC v2:
--------------------
RFC v2: https://lore.kernel.org/lkml/d258a32f-12d5-464d-abe9-4720fb3e44b3@intel.com/
git://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git branch resctrl/controls_rfc_v2
User visible changes:
- Make scope a property of the control again, now in addition to a separate
allocation scope of the resource. Expose the control scope via a new
per-control "scope" file (L2, L3, or NODE) that tells user space what a
domain ID in the schemata file represents. Needed to support AMD's GLBE
and CPU-less memory bandwidth allocation. (Ben and Babu)
- Name controls according to the scheme agreed during RFC v2 discussions:
<resource>_<resource_scope><control_scope>_<control>, with the control
scope dropped when it matches the resource scope. MB and SMBA carry their
L3 scope only implicitly, so their new controls show it explicitly, for
example MB_L3_MAX, or MB_L3NODE for a default control at NODE scope.
https://lore.kernel.org/all/bccb1249-e722-451a-9c75-8aa846713045@intel.com/
- Report "max" per domain in preparation for systems with resource
instances of different capacity. A bitmap's "max" no longer has a "0x"
prefix. (Drew and Tony)
- Drop the "min_bits" file. The "min" file of a bitmap control now reports
the minimum number of consecutive bits.
- Only offer, and only allow switching to, "native" control mode when the
resource has emulated controls. (Ben)
- Only allow cache pseudo-locking via the default cache control.
- Display the "size" of scalar cache controls. (Ben)
- Stop reporting scalar control parsing errors as being about "MB". (Ben)
- Document the control naming, the "scope" file, that control values may be
reset on a control mode switch, that legacy info files return no content
in "native" mode, and that non-legacy resources need not have a default
control.
Other changes:
- Require a control and the controls it is emulated by to have the same
scope.
- Require only legacy resources to start in legacy control mode.
- Generate control schema suffix once during initialization.
- Fix initialization of the list of emulating controls (Ben), clearing of
staged configurations of backing controls (Chenyu), and Haswell control
initialization (Chenyu).
- Reword changelogs about CDP, allocation size and the bitmap control so
they no longer suggest resctrl will only ever support one cache control.
- Fix checkpatch.pl issues, subject prefixes and changelog typos.
Series structure:
- Rebase on:
- x86/cache branch of tip that is based on v7.4-rc1 with the queued
resctrl cleanups
- MPAM domain separation that was extracted from RFC v2 and submitted
separately:
https://lore.kernel.org/lkml/cover.1794283825.git.reinette.chatre@intel.com/
- Squash four patches into the patches they support:
- "fs/resctrl: Provide control to cache allocation"
- "x86,fs/rectrl: Provide control when requesting arch to update a single
domain", which also keeps MPAM building at every patch in the series.
- "fs/resctrl: Expose bitmap properties via new files in schemata folder"
- "fs/resctrl: Include emulated controls when determining control field
width"
- New patch from Ben: "fs/resctrl: Display size for scalar cache controls".
- Move IO allocation control selection, and the helpers that display the
new control properties, earlier in the series.
Any feedback is appreciated.
Reinette
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [RFC v3] arm,x86,fs/resctrl: Generic schema description Proof of Concept
2026-11-20 5:04 [RFC v3] arm,x86,fs/resctrl: Generic schema description Proof of Concept Reinette Chatre
@ 2026-11-20 19:48 ` Fenghua Yu
2026-11-20 20:26 ` Reinette Chatre
0 siblings, 1 reply; 3+ messages in thread
From: Fenghua Yu @ 2026-11-20 19:48 UTC (permalink / raw)
To: Reinette Chatre, Tony Luck, Ben Horgan, James Morse, Dave Martin,
Babu Moger, Drew Fustini, Chen Yu, Jinjie Ruan
Cc: Borislav Petkov, Thomas Gleixner, Dave Hansen, Peter Newman, x86,
linux-kernel
On 11/19/26 21:04, Reinette Chatre wrote:
> Hi Everybody,
>
> I believe that discussions around resctrl's upcoming support for multiple
> controls are starting to settle. This RFC aims to capture all the remaining
> items in implementation as well as documentation. Please point out to me if
> there is anything I missed.
>
> RFC v3 of this PoC can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git branch resctrl/controls_rfc_v3
>
> Please refer to the documentation patch for an overview of the planned interface
> changes as well as user space contracts/expectations:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git/commit/?h=resctrl/controls_rfc_v3&id=95ff9ff7430095cb7264946c944c750315db73d9
>
> Remaining opens:
> ---------------
> - Ben: I do have a question about the formula used to determine the size of
> a scalar cache control. Please see patch changelog of:
> https://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git/commit/?h=resctrl/controls_rfc_v3&id=8695aab0997d5aa60e104374fae9701f51156c18
> - MPAM only compile tested.
Basic MPAM tests work fine.
Thanks.
-Fenghua
[SNIP]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [RFC v3] arm,x86,fs/resctrl: Generic schema description Proof of Concept
2026-11-20 19:48 ` Fenghua Yu
@ 2026-11-20 20:26 ` Reinette Chatre
0 siblings, 0 replies; 3+ messages in thread
From: Reinette Chatre @ 2026-11-20 20:26 UTC (permalink / raw)
To: Fenghua Yu, Tony Luck, Ben Horgan, James Morse, Dave Martin,
Babu Moger, Drew Fustini, Chen Yu, Jinjie Ruan
Cc: Borislav Petkov, Thomas Gleixner, Dave Hansen, Peter Newman, x86,
linux-kernel
Hi Fenghua,
On 11/20/26 11:48 AM, Fenghua Yu wrote:
>
>
> On 11/19/26 21:04, Reinette Chatre wrote:
>> Hi Everybody,
>>
>> I believe that discussions around resctrl's upcoming support for multiple
>> controls are starting to settle. This RFC aims to capture all the remaining
>> items in implementation as well as documentation. Please point out to me if
>> there is anything I missed.
>>
>> RFC v3 of this PoC can be found at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git branch resctrl/controls_rfc_v3
>>
>> Please refer to the documentation patch for an overview of the planned interface
>> changes as well as user space contracts/expectations:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git/commit/?h=resctrl/controls_rfc_v3&id=95ff9ff7430095cb7264946c944c750315db73d9
>>
>> Remaining opens:
>> ---------------
>> - Ben: I do have a question about the formula used to determine the size of
>> a scalar cache control. Please see patch changelog of:
>> https://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git/commit/?h=resctrl/controls_rfc_v3&id=8695aab0997d5aa60e104374fae9701f51156c18
>> - MPAM only compile tested.
>
> Basic MPAM tests work fine.
>
Thank you very much for testing this. Much appreciated.
This version implements the naming format that Ben pointed out to you in
https://lore.kernel.org/all/10d97df6-ccfc-4025-9773-0ebe7421cbaf@arm.com/
that points to a discussion during RFC v1 of the PoC, which continued in RFC v2
and finally settled there as
https://lore.kernel.org/all/bccb1249-e722-451a-9c75-8aa846713045@intel.com/
In this version, the driver is required to set a scope when creating a new control
and resctrl filesystem constructs the final name. The new naming should "just work"
for features built on top of this. Please let me know where it does not.
Reinette
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-11-20 20:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-11-20 5:04 [RFC v3] arm,x86,fs/resctrl: Generic schema description Proof of Concept Reinette Chatre
2026-11-20 19:48 ` Fenghua Yu
2026-11-20 20:26 ` Reinette Chatre
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®