From: Ingo Molnar <mingo@kernel.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Borislav Petkov <bp@alien8.de>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-arch@vger.kernel.org
Subject: Re: [RFC PATCH v6] Documentation/arch: Add Documentation/arch-features.txt
Date: Thu, 14 May 2015 12:16:15 +0200 [thread overview]
Message-ID: <20150514101615.GB27550@gmail.com> (raw)
In-Reply-To: <20150513165358.GA22979@x>
* Josh Triplett <josh@joshtriplett.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
next prev parent reply other threads:[~2015-05-14 10:16 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 19:29 [PATCHv2 1/2] clone: Support passing tls argument via C rather than pt_regs magic Josh Triplett
2015-05-12 21:22 ` Andrew Morton
2015-05-12 21:38 ` Peter Zijlstra
2015-05-12 21:49 ` Andrew Morton
2015-05-13 8:34 ` [RFC PATCH] Documentation/arch: Add Documentation/arch-TODO Ingo Molnar
2015-05-13 8:56 ` [RFC PATCH v2] " Ingo Molnar
2015-05-13 9:24 ` [RFC PATCH v3] " Ingo Molnar
2015-05-13 9:46 ` Ingo Molnar
2015-05-13 9:47 ` [RFC PATCH v5] " Ingo Molnar
2015-05-13 13:18 ` Borislav Petkov
2015-05-13 13:48 ` [RFC PATCH v6] Documentation/arch: Add Documentation/arch-features.txt Ingo Molnar
2015-05-13 16:27 ` Josh Triplett
2015-05-13 16:53 ` Josh Triplett
2015-05-14 10:16 ` Ingo Molnar [this message]
2015-05-14 10:31 ` Josh Triplett
2015-05-13 22:05 ` Andrew Morton
2015-05-14 10:02 ` Ingo Molnar
2015-05-14 10:15 ` [PATCH] Documentation/arch: Add kernel feature descriptions and arch support status under Documentation/features/ Ingo Molnar
2015-05-14 10:35 ` [PATCH v2] " Ingo Molnar
2015-05-14 19:38 ` Andrew Morton
2015-05-14 19:59 ` Ingo Molnar
2015-05-14 22:33 ` Stephen Rothwell
2015-05-15 7:38 ` Ingo Molnar
2015-05-15 7:51 ` Ingo Molnar
2015-05-15 9:37 ` Ingo Molnar
2015-05-14 20:34 ` Richard Weinberger
2015-05-14 22:57 ` Michael Ellerman
2015-05-15 7:49 ` Ingo Molnar
2015-05-18 1:37 ` Michael Ellerman
2015-05-18 8:54 ` Ingo Molnar
2015-05-19 2:02 ` Michael Ellerman
2015-05-22 15:49 ` Jonathan Corbet
2015-05-23 8:07 ` Ingo Molnar
2015-05-24 18:44 ` Jonathan Corbet
2015-06-03 11:03 ` [GIT PULL] Documentation/features: Add kernel feature descriptions and arch support status files " Ingo Molnar
2015-06-08 23:08 ` Jonathan Corbet
2015-05-14 7:08 ` [RFC PATCH v6] Documentation/arch: Add Documentation/arch-features.txt Ingo Molnar
2015-05-14 3:55 ` Paul Mackerras
2015-05-14 7:02 ` Ingo Molnar
2015-05-13 14:09 ` [RFC PATCH v5] Documentation/arch: Add Documentation/arch-TODO Michele Curti
2015-05-13 14:42 ` Geert Uytterhoeven
2015-05-14 7:21 ` H. Peter Anvin
2015-05-14 7:21 ` H. Peter Anvin
2015-05-13 0:53 ` [PATCHv2 1/2] clone: Support passing tls argument via C rather than pt_regs magic josh
2015-05-13 22:56 ` Andrew Morton
2015-05-13 23:25 ` josh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150514101615.GB27550@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=josh@joshtriplett.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).