public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	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 12:43:40 +0100	[thread overview]
Message-ID: <1295437420.28776.4.camel@laptop> (raw)
In-Reply-To: <1295419594-13085-1-git-send-email-sboyd@codeaurora.org>

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, how about you look at
the output of:

grep -e "^cpu" -e "nohz" /proc/timer_list

instead?

>  kernel/time/tick-sched.c |    5 ++++-
>  1 files changed, 4 insertions(+), 1 deletions(-)
> 
> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> index 3e216e0..6c012c5 100644
> --- a/kernel/time/tick-sched.c
> +++ b/kernel/time/tick-sched.c
> @@ -795,8 +795,11 @@ void tick_setup_sched_timer(void)
>  	}
>  
>  #ifdef CONFIG_NO_HZ
> -	if (tick_nohz_enabled)
> +	if (tick_nohz_enabled) {
>  		ts->nohz_mode = NOHZ_MODE_HIGHRES;
> +		pr_info("Switched to NOHz mode on CPU #%d\n",
> +				smp_processor_id());
> +	}
>  #endif
>  }
>  #endif /* HIGH_RES_TIMERS */



  reply	other threads:[~2011-01-19 11:43 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 [this message]
2011-01-19 12:04   ` Ingo Molnar
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=1295437420.28776.4.camel@laptop \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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