[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150514103101.GA30945@x>
Date: Thu, 14 May 2015 03:31:01 -0700
From: Josh Triplett <josh@...htriplett.org>
To: Ingo Molnar <mingo@...nel.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
On Thu, May 14, 2015 at 12:16:15PM +0200, Ingo Molnar wrote:
>
> * 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.
Still feasible to automate with a bit more scripting.
> There are also many #define driven features.
It'd be nice to move those over to Kconfig.
- Josh Triplett
--
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/
Powered by blists - more mailing lists