From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: Architecture specific implementations for tickless kernel and deferrable timers
Date: Wed, 27 Apr 2011 10:17:14 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1104271015000.3323@ionos> (raw)
In-Reply-To: <BANLkTi=Y0CdRt1ktCs7NwG4pLqWeZeLQPg@mail.gmail.com>
On Wed, 27 Apr 2011, Vikram Narayanan wrote:
> On Wed, Apr 27, 2011 at 2:07 AM, Russell King - ARM Linux
> > The only way to have a stable time source is to have a stable clocksource
> > - one which is never stopped or otherwise messed around with. ?If you
> > try to combine clocksource and clockevent with one-shot mode, where
> > the clocksource part is reset each time a new event is set, you'll probably
> > soon end up with time going screwy.
> >
> Thanks for the insight.
> My another question is that, where can I find some examples of dynamic
> tick implementation. Are there any documents for implementing the
> functionality?
> Also the struct dyn_tick_timer in the file include/asm-arm/mach/time.h
> is removed since 2.6.27. So how do I achieve this?
> If you refer me to some documentation on this, that would be great.
Provide a functional clocksource plus a clockevent device which is
oneshot capable. Enable CONFIG_NOHZ and there you go.
Thanks,
tglx
next prev parent reply other threads:[~2011-04-27 8:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 18:15 Architecture specific implementations for tickless kernel and deferrable timers Vikram Narayanan
2011-04-22 3:13 ` Jeff Ohlstein
2011-04-24 14:20 ` Vikram Narayanan
2011-04-26 20:37 ` Russell King - ARM Linux
2011-04-27 3:30 ` Vikram Narayanan
2011-04-27 7:25 ` Russell King - ARM Linux
2011-04-27 8:17 ` Thomas Gleixner [this message]
2011-04-28 13:31 ` Vikram Narayanan
2011-04-28 13:38 ` Russell King - ARM Linux
2011-04-28 13:54 ` Vikram Narayanan
2011-04-28 14:28 ` Russell King - ARM Linux
2011-04-28 17:29 ` Vikram Narayanan
2011-04-28 18:24 ` Russell King - ARM Linux
2011-04-29 14:26 ` Vikram Narayanan
2011-04-29 14:34 ` Russell King - ARM Linux
2011-04-29 15:07 ` Vikram Narayanan
2011-04-29 17:05 ` Thomas Gleixner
2011-04-29 17:05 ` Thomas Gleixner
2011-04-29 17:57 ` john stultz
2011-05-03 2:17 ` Vikram Narayanan
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=alpine.LFD.2.02.1104271015000.3323@ionos \
--to=tglx@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.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