From: Linus Torvalds <torvalds@linux-foundation.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>,
Michal Hocko <mhocko@kernel.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] is Kconfig a bit hard sometimes?
Date: Tue, 27 Jun 2017 10:18:04 -0700 [thread overview]
Message-ID: <CA+55aFxBUe4QAa11i-ySr2i959EpvcEZYf=9NumWyTDH+6BEQw@mail.gmail.com> (raw)
In-Reply-To: <20170627135839.GB1886@jagdpanzerIV.localdomain>
On Tue, Jun 27, 2017 at 6:58 AM, Sergey Senozhatsky
<sergey.senozhatsky.work@gmail.com> wrote:
>
> am I the only one who struggle with the Kconfig sometimes?
I hate our Kconfig. It's my least favorite part of the kernel. It asks
questions about insane things that nobody can know the answer to.
Taking a distro default config and doing"make localmodconfig" is what
I end up doing on new machines, and it has all kinds of suckage too.
I don't have a solution to it. But I think part of the solution would
be for us to have various "sane minimal requirement" Kconfig
fragments, and trhe ability to feed them incrementally, so that people
can build up a sane Kconfig from "I want this".
For example, instead of answering a million odd questions about
specific features that the base distro expects to always be there
(say, just the networking firewall rules and stuff like that), have
some "minimal required features to boot Fedora 25 or SuSE 12 sp2".
And then a "I use Intel KVM, so I need those minimal features, but I
do *not* want paravirtualization or any other virtualization
services".
We could *maybe* make it part of some "make simpleconfig" that just
basically uses "select" a lot with s special architecture-specific
Kconfig file, and try to help people with a few bigger questions.
Not the thousands of detailed questions. Just do the big strokes, and
enable teh *normal* still. The "defconfig" approach doesn't work (and
hasn't for a long time except for cases where you have very specific
configurations), but just having the abilitty to enable a *sane* basic
config for modern machines would be fine.
Would you have to tweak it later when you have odd hardware or speific
issues? Yes. But there shouldn't be a single question about USB - just
enable basic support, and then add support for HID and USB storage
that pretty much everybody will need. Things like that, to get a
workign but basic config going.
And yes, the security questions are all insane. Nobody knows what the
answers are, since some of it is distro-specific, and others are just
"do you want to test hardening". And because people don't even know
which is which, they often end up enabling features that they
shouldn't, just because they are unsure.
The default distro config still enables PCCARD support, even if you
don't have a laptop at all (or if your laptop is not from the middle
ages any more). Big things like that make a big difference in what
questions you are then asked about random devices.
ISDN? ATM? They're dead. Some sane simple config shouldn't ask about
them any more. The "ten thousand questions" could probably be narrowed
down to maybe a few tens, with some tweaking for special devices
people have lying around.
And note that none of this is about technoliogy, and SAT solvers and
resolving the KConfig depdendencies that some techie people love
talking about. It's all about "what if we just had some kconfig
fragments to enable some commonly used stuff" (where "commonly used"
is obviously architecture dependent, but also target-dependent - a
"simpleconfig" for a PC workstation kind of config is very different
from a "simpleconfig" for a server or some ARM embedded thing).
Linus
next prev parent reply other threads:[~2017-06-27 17:18 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 13:58 Sergey Senozhatsky
2017-06-27 17:18 ` Linus Torvalds [this message]
2017-06-27 18:44 ` Luis R. Rodriguez
2017-06-27 19:27 ` Linus Torvalds
2017-06-27 20:53 ` Kees Cook
2017-06-27 21:16 ` Olof Johansson
2017-06-27 21:36 ` Linus Torvalds
2017-06-27 23:10 ` Serge E. Hallyn
2017-06-28 0:09 ` Luis R. Rodriguez
2017-06-28 0:14 ` Linus Torvalds
2017-06-28 0:26 ` Luis R. Rodriguez
2017-06-28 3:54 ` Stephen Hemminger
[not found] ` <CAFhKne-o0S8fMo_XD_aUk2Rf7VbDhgO+PT_bjnM-9WpKfnWBvw@mail.gmail.com>
[not found] ` <CAFhKne8FE=17wNdp=Svf2Z2tADok6htfYqTABEiZUrCOyeMaYg@mail.gmail.com>
2017-06-28 13:35 ` Matthew Wilcox
2017-06-28 17:56 ` Geert Uytterhoeven
2017-06-29 10:02 ` Mauro Carvalho Chehab
2017-06-28 0:11 ` Linus Torvalds
2017-06-29 10:23 ` Mauro Carvalho Chehab
2017-06-28 12:58 ` Dan Carpenter
2017-06-30 17:11 ` Steven Rostedt
2017-06-30 17:52 ` Darren Hart
2017-06-30 17:58 ` Darren Hart
2017-07-01 17:24 ` Hannes Reinecke
2017-06-27 20:41 ` Kees Cook
2017-07-06 14:40 ` Dan Carpenter
2017-07-06 14:41 ` [Ksummit-discuss] [PATCH 1/2] kconfig: add a silent option to conf_write() Dan Carpenter
2017-07-06 15:08 ` Steven Rostedt
2017-07-06 14:42 ` [Ksummit-discuss] [PATCH 2/2] kconfig: new command line kernel configuration tool Dan Carpenter
2017-07-07 5:55 ` Krzysztof Kozlowski
2017-07-07 9:02 ` Dan Carpenter
2017-07-09 3:56 ` Linus Walleij
2017-07-09 8:31 ` Geert Uytterhoeven
2017-07-09 17:03 ` Randy Dunlap
2017-07-09 19:43 ` Geert Uytterhoeven
2017-07-09 17:32 ` Frank Rowand
2017-07-10 9:44 ` Geert Uytterhoeven
2017-07-10 11:15 ` Dan Carpenter
2017-07-06 16:41 ` [Ksummit-discuss] [TECH TOPIC] is Kconfig a bit hard sometimes? Linus Torvalds
2017-07-06 17:11 ` Randy Dunlap
2017-07-07 11:36 ` Dan Carpenter
2017-07-10 17:15 ` Luck, Tony
2017-07-10 17:33 ` Alexandre Belloni
2017-07-10 18:28 ` Linus Torvalds
2017-07-10 19:44 ` Randy Dunlap
2017-07-11 6:21 ` Valentin Rothberg
2017-07-06 21:19 ` Laurent Pinchart
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='CA+55aFxBUe4QAa11i-ySr2i959EpvcEZYf=9NumWyTDH+6BEQw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mhocko@kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
/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