linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Borislav Petkov <bp@alien8.de>, 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: [PATCH v2] Documentation/arch: Add kernel feature descriptions and arch support status under Documentation/features/
Date: Fri, 15 May 2015 08:57:28 +1000	[thread overview]
Message-ID: <1431644248.2981.1.camel@ellerman.id.au> (raw)
In-Reply-To: <20150514123835.1bf436bc35d711f8dbf9bc0f@linux-foundation.org>

On Thu, 2015-05-14 at 12:38 -0700, Andrew Morton wrote:
> > Add arch support matrices for more than 40 generic kernel features
> > that need per architecture support.
> > 
> > Each feature has its own directory under Documentation/features/feature_name/,
> > and the arch-support.txt file shows its current arch porting status.
> 
> It would be nice to provide people with commit IDs to look at, but the
> IDs won't be known at the time the documentation file is created.  We
> could provide patch titles.

+1 on patch titles.

> But still, let's not overdo it - get something in there, see how well
> it works, evolve it over time.
> 
> I don't think we've heard from any (non-x86) arch maintainers?  Do they
> consider this useful at all?  Poke.

Yes it is. I have my own version I've cobbled together for powerpc, but this is
much better.

I'd like to see more description in the individual files of what the feature
is, and preferably some pointers to what's needed to implement it.

The kconfig for HAVE_ARCH_SECCOMP_FILTER is a good example of what I mean.

I realise retrofitting that for all these existing features is quite time
consuming, but for new features hopefully the bar can be raised a little in
terms of that description.

cheers



  parent reply	other threads:[~2015-05-14 22:57 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
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 [this message]
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=1431644248.2981.1.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --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@kernel.org \
    --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).