All of lore.kernel.org
 help / color / mirror / Atom feed
From: Preeti Murthy <preeti.lkml@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
	Preeti U Murthy <preeti@linux.vnet.ibm.com>
Subject: Re: [Query]: tick-sched: why don't we stop tick when we are running idle task?
Date: Mon, 14 Apr 2014 15:18:30 +0530	[thread overview]
Message-ID: <CAM4v1pOWQFNaoc44b+7=hrYEzwiMMnhVFZnqfJEZiECuiquuEQ@mail.gmail.com> (raw)
In-Reply-To: <CAKohpomgv-LbUcPxazfJkf0Jq0sSULxT0WjrbFovn0k0O-ORwg@mail.gmail.com>

Hi Viresh,

I am not too sure about the complexity or the worthiness of this patch but
just wanted to add that care must be taken to migrate the tick_sched_timer
of all the remote CPUs off a hotplugged out CPU if the latter was keeping
their time thus far. In the normal scenario I am guessing the tick_sched_timer
dies along with the hotplugged out CPU since there is no need for it any more.

Regards
Preeti U Murthy

  reply	other threads:[~2014-04-14  9:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 10:33 [Query]: tick-sched: why don't we stop tick when we are running idle task? Viresh Kumar
2014-04-09 10:49 ` Viresh Kumar
2014-04-10 14:39   ` Frederic Weisbecker
2014-04-11 10:04     ` Viresh Kumar
2014-04-11 14:53       ` Frederic Weisbecker
2014-04-11 15:18         ` Peter Zijlstra
2014-04-11 16:38           ` Viresh Kumar
2014-04-14  9:48             ` Preeti Murthy [this message]
2014-04-14  9:51               ` Viresh Kumar
2014-04-14 11:02             ` Peter Zijlstra
2014-04-14 11:42               ` Viresh Kumar
2014-04-14 11:47                 ` Peter Zijlstra
2014-04-14 11:52                   ` Viresh Kumar
2014-04-14 12:06                     ` Peter Zijlstra
2014-04-15  6:04                       ` Viresh Kumar
2014-04-15  9:30                       ` Frederic Weisbecker
2014-04-15 10:52                         ` Peter Zijlstra
2014-04-15 10:53                           ` Peter Zijlstra
2014-04-23 11:12                         ` Viresh Kumar
2014-05-09  8:44                           ` Viresh Kumar
2014-05-13 23:30                             ` Frederic Weisbecker
2014-05-22  8:44                               ` Peter Zijlstra

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='CAM4v1pOWQFNaoc44b+7=hrYEzwiMMnhVFZnqfJEZiECuiquuEQ@mail.gmail.com' \
    --to=preeti.lkml@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=preeti@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=viresh.kumar@linaro.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.