linux-mips
[Top] [All Lists]

Re: [RFC] Separate time support for using cpu timer

To: Jun Sun <jsun@mvista.com>
Subject: Re: [RFC] Separate time support for using cpu timer
From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Date: Wed, 21 Apr 2004 15:19:45 +0200 (CEST)
Cc: linux-mips@linux-mips.org
In-reply-to: <20040420162500.H22846@mvista.com>
Organization: Technical University of Gdansk
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20040419180720.H14976@mvista.com> <Pine.LNX.4.55.0404201522220.28193@jurand.ds.pg.gda.pl> <20040420162500.H22846@mvista.com>
Sender: linux-mips-bounce@linux-mips.org
On Tue, 20 Apr 2004, Jun Sun wrote:

> >  It makes it separate again -- more maintenance burden and a bigger
> > opportunity to have functional divergence, sigh...
> 
> Pretty much true for lots of improvement we made in the past a couple of
> years .... :)

 Hmm, s/improvement/hacks/, perhaps?

> >  Additionally I don't think using the CP0 Count & Compare registers for
> > the system timer is the way to go.  It's rather a way to escape when
> > there's no other possibility.  A lot of systems have a reliable external
> > timer interrupt source and using it actually would free the CP0 registers
> > for other uses, like profiling or a programmable interval timer.
> 
> I was rather neutral on this point until I started to add HRT/VST support to 
> MIPS.  When adding such features you really just want one common timer code.
> And the best choice for MIPS is cpu timer.

 Well, with the _hpt_ abstraction layer you have one common timer code,
regardless of the actual timer hardware used.  If there's some
functionality you miss there, we may discuss about possible solutions.

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

<Prev in Thread] Current Thread [Next in Thread>