Re: [PATCH v6 04/18] fs/resctrl: Introduce kernel mode enum

[Babu Moger <babu.moger@amd.com>]

Hi Reinette,

On 10/19/26 11:17, Reinette Chatre wrote:
> Hi Babu,
> 
> On 10/15/26 4:09 PM, Babu Moger wrote:
>> On 10/15/26 09:44, Reinette Chatre wrote:
>>> On 10/1/26 8:10 AM, Babu Moger wrote:
>>>> Kernel mode work can use different allocation and monitoring associations
>>>
>>> Here I think "different allocation and monitoring associations" means
>>> different CLOSID/RMID, while other places "different allocation and monitoring
>>> associations" means different MSR_IA32_PQR_PLZA_ASSOC.closid_en and
>>> MSR_IA32_PQR_PLZA_ASSOC.rmid_en?
>>
>> That is correct. Hope text here is fine.
>>
> I had to guess. This is the same topic as being discussed in patch #3. Could you
> please add clear definitions to eliminate the need for guessing?
> 
> 
Ack, rephrased the changelog to use CLOSID and RMID terminology to avoid 
the ambiguity around "allocation and monitoring associations". If you 
agree, we can use CLOSID and RMID consistently throughout the series.


"fs/resctrl: Introduce kernel mode enum

Kernel mode operation enables a CPU to use a different CLOSID and/or
RMID when executing in kernel mode than those used in user mode.

Architectures need a common set of kernel mode definitions so resctrl
can report supported modes and indicate which mode is active.

Introduce enum resctrl_kernel_mode:

   - RESCTRL_INHERIT_USER: Kernel mode work inherits the CLOSID and/or
     RMID of the user task.

   - RESCTRL_GLOBAL_ENABLE_PER_CPU: Kernel mode work uses a single
     global CLOSID and/or RMID association shared by all userspace
     tasks. The mode can be enabled or disabled on a per-CPU basis.

Signed-off-by: Babu Moger <babu.moger@amd.com>"

Thanks
Babu