linux-kernel - Re: [RFC PATCH v6] Documentation/arch: Add Documentation/arch-features.txt

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]

Date:	Thu, 14 May 2015 12:16:15 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Josh Triplett <josh@...htriplett.org>
Cc:	Borislav Petkov <bp@...en8.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jonathan Corbet <corbet@....net>,
	Peter Zijlstra <peterz@...radead.org>,
	Andy Lutomirski <luto@...capital.net>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
	x86@...nel.org, linux-arch@...r.kernel.org
Subject: Re: [RFC PATCH v6] Documentation/arch: Add
 Documentation/arch-features.txt


* Josh Triplett <josh@...htriplett.org> wrote:

> On Wed, May 13, 2015 at 09:27:57AM -0700, Josh Triplett wrote:
>
> > How likely is this to get out of date?  Are people going to 
> > remember to patch this when they add a feature to their 
> > architecture?  If they found out they had work to do by reading 
> > this file, which is the goal, then they'll likely remember to edit 
> > the file; however, if they find the feature and fix it without 
> > knowing about the file, will someone notice?
> > 
> > Is there any way we can *generate* this file from Kconfig?  Can we 
> > extract the necessary "this is possible to enable" or "this arch 
> > selects this symbol" information from Kconfig, and together with 
> > the list of symbols for features needing architecture support, 
> > generate the table?
> 
> Just tried this.  Looks like it's pretty trivial for most of these 
> features: just make ARCH=thearch allyesconfig, then look for the 
> config symbol in the result.

No, that's not nearly enough to do a correct support matrix, for 
example due to subarchitectures that aren't included in an 
allyesconfig. There are also many #define driven features.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/