linux-kernel - Re: [PATCH v18 14/33] x86/resctrl: Add data structures and definitions for ABMC assignment

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] [day] [month] [year] [list]

Message-ID: <e3136d56-6b81-4d9e-aca7-d22a14eae49a@amd.com>
Date: Wed, 10 Sep 2025 15:26:54 -0500
From: "Moger, Babu" <babu.moger@....com>
To: Borislav Petkov <bp@...en8.de>
Cc: corbet@....net, tony.luck@...el.com, reinette.chatre@...el.com,
 Dave.Martin@....com, james.morse@....com, tglx@...utronix.de,
 mingo@...hat.com, dave.hansen@...ux.intel.com, x86@...nel.org,
 hpa@...or.com, kas@...nel.org, rick.p.edgecombe@...el.com,
 akpm@...ux-foundation.org, paulmck@...nel.org, frederic@...nel.org,
 pmladek@...e.com, rostedt@...dmis.org, kees@...nel.org, arnd@...db.de,
 fvdl@...gle.com, seanjc@...gle.com, thomas.lendacky@....com,
 pawan.kumar.gupta@...ux.intel.com, perry.yuan@....com,
 manali.shukla@....com, sohil.mehta@...el.com, xin@...or.com,
 Neeraj.Upadhyay@....com, peterz@...radead.org, tiala@...rosoft.com,
 mario.limonciello@....com, dapeng1.mi@...ux.intel.com, michael.roth@....com,
 chang.seok.bae@...el.com, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-coco@...ts.linux.dev,
 kvm@...r.kernel.org, peternewman@...gle.com, eranian@...gle.com,
 gautham.shenoy@....com
Subject: Re: [PATCH v18 14/33] x86/resctrl: Add data structures and
 definitions for ABMC assignment



On 9/10/25 14:59, Borislav Petkov wrote:
> On Wed, Sep 10, 2025 at 02:49:23PM -0500, Moger, Babu wrote:
>> No particular reason — it was just carried over from older MSRs by copy-paste.
>>
>> In fact, all five of them are AMD-specific in this case. Let me know the
>> best way to handle this.
> 
> You could s/IA32/AMD/ them later, when the dust settles.

ok. sounds good.

> 
> "AMD64" would mean they're architectural which doesn't look like it ... yet.
> 

Yea. That's correct.
-- 
Thanks
Babu Moger