From mboxrd@z Thu Jan  1 00:00:00 1970
From: tglx@linutronix.de (Thomas Gleixner)
Date: Wed, 27 Apr 2011 10:17:14 +0200 (CEST)
Subject: Architecture specific implementations for tickless kernel and
	deferrable timers
In-Reply-To: <BANLkTi=Y0CdRt1ktCs7NwG4pLqWeZeLQPg@mail.gmail.com>
References: <BANLkTi=q8-1ybXNky04A6WA7+VA5ZgOB-g@mail.gmail.com>
	<4DB0F249.6000307@codeaurora.org>
	<BANLkTinkkMkyy3OnSiOqgUBHiytFPparbQ@mail.gmail.com>
	<20110426203756.GD17290@n2100.arm.linux.org.uk>
	<BANLkTi=Y0CdRt1ktCs7NwG4pLqWeZeLQPg@mail.gmail.com>
Message-ID: <alpine.LFD.2.02.1104271015000.3323@ionos>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

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