linux-kernel - Re: [PATCH] Documentation/x86: Clarify naming of CPU features for /proc/cpuinfo

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: <en5nisgiq2in7sjj2ysovxrqcuqh6ruhi32nsfrwamrt6odftc@jehodnirqa64>
Date: Thu, 3 Apr 2025 20:32:15 +0530
From: Naveen N Rao <naveen@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org, 
	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...nel.org>, 
	Dave Hansen <dave.hansen@...ux.intel.com>, Jonathan Corbet <corbet@....net>, x86@...nel.org
Subject: Re: [PATCH] Documentation/x86: Clarify naming of CPU features for
 /proc/cpuinfo

On Thu, Apr 03, 2025 at 03:21:21PM +0200, Borislav Petkov wrote:
> On Thu, Apr 03, 2025 at 06:40:00PM +0530, Naveen N Rao wrote:
> > As far as I can tell, the script still processes cpufeatures.h but no 
> > longer "generates" names. It simply picks names within double-quotes if 
> > present. I don't think that is relevant for describing how the flags are 
> > named anymore.
> 
> It is relevant in a documentation file which is called cpuinfo.rst. Because
> this thing is somewhat of a magic - and Xen has even more magic there - so I'd
> like that file to explain the *whole* story.

Ok.

> 
> > Regardless, please take another look at this and let me know if you 
> > think this still doesn't read right, or is missing anything (the script 
> > part, in particular). For reference, here is how the flag naming section 
> > looks like with this patch:
> 
> Tell you what: I'll take your text, put it in the file, edit it how I think it
> should like and send you a patch for you to ack. This'll save us a lot of
> time.

Sure, feel free to edit my patch as you see fit before applying. I am 
fine if you want to retain the section about the script - it should 
still be a minor edit, unless you want to rewrite other parts.


Thank you!
- Naveen