[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1431381021.2398.111.camel@x220>
Date: Mon, 11 May 2015 23:50:21 +0200
From: Paul Bolle <pebolle@...cali.nl>
To: Josh Triplett <josh@...htriplett.org>
Cc: Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Michal Hocko <mhocko@...e.cz>,
Vladimir Davydov <vdavydov@...allels.com>,
Johannes Weiner <hannes@...xchg.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Andy Lutomirski <luto@...capital.net>,
Bertrand Jacquin <beber@...eeweb.net>,
"Luis R. Rodriguez" <mcgrof@...e.com>,
Iulia Manda <iulia.manda21@...il.com>,
Pranith Kumar <bobby.prani@...il.com>,
Clark Williams <clark.williams@...il.com>,
Mel Gorman <mgorman@...e.de>,
Randy Dunlap <rdunlap@...radead.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/1] init/Kconfig: Split expert menu into a separate
file, init/Kconfig.expert
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists