All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rado Vrbovsky <rvrbovsk@redhat.com>
To: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Subject: [PATCH] time: Change log level of "NOHZ: local_softirq_pending" message
Date: Fri, 8 Feb 2013 12:37:30 -0500 (EST)	[thread overview]
Message-ID: <2037057938.893524.1360345050772.JavaMail.root@redhat.com> (raw)
In-Reply-To: <350315726.726339.1360327201303.JavaMail.root@redhat.com>

The "NOHZ: local_softirq_pending" message is a largely informational message.
This makes extra work for customers that have a policy of investigating all
kernel log messages logged at <= KERN_ERR log level.
This patch sets the message to a different log level.

Signed-off-by: Rado Vrbovsky <rvrbovsk@redhat.com>

---
 kernel/time/tick-sched.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index d58e552..ece2beb 100644
--- a/kernel/time/tick-sched.c
+++ b/kernel/time/tick-sched.c
@@ -481,7 +481,7 @@ static bool can_stop_idle_tick(int cpu, struct tick_sched *ts)
 
                if (ratelimit < 10 &&
                    (local_softirq_pending() & SOFTIRQ_STOP_IDLE_MASK)) {
-                       printk(KERN_ERR "NOHZ: local_softirq_pending %02x\n",
+                       printk(KERN_WARNING "NOHZ: local_softirq_pending %02x\n",
                               (unsigned int) local_softirq_pending());
                        ratelimit++;
                }
-- 
1.7.11.7

       reply	other threads:[~2013-02-08 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <350315726.726339.1360327201303.JavaMail.root@redhat.com>
2013-02-08 17:37 ` Rado Vrbovsky [this message]
2013-03-25  9:58   ` [tip:timers/core] tick: Change log level of NOHZ: local_softirq_pending message tip-bot for Rado Vrbovsky

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=2037057938.893524.1360345050772.JavaMail.root@redhat.com \
    --to=rvrbovsk@redhat.com \
    --cc=dzickus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@redhat.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 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.