From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
tglx <tglx@linutronix.de>
Subject: Re: [PATCH] sched: Notify hrtimer users of switches to NOHZ mode
Date: Wed, 19 Jan 2011 13:04:12 +0100 [thread overview]
Message-ID: <20110119120412.GA3527@elte.hu> (raw)
In-Reply-To: <1295437420.28776.4.camel@laptop>
* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Tue, 2011-01-18 at 22:46 -0800, Stephen Boyd wrote:
> > When NOHZ=y and high res timers are disabled (via cmdline or
> > Kconfig) tick_nohz_switch_to_nohz() will notify the user about
> > switching into NOHZ mode. Nothing is printed for the case where
> > HIGH_RES_TIMERS=y. Fix this for the HIGH_RES_TIMERS=y case by
> > duplicating the printk from the low res NOHZ path in the high res
> > NOHZ path.
> >
> > Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> > ---
> >
> > This confused me since I was thinking 'dmesg | grep -i NOHZ' would
> > tell me if NOHZ was enabled, but if I have hrtimers there is
> > nothing. If we don't do this we should probably remove the original
> > printk.
>
> I'm not quite sure we want _more_ dmesg chatter, [...]
Well, we used to have bugs in the past where the system locked up after changing the
main hrtimer mode, so the messages are useful.
This patch completes the messages in that sense and makes them consistent. If we
want to remove them altogether that would be another patch.
Thanks,
Ingo
next prev parent reply other threads:[~2011-01-19 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 6:46 [PATCH] sched: Notify hrtimer users of switches to NOHZ mode Stephen Boyd
2011-01-19 11:43 ` Peter Zijlstra
2011-01-19 12:04 ` Ingo Molnar [this message]
2011-01-19 19:03 ` [tip:timers/urgent] hrtimers: " tip-bot for Stephen Boyd
2011-01-19 19:09 ` tip-bot for Stephen Boyd
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=20110119120412.GA3527@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--cc=tglx@linutronix.de \
/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