From: Babu Moger <bmoger@amd.com>
To: Aaron Tomlin <atomlin@atomlin.com>, "Luck, Tony" <tony.luck@intel.com>
Cc: "Chatre, Reinette" <reinette.chatre@intel.com>,
"Dave.Martin@arm.com" <Dave.Martin@arm.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"babu.moger@amd.com" <babu.moger@amd.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] x86/resctrl: Add io_alloc_min_cbm_all interface for CBM reset
Date: Tue, 11 Nov 2025 15:04:55 -0600 [thread overview]
Message-ID: <589d5db4-68f8-4aee-9d6e-dee5b8754564@amd.com> (raw)
In-Reply-To: <7e264e18-23f4-4566-86f2-f0600a243227@amd.com>
Hi Reinette,
On 11/11/25 09:29, Babu Moger wrote:
> Hi Everyone,
>
> On 11/10/25 20:44, Aaron Tomlin wrote:
>> On Tue, Nov 11, 2025 at 01:40:45AM +0000, Luck, Tony wrote:
>>>> Seems like user space has needed information to perform a sane reset?
>>> Like this:
>>>
>>> 1) Read info files to figure out what minimum mask is needed for
>>> this system
>>> 2) Use Babu's suggested syntax of
>>> # echo "L3:*={min_mask_from_step_1}" > schemata
>>>
>>> Rather than Aaron's
>>>
>>> # echo "L3:*=0" > schemata
>> Hi Tony,
>>
>> I am satisfied with either approach.
>>
>> However, to clarify, the primary function of the "io_alloc_min_cbm_all"
>> interface is to efficiently set the lowest architecturally valid CBM
>> across
>> all shared L3 domains. This operation relies entirely on
>> r->cache.min_cbm_bits. Since this value is guaranteed by the hardware
>> to be
>> valid, this approach is robust and will not return an error (e.g.,
>> -EINVAL)
>> to userspace.
>>
>>
>
> Here’s my understanding of the discussion from this thread:
>
>
> We plan to support the following operation:
>
> #echo "*=value" > /sys/fs/resctrl/info/L3/io_alloc_cbm
>
Looks like we are going with the above approach where "*" represents all
the domain.
Couple of things to consider.
a. Send a separate patch to add this feature after [1] is merged.
b. Add this change as part of [1] series in patch 9. The series is
mostly ready for merge. I can add the changes. Only concern is, it will
might delay the series merge little bit. My expectation is to have this
series ready for next merge window.
[1] https://lore.kernel.org/lkml/cover.1761844489.git.babu.moger@amd.com/
Any thoughts?
Thanks
Babu
next prev parent reply other threads:[~2025-11-11 21:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 1:23 [PATCH 0/2] x86/resctrl: Add io_alloc_min_cbm_all interface for CBM reset Aaron Tomlin
2025-11-07 1:24 ` [PATCH 1/2] " Aaron Tomlin
2025-11-07 22:02 ` Moger, Babu
2025-11-07 22:25 ` Aaron Tomlin
2025-11-07 23:08 ` Moger, Babu
2025-11-08 0:19 ` Aaron Tomlin
2025-11-08 0:42 ` Luck, Tony
2025-11-10 16:34 ` Babu Moger
2025-11-10 17:50 ` Luck, Tony
2025-11-10 19:42 ` Babu Moger
2025-11-10 19:56 ` Luck, Tony
2025-11-10 21:40 ` Reinette Chatre
2025-11-11 0:41 ` Aaron Tomlin
2025-11-11 0:51 ` Luck, Tony
2025-11-11 1:00 ` Reinette Chatre
2025-11-11 1:40 ` Luck, Tony
2025-11-11 2:37 ` Reinette Chatre
2025-11-11 2:44 ` Aaron Tomlin
2025-11-11 15:29 ` Babu Moger
2025-11-11 21:04 ` Babu Moger [this message]
2025-11-11 22:34 ` Aaron Tomlin
2025-11-11 23:21 ` Moger, Babu
2025-11-07 1:24 ` [PATCH 2/2] fs/resctrl: resctrl: Return -EINVAL for a missing seq_show implementation Aaron Tomlin
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=589d5db4-68f8-4aee-9d6e-dee5b8754564@amd.com \
--to=bmoger@amd.com \
--cc=Dave.Martin@arm.com \
--cc=atomlin@atomlin.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@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