[PATCH 2.6.21-rt2] PowerPC: decrementer clockevent driver
paubert at iram.es
Tue Jul 10 20:52:12 EST 2007
On Fri, May 18, 2007 at 05:52:45PM +0100, Matt Sealey wrote:
> Kumar Gala wrote:
> > On May 18, 2007, at 9:48 AM, Thomas Gleixner wrote:
> >> On Fri, 2007-05-18 at 15:28 +0100, Matt Sealey wrote:
> >>> I think both the MPC52xx GPT0-7 and the SLT0-1 fulfil this fairly
> >>> easily.
> >> There is some basic work for MPC5200 available:
> >> http://www.pengutronix.de/oselas/bsp/phytec/index_en.html#phyCORE-MPC5200B-tiny
> > I asked this earlier, but figured you might have a better insight. Is
> > their value in having 'drivers' for more than one clock source? I'd say
> > most (of not all) the PPC SoCs have timers on the system side that we
> > could provide drivers for, I'm just not sure if that does anything for
> > anyone.
> As I asked after, I'm also very intrigued as to what is going to end
> up using these timers, but likewise, not much use writing a driver if
> everyone can use the extremely high resolution decrementer all at
> As I said before too, at least Intel has decided there is a great need
> for up to 256 high resolution timer sources on a system, but since this
> is a fairly new concept to Linux (and hrtimers and dynticks too) it
> only seems to be used in the case of i8254/RTC emulation, mostly on
> I'm looking at it now and finding "users" of hrtimers is looking very
> thin on the ground. Maybe it's justified on the basis that more is
> better, and having support is preferable to not having it (even if
> nobody really uses it) but it seems the entire gamut of timing
> possibility in Linux can be handled through a simple, and single,
> high resolution timer and a queue of events..
> So do we need some more? :D
I don't think so. I really wonder what other capabilities the
other clock sources bring, except more convoluted and complex
code in the end.
There may be one exception to it: scheduled wakeup with
very deep sleep in which you can't even afford the power
dissipated by the processor in the modes in with the
timebase/decrementer keeps running (which is fairly low
to start with). But this would be a special wakeup path
where timebase and decrementer are reinitialized and
become again the main timer source.
Otherwise the decrementer can provide essentially arbitrary
high resolution (i.e., comparable to the time of an external
bus access) on a fairly large number of independent timers.
This scales with the number of processors since there is one
decrementer per core (is it per thread on SMT chips?
I don't know).
A few months ago, I implemented here for out internal needs
the equivalent of HRT (I called them FGT for fine-grained timers)
for our VME machines still running a 2.2 kernel. We have boards
who should have generated regular interrupts at programmable
rate interpreting GPS timestamp signals (IRIG B). Unfortunately
the signals were sometimes corrupt and the interrupts were no
more regularly spaced. Now the IRIGB signal is only used to feed
NTP which acts as a low pass filter with an extremely small
cut-off frequency (1mHz or less) and the regular interrupts
are generated from the decrementer in parallel with the standard
ticks. The code is not really polished and would not scale to
a large number of timers but it took me about one day and a half
to write and debug it. I can even monitor it from a /proc file:
[root at vac1 /root]# cat /proc/fgtimer
Calls Lost Name
60865181 158 System timer tick
77889762 0 itFast (128Hz)
There are a few lost ticks for the main system timer because
some operations mask interrupts for too long during early
boot, especially with root on NFS which is the case here,
they never happen after the root file system is mounted.
This is also a somewhat special 2.2 kernel, it essentially has
the timekeeping code I submitted for 2.4 and which is
still the core of PPC timekeeping.
More information about the Linuxppc-dev