Marc Andre Tanner ha scritto: > Introduce a config option which allows to selectively compile out > printk messages based on a specified verbosity level. > > Signed-off-by: Marc Andre Tanner <mat@xxxxxxxxxxxxxx> > --- > init/Kconfig | 29 +++++++++++++++++++++++++++++ > 1 files changed, 29 insertions(+), 0 deletions(-) > > diff --git a/init/Kconfig b/init/Kconfig > index 3f7e609..549ed95 100644 > --- a/init/Kconfig > +++ b/init/Kconfig > @@ -833,6 +833,35 @@ config PRINTK > very difficult to diagnose system problems, saying N here is > strongly discouraged. > > +config PRINTK_VERBOSITY > + int "Printk compile time verbosity" > + depends on EMBEDDED && PRINTK > + range 0 7 > + default 0 > + help > + > + Select the maximum printk verbosity level to be compiled into > + the kernel. > + > + Messages above the specified verbosity level are removed from > + the kernel at compile time. This reduces the kernel image size > + at the cost of a calmer kernel. > + > + Possible verbosity levels are listed below. Note that messages > + without an explicit loglevel will be classified as KERN_WARNING. > + > + 0 Disable this feature and compile all messages in. > + > + 1 KERN_ALERT /* action must be taken immediately */ > + 2 KERN_CRIT /* critical conditions */ > + 3 KERN_ERR /* error conditions */ > + 4 KERN_WARNING /* warning conditions */ > + 5 KERN_NOTICE /* normal but significant condition */ > + 6 KERN_INFO /* informational */ > + 7 KERN_DEBUG /* debug-level messages */ > + > + If unsure, just move on and leave this option alone. > + > config BUG > bool "BUG() support" if EMBEDDED > default y If there are some problems to handle KERN_CONT you should say something here. You should even add in cc: the kernel ML, however it seems a good work. Marco -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
