Re: [PATCH v9 14/26] x86/resctrl: Introduce interface to display number of free counters

[Reinette Chatre <reinette.chatre@intel.com>]

Hi Babu,

On 11/22/24 3:36 PM, Moger, Babu wrote:
> Hi Reinette,
> 
> On 11/21/2024 3:12 PM, Reinette Chatre wrote:
>> Hi Babu,
>>
>> On 11/19/24 11:20 AM, Moger, Babu wrote:
>>> Hi Reinette,
>>>
>>> On 11/15/24 18:31, Reinette Chatre wrote:
>>>> Hi Babu,
>>>>
>>>> On 10/29/24 4:21 PM, Babu Moger wrote:
>>>>> Provide the interface to display the number of free monitoring counters
>>>>> available for assignment in each doamin when mbm_cntr_assign is supported.
>>>>>
>>>>> Signed-off-by: Babu Moger <babu.moger@amd.com>
>>>>> ---
>>>>> v9: New patch.
>>>>> ---
>>>>>   Documentation/arch/x86/resctrl.rst     |  4 ++++
>>>>>   arch/x86/kernel/cpu/resctrl/monitor.c  |  1 +
>>>>>   arch/x86/kernel/cpu/resctrl/rdtgroup.c | 33 ++++++++++++++++++++++++++
>>>>>   3 files changed, 38 insertions(+)
>>>>>
>>>>> diff --git a/Documentation/arch/x86/resctrl.rst b/Documentation/arch/x86/resctrl.rst
>>>>> index 2f3a86278e84..2bc58d974934 100644
>>>>> --- a/Documentation/arch/x86/resctrl.rst
>>>>> +++ b/Documentation/arch/x86/resctrl.rst
>>>>> @@ -302,6 +302,10 @@ with the following files:
>>>>>       memory bandwidth tracking to a single memory bandwidth event per
>>>>>       monitoring group.
>>>>>   +"available_mbm_cntrs":
>>>>> +    The number of free monitoring counters available assignment in each domain
>>>>
>>>> "The number of free monitoring counters available assignment" -> "The number of monitoring
>>>> counters available for assignment"?
>>>>
>>>> (not taking into account how text may change after addressing Peter's feedback)
>>>
>>> How about this?
>>>
>>> "The number of monitoring counters available for assignment in each domain
>>> when the architecture supports mbm_cntr_assign mode. There are a total of
>>> "num_mbm_cntrs" counters are available for assignment. Counters can be
>>> assigned or unassigned individually in each domain. A counter is available
>>> for new assignment if it is unassigned in all domains."
>>
>> Please consider the context of this paragraph. It follows right after the description
>> of "num_mbm_cntrs" that states "Up to two counters can be assigned per monitoring group".
>> I think it is confusing to follow that with a paragraph that states "Counters can be
>> assigned or unassigned individually in each domain." I wonder if it may be helpful to
>> use a different term ... for example a counter is *assigned* to an event of a monitoring
>> group but this assignment may be to specified (not yet supported) or all (this work) domains while
>> it is only *programmed*/*activated* to specified domains. Of course, all of this documentation
>> needs to remain coherent if future work decides to indeed support per-domain assignment.
>>
> 
> Little bit lost here. Please help me.

I think this highlights the uncertainty this interface brings. How do you expect users
to use this interface? At this time I think this interface can create a lot of confusion.
For example, consider a hypothetical system with three domains and four counters that
has the following state per mbm_assign_control:

//0=tl;1=_;2=l #default group uses counters 0 and 1 to monitor total and local MBM
/m1/0=_;1=t;2=t #monitor group m1 uses counter 2, just for total MBM
/m2/0=l;1=_;2=l #monitor group m2 uses counter 3, just for local MBM
/m3/0=_;1=_;2=_

Since, in this system there are only four counters available, and
they have all been assigned, then there are no new counters available for
assignment.

If I understand correctly, available_mbm_cntrs will read:
0=1;1=3;2=1

How is a user to interpret the above numbers? It does not reflect
that no counter can be assigned to m3, instead it reflects which of the
already assigned counters still need to be activated on domains.
If, for example, a user is expected to use this file to know how
many counters can still be assigned, should it not reflect the actual
available counters. In the above scenario it will then be:
0=0;1=0;2=0

Of course, when doing the above the user may get impression that a counter
that has already been assigned, just not activated, is no longer available
for use.

 
> "available_mbm_cntrs":
> "The number of monitoring counters available for assignment in each domain when the architecture supports "mbm_cntr_assign" mode. There are a total of "num_mbm_cntrs" counters are available for assignment.
> A counter is assigned to an event within a monitoring group and is available for activation across all domains. Users have the flexibility to activate it selectively within specific domains."
> 

Once we understand how users are to use this file the documentation should be easier
to create.

Reinette