From: Viresh Kumar <viresh.kumar@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Kevin Hilman <khilman@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH V2 0/2] clockevents: Stop unused clockevent devices
Date: Thu, 7 May 2015 13:20:30 +0530 [thread overview]
Message-ID: <CAKohpokyHvwB=DGem+cwY5P9iLsMLa8eqmdP3cHRbcKSyn7SYg@mail.gmail.com> (raw)
In-Reply-To: <cover.1428031396.git.viresh.kumar@linaro.org>
On 3 April 2015 at 09:04, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> Hi,
>
> A clockevent device is used to service timers/hrtimers requests and the next
> event (when it should fire) is decided by the timer/hrtimer expiring next. When
> no timers/hrtimers are pending to be serviced, the expiry time is set to a
> special value: KTIME_MAX.
>
> This would normally happen with NO_HZ_{IDLE|FULL} in both LOWRES/HIGHRES modes.
>
> When 'expiry == KTIME_MAX', we either cancel the 'tick-sched' hrtimer
> (NOHZ_MODE_HIGHRES) or skip reprogramming clockevent device (NOHZ_MODE_LOWRES).
> But, the clockevent device is already reprogrammed from the tick-handler for
> next tick.
>
> As the clock event device is programmed in ONESHOT mode it will at least fire
> one more time (unnecessarily). Timers on few implementations (like
> arm_arch_timer, etc.) only support PERIODIC mode and their drivers emulate
> ONESHOT over that. Which means that on these platforms we will get spurious
> interrupts periodically (at last programmed interval rate, normally tick rate).
>
> In order to avoid spurious interrupts, the unused clockevent device should be
> stopped or its interrupts should be masked.
>
> Thomas suggested to add an optional state ONESHOT_STOPPED to solve this problem:
> lkml.org/lkml/2014/5/9/508.
>
> First patch implements the required infrastructure to start/stop clockevent
> device. The second patch stops/starts clockevent devices as and when required.
>
> It is also pushed here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/linux.git tick/oneshot-stopped
>
> @Preeti: I have applied your Reviewed-by only for the first commit as others
> have changed significantly. Feel free to give it again :)
>
> V1->V2:
> - Peter & Ingo suggested to to start/stop clockevent device from
> tick_program_event() instead of the call sites that called
> tick_program_event().
Hi Thomas,
Gentle reminder ping...
--
viresh
prev parent reply other threads:[~2015-05-07 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 3:34 [PATCH V2 0/2] clockevents: Stop unused clockevent devices Viresh Kumar
2015-04-03 3:34 ` [PATCH V2 1/2] clockevents: Introduce CLOCK_EVT_STATE_ONESHOT_STOPPED state Viresh Kumar
2015-05-19 14:39 ` [tip:timers/core] " tip-bot for Viresh Kumar
2015-04-03 3:34 ` [PATCH V2 2/2] Clockevents: Stop unused clockevent devices Viresh Kumar
2015-05-19 14:39 ` [tip:timers/core] clockevents: " tip-bot for Viresh Kumar
2015-05-07 7:50 ` Viresh Kumar [this message]
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='CAKohpokyHvwB=DGem+cwY5P9iLsMLa8eqmdP3cHRbcKSyn7SYg@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=fweisbec@gmail.com \
--cc=khilman@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=preeti@linux.vnet.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).