public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Linaro Networking <linaro-networking@linaro.org>
Subject: Re: [QUERY]: Is using CPU hotplug right for isolating CPUs?
Date: Mon, 20 Jan 2014 16:51:46 +0100	[thread overview]
Message-ID: <20140120155145.GB9436@localhost.localdomain> (raw)
In-Reply-To: <CAKohpond3wY25H_tsJQ9xs_D2dP2_wGGU5J8fBteyfB=7wmAdA@mail.gmail.com>

On Mon, Jan 20, 2014 at 05:00:20PM +0530, Viresh Kumar wrote:
> On 16 January 2014 15:16, Thomas Gleixner <tglx@linutronix.de> wrote:
> > Just do the math.
> >
> >      max reload value / timer freq = max time span
> 
> Thanks.
> 
> > So:
> >
> >      0x7fffffff / 24MHz = 89.478485 sec
> >
> > Nothing to do here except to get rid of the requirement to arm the
> > timer at all.
> 
> @Frederic: Any inputs on how to get rid of this timer here?

I fear you can't. If you schedule a timer in 4 seconds away and your clockdevice
can only count up to 2 seconds, you can't help much the interrupt in the middle to
cope with the overflow.

So you need to act on the source of the timer:

* identify what cause this timer
* try to turn that feature off
* if you can't then move the timer to the housekeeping CPU

I'll have a look into the latter point to affine global timers to the
housekeeping CPU. Per cpu timers need more inspection though. Either we rework
them to be possibly handled by remote/housekeeping CPUs, or we let the associate feature
to be turned off. All in one it's a case by case work.

  reply	other threads:[~2014-01-20 15:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  9:27 [QUERY]: Is using CPU hotplug right for isolating CPUs? Viresh Kumar
2014-01-15 10:38 ` Peter Zijlstra
2014-01-15 10:47   ` Viresh Kumar
2014-01-15 11:34     ` Peter Zijlstra
2014-02-28  9:04       ` Viresh Kumar
2014-01-15 17:17 ` Frederic Weisbecker
     [not found]   ` <CAKohponEZydR1OmP2xziA9bc3OJPgP3bFmuWFQmrmeQFZccMVQ@mail.gmail.com>
2014-01-16  9:46     ` Thomas Gleixner
2014-01-20 11:30       ` Viresh Kumar
2014-01-20 15:51         ` Frederic Weisbecker [this message]
2014-01-21 10:33           ` Viresh Kumar
2014-01-23 14:58             ` Frederic Weisbecker
2014-01-24  5:21               ` Viresh Kumar
2014-01-24  8:29                 ` Mike Galbraith
2014-01-28 13:23                 ` Frederic Weisbecker
2014-01-28 16:11                   ` Kevin Hilman
2014-02-03  8:26                     ` Viresh Kumar
2014-02-11  8:52                   ` Viresh Kumar
2014-02-13 14:20                     ` Frederic Weisbecker
2014-01-20 13:59 ` Lei Wen
2014-01-20 15:00   ` Viresh Kumar
2014-01-20 15:41     ` Frederic Weisbecker
2014-01-21  2:07       ` Lei Wen
2014-01-21  9:50         ` Viresh Kumar
2014-01-23 13:54         ` Frederic Weisbecker
2014-01-23 14:27           ` Viresh Kumar
2014-01-21  9:49       ` Viresh Kumar
2014-01-23 14:01         ` Frederic Weisbecker
2014-01-24  8:53           ` Viresh Kumar

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=20140120155145.GB9436@localhost.localdomain \
    --to=fweisbec@gmail.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linaro-networking@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox