[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2d9a60fb-1544-427f-9c73-d303bfe85773@intel.com>
Date: Mon, 9 Dec 2024 11:28:59 -0800
From: Sohil Mehta <sohil.mehta@...el.com>
To: "H. Peter Anvin" <hpa@...or.com>, <x86@...nel.org>, "Ahmed S . Darwish"
<darwi@...utronix.de>
CC: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
"Uros Bizjak" <ubizjak@...il.com>, Sandipan Das <sandipan.das@....com>, "Sean
Christopherson" <seanjc@...gle.com>, Peter Zijlstra <peterz@...radead.org>,
Vegard Nossum <vegard.nossum@...cle.com>, Tony Luck <tony.luck@...el.com>,
Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>, Nikolay Borisov
<nik.borisov@...e.com>, Eric Biggers <ebiggers@...gle.com>, Xin Li
<xin3.li@...el.com>, Alexander Shishkin <alexander.shishkin@...el.com>,
Kirill Shutemov <kirill.shutemov@...ux.intel.com>,
<linux-kernel@...r.kernel.org>, Borislav Petkov <bp@...en8.de>, Dave Hansen
<dave.hansen@...ux.intel.com>
Subject: Re: [PATCH v3 2/2] x86/cpufeature: Add a debug print for unmet
dependencies
On 12/7/2024 1:11 PM, H. Peter Anvin wrote:
>
> Ok, I realize that the x86 maintainers **very legitimately** don't
> want more crap in /proc/cpuinfo, but perhaps we could include the
> strings for printing debug messages in cleartext? Add a bitmap for
> which entries should go into /proc/cpuinfo.
Could the cpuid-db project be helpful at some point in this regard? It
seems to have a name ("id") for each feature and a tracking of whether
each feature is exposed via cpuinfo and with what name.
> <bit20 len="1" id="cet_ibt" desc="CET indirect branch tracking">
> <linux feature="true" proc="true" altid="ibt" />
> </bit20>
Though I am not sure if it only tracks the hardware originating features
represented in cpuid or the linux defined features as well?
Powered by blists - more mailing lists