linux-kernel - Re: [PATCH v6 09/22] x86/resctrl: Introduce MBM counters bitmap

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: <c7e601f6-35cd-49fd-b120-62b9f4d99f13@intel.com>
Date: Tue, 20 Aug 2024 11:08:40 -0700
From: Reinette Chatre <reinette.chatre@...el.com>
To: <babu.moger@....com>, <corbet@....net>, <fenghua.yu@...el.com>,
	<tglx@...utronix.de>, <mingo@...hat.com>, <bp@...en8.de>,
	<dave.hansen@...ux.intel.com>
CC: <x86@...nel.org>, <hpa@...or.com>, <paulmck@...nel.org>,
	<rdunlap@...radead.org>, <tj@...nel.org>, <peterz@...radead.org>,
	<yanjiewtw@...il.com>, <kim.phillips@....com>, <lukas.bulwahn@...il.com>,
	<seanjc@...gle.com>, <jmattson@...gle.com>, <leitao@...ian.org>,
	<jpoimboe@...nel.org>, <rick.p.edgecombe@...el.com>,
	<kirill.shutemov@...ux.intel.com>, <jithu.joseph@...el.com>,
	<kai.huang@...el.com>, <kan.liang@...ux.intel.com>,
	<daniel.sneddon@...ux.intel.com>, <pbonzini@...hat.com>,
	<sandipan.das@....com>, <ilpo.jarvinen@...ux.intel.com>,
	<peternewman@...gle.com>, <maciej.wieczor-retman@...el.com>,
	<linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<eranian@...gle.com>, <james.morse@....com>
Subject: Re: [PATCH v6 09/22] x86/resctrl: Introduce MBM counters bitmap

Hi Babu,

On 8/19/24 8:49 AM, Moger, Babu wrote:
> On 8/16/24 16:35, Reinette Chatre wrote:
>> On 8/6/24 3:00 PM, Babu Moger wrote:

>> resource
>> as parameter but freeing a counter does not. James already proposed different
>> treatment of the bitmap and L3 resource parameters, I expect with such
>> guidance
>> the interfaces will become more intuitive.
>>
> 
> How about making "mbm_cntrs_free_map" as part  of struct resctrl_mon?
> It will be pointer and allocated dynamically based on number of counters.
> All the related information (num_mbm_cntrs and mbm_cntr_assignable) is
> already part of this data structure.

That sounds good.

Reinette