Re: [PATCH 1/2] x86/resctrl, Documentation: Keep mbm_assign_mode "default" on boot

Hi Boris,

On 7/28/26 14:18, Borislav Petkov wrote:
> On Fri, Jul 17, 2026 at 04:13:55PM -0500, Babu Moger wrote:
>> The kernel currently enables the ABMC-based "mbm_event" mode by default on
>> hardware that supports it. However, this can cause bandwidth monitoring
>> failures with existing userspace tools such as pqos.
>>
>> The pqos tool mounts the resctrl filesystem and creates 16 or more resctrl
>> groups by default. On systems with 32 or fewer ABMC counters, this default
>> configuration can consume all available counters, since each group requires
>> one counter for local MBM and another for total MBM. If additional
>> monitoring groups are created, counter resources are exhausted and pqos
>> tool reports memory bandwidth counters as zero for those groups.
>>
>> Avoid this compatibility issue by leaving mbm_assign_mode in the "default"
>> mode during initialization.
> 
> Question: why doesn't the default mode suffer from this counter exhaustion? Or
> if it does, why is the whole issue better in the default mode?
> 
ABMC mode (also referred to as mbm_event mode) relies on ABMC counters, 
and this system provides only 32 such counters.

By comparison, the default mode uses RMIDs, with up to 4096 RMIDs 
available. However, even though the RMID space is much larger, the 
hardware can track only 64 RMIDs concurrently. As a result, if pqos 
attempts to monitor more than 64 groups, the reported bandwidth 
measurements may become inaccurate.

That said, I have not been able to reproduce any bandwidth inaccuracies 
on the systems I tested. My point is that this may not be a significant 
issue for the vast majority of users.

The possibility of reduced accuracy when monitoring a large number of 
groups is the primary concern that Reinette has raised.

Thanks
Babu