From: Marco Stornelli <marco.stornelli@gmail.com>
To: Marc Andre Tanner <mat@brain-dump.org>
Cc: linux-embedded@vger.kernel.org
Subject: Re: [PATCH 1/5] printk: introduce CONFIG_PRINTK_VERBOSITY
Date: Wed, 02 Sep 2009 18:44:06 +0200 [thread overview]
Message-ID: <4A9EA0D6.2030504@gmail.com> (raw)
In-Reply-To: <1251901505-4313-2-git-send-email-mat@brain-dump.org>
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@brain-dump.org>
> ---
> 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
next prev parent reply other threads:[~2009-09-02 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 14:25 [RFC|PATCHv2] Compile time printk verbosity Marc Andre Tanner
2009-09-02 14:25 ` [PATCH 1/5] printk: introduce CONFIG_PRINTK_VERBOSITY Marc Andre Tanner
2009-09-02 16:44 ` Marco Stornelli [this message]
2009-09-02 17:32 ` Marc Andre Tanner
2009-09-02 14:25 ` [PATCH 2/5] printk: move printk to the end of the file Marc Andre Tanner
2009-09-02 14:25 ` [PATCH 3/5] printk: introduce printk_unfiltered as an alias to printk Marc Andre Tanner
2009-09-02 14:25 ` [PATCH 4/5] char/mem: replace printk with printk_unfiltered Marc Andre Tanner
2009-09-02 14:25 ` [PATCH 5/5] printk: provide a filtering macro for printk Marc Andre Tanner
2009-09-02 16:44 ` Marco Stornelli
2009-09-02 17:27 ` Marc Andre Tanner
2009-09-03 6:29 ` Marco Stornelli
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=4A9EA0D6.2030504@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=mat@brain-dump.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.