From: Paul Bolle <pebolle@tiscali.nl>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Michal Hocko <mhocko@suse.cz>,
Vladimir Davydov <vdavydov@parallels.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andy Lutomirski <luto@amacapital.net>,
Bertrand Jacquin <beber@meleeweb.net>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
Iulia Manda <iulia.manda21@gmail.com>,
Pranith Kumar <bobby.prani@gmail.com>,
Clark Williams <clark.williams@gmail.com>,
Mel Gorman <mgorman@suse.de>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/1] init/Kconfig: Split expert menu into a separate file, init/Kconfig.expert
Date: Mon, 11 May 2015 23:50:21 +0200 [thread overview]
Message-ID: <1431381021.2398.111.camel@x220> (raw)
In-Reply-To: <20150511202301.GA11897@jtriplet-mobl1>
On Mon, 2015-05-11 at 13:23 -0700, Josh Triplett wrote:
> --- /dev/null
> +++ b/init/Kconfig.expert
> @@ -0,0 +1,231 @@
> +menuconfig EXPERT
> + bool "Configure standard kernel features (expert users)"
> + # Unhide debug options, to make the on-by-default options visible
> + select DEBUG_KERNEL
> + help
> + This option allows certain base kernel options and settings
> + to be disabled or tweaked. This is for specialized
> + environments which can tolerate a "non-standard" kernel.
> + Only use this if you really know what you are doing.
Comment here saying
# All entries in this file must have "if EXPERT" after their prompt
or something to that effect (pending you patch, that is)?
> +config KALLSYMS
> + bool "Load all symbols for debugging/ksymoops" if EXPERT
> + default y
> + help
> + Say Y here to let the kernel print out symbolic crash information and
> + symbolic stack backtraces. This increases the size of the kernel
> + somewhat, as all symbols have to be loaded into the kernel image.
> +
> +config KALLSYMS_ALL
> + bool "Include all symbols in kallsyms"
(For some reason this entry doesn't have if EXPERT but it seems to
behave as expected. Odd.)
> + depends on DEBUG_KERNEL && KALLSYMS
> + help
> + Normally kallsyms only contains the symbols of functions for nicer
> + OOPS messages and backtraces (i.e., symbols from the text and inittext
> + sections). This is sufficient for most cases. And only in very rare
> + cases (e.g., when a debugger is used) all symbols are required (e.g.,
> + names of variables from the data sections, etc).
> +
> + This option makes sure that all symbols are loaded into the kernel
> + image (i.e., symbols from all sections) in cost of increased kernel
> + size (depending on the kernel configuration, it may be 300KiB or
> + something like this).
> +
> + Say N unless you really need all symbols.
> +
> +config PRINTK
> + default y
> + bool "Enable support for printk" if EXPERT
Now you're touching this: bool [...] as the first line, please.
> + select IRQ_WORK
> + help
> + This option enables normal printk support. Removing it
> + eliminates most of the message strings from the kernel image
> + and makes the kernel more or less silent. As this makes it
> + very difficult to diagnose system problems, saying N here is
> + strongly discouraged.
> +config ELF_CORE
> + depends on COREDUMP
> + default y
> + bool "Enable ELF core dumps" if EXPERT
Ditto.
> + help
> + Enable support for generating core dumps. Disabling saves about 4k.
> +config BASE_FULL
> + default y
> + bool "Enable full-sized data structures for core" if EXPERT
Ditto.
> + help
> + Disabling this option reduces the size of miscellaneous core
> + kernel data structures. This saves memory on small machines,
> + but may reduce performance.
> +config PCI_QUIRKS
> + default y
> + bool "Enable PCI quirk workarounds" if EXPERT
Ditto.
> + depends on PCI
> + help
> + This enables workarounds for various PCI chipset
> + bugs/quirks. Disable this only if your target machine is
> + unaffected by PCI quirks.
Paul Bolle
next prev parent reply other threads:[~2015-05-11 21:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 18:13 [PATCH] init/Kconfig: Fix break in middle of EXPERT menu Josh Triplett
2015-05-11 18:23 ` Randy Dunlap
2015-05-11 20:23 ` [PATCH 2/1] init/Kconfig: Split expert menu into a separate file, init/Kconfig.expert Josh Triplett
2015-05-11 21:01 ` Paul Bolle
2015-05-11 21:18 ` Josh Triplett
2015-05-11 21:32 ` Paul Bolle
2015-05-11 21:47 ` Josh Triplett
2015-05-11 22:01 ` Paul Bolle
2015-05-11 22:40 ` Josh Triplett
2015-05-11 21:50 ` Paul Bolle [this message]
2015-05-11 22:04 ` Josh Triplett
2015-05-11 22:15 ` Paul Bolle
2015-05-28 8:13 ` Paul Bolle
2015-05-11 22:36 ` Luis R. Rodriguez
2015-05-11 22:51 ` Josh Triplett
2015-05-12 7:04 ` [PATCH] init/Kconfig: Fix break in middle of EXPERT menu Ingo Molnar
2015-05-12 7:08 ` Josh Triplett
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=1431381021.2398.111.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=akpm@linux-foundation.org \
--cc=beber@meleeweb.net \
--cc=bobby.prani@gmail.com \
--cc=clark.williams@gmail.com \
--cc=geert@linux-m68k.org \
--cc=hannes@cmpxchg.org \
--cc=iulia.manda21@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@suse.com \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rdunlap@infradead.org \
--cc=vdavydov@parallels.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