[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <569E089B.2000808@suse.cz>
Date: Tue, 19 Jan 2016 10:57:47 +0100
From: Michal Marek <mmarek@...e.cz>
To: Ingo Molnar <mingo@...nel.org>
Cc: Borislav Petkov <bp@...e.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Måns Rullgård <mans@...sr.com>,
Markus Trippelsdorf <markus@...ppelsdorf.de>,
Thomas Voegtle <tv@...96.de>, linux-kernel@...r.kernel.org,
x86-ml <x86@...nel.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>,
Jiri Olsa <jolsa@...hat.com>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Frédéric Weisbecker <fweisbec@...il.com>
Subject: Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y
On 2016-01-19 09:20, Ingo Molnar wrote:
> In fact on x86 I'd suggest we go farther than that and add a core set of selects
> that can be disabled only through a sufficiently scary "I really know I'm doing
> something utmost weird" (and default disabled) config option.
Agreed.
> From my own randconfig testing I can give a core list of must-have kernel options,
> without which most distros (Fedora, RHEL, Ubuntu, SuSE) won't boot properly:
>
> +config FORCE_MINIMALLY_SANE_CONFIG
> + bool
> + default y
You should add a prompt so that the option can be disabled. Or make it
default !EXPERT, to have a single "I know what I'm doing"-type of option.
Michal
Powered by blists - more mailing lists