linux-kernel - Re: [PATCH v2 3/3] x86/resctrl: Add "*" shorthand to set minimum io

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6aa6ac29-462a-453f-ace8-43aef9ed67c4@amd.com>
Date: Thu, 18 Dec 2025 18:40:23 -0600
From: "Moger, Babu" <bmoger@....com>
To: Aaron Tomlin <atomlin@...mlin.com>
Cc: "Luck, Tony" <tony.luck@...el.com>,
 "Chatre, Reinette" <reinette.chatre@...el.com>,
 "Dave.Martin@....com" <Dave.Martin@....com>,
 "james.morse@....com" <james.morse@....com>,
 "babu.moger@....com" <babu.moger@....com>,
 "tglx@...utronix.de" <tglx@...utronix.de>,
 "mingo@...hat.com" <mingo@...hat.com>, "bp@...en8.de" <bp@...en8.de>,
 "dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
 "sean@...e.io" <sean@...e.io>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 3/3] x86/resctrl: Add "*" shorthand to set minimum
 io_alloc CBM for all domains

Hi Aaron,

On 12/18/2025 6:31 PM, Aaron Tomlin wrote:
> On Thu, Dec 18, 2025 at 03:56:24PM -0600, Moger, Babu wrote:
>>> Why is io_alloc special? The same simple change could apply to
>>> parse_line() to allow setting all domains in a resource to be set to
>>> the same value:
> 
> Hi Tony, Babu,
> 
>> Yes. I am fine with that approach. Treat "*" equivalent for all the
>> resources not just io_alloc.
> 
> No. While I appreciate the desire for a more uniform interface, I would
> strongly suggest that this particular change remain applicable only to
> io_alloc for the time being. If I recall correctly, the architectural
> requirements for other resources differ enough that the suggested approach
> may not be universally applicable or appropriate in every case, no?
> 

Yes. That is correct. Lets do this only for io_alloc.

Reinette commented on the already.

https://lore.kernel.org/lkml/a76c2eee-2a64-42ab-b81c-90638321cd15@intel.com/

Thanks
Babu