Subject: Re: Fixing sgimips clock behaviour
To: None <port-sgimips@netbsd.org, port-mips@netbsd.org>
From: Matt Thomas <matt@3am-software.com>
List: port-sgimips
Date: 02/26/2002 20:47:35
At 06:52 PM 2/26/2002 -0800, cgd@broadcom.com wrote:
>At Wed, 27 Feb 2002 02:14:44 +0000 (UTC), "Rafal Boni" wrote:
> > The following patch fixes it, but I'm still not sure what the right
> > thing to do is if the interrupt is so delayed that we'll miss the next
> > one -- I currently simply schedule the next clock interrupt the fixed
> > time from *now* to avoid complexity in figuring out how far we'd fallen
> > behind and adding in the right fugde factor.
>
>I think i've seen the following different methods used, at least:
>
>* figure out how many ticks should were missed, and call the
>appropriate interrupt-delivery function that many times.  (i.e.,
>bursty tick delivery when you have missed ticks.)

PowerPC uses this method.


-- 
Matt Thomas               Internet:   matt@3am-software.com
3am Software Foundry      WWW URL:    http://www.3am-software.com/bio/matt/
Cupertino, CA             Disclaimer: I avow all knowledge of this message