Re: [Xen-ia64-devel] [PATCH] fix oops message from timer_interru

On Tue, 2007-01-23 at 16:44 -0500, Aron Griffis wrote:
> Atsushi SAKAI wrote:  [Mon Jan 22 2007, 07:36:55PM EST]
> > Oops: timer tick before it's due (itc=ed98bb5849,itm=ed98bb5849)
> > Oops: timer tick before it's due (itc=f20bca8ca3,itm=f20bca8ca3)
> > Oops: timer tick before it's due (itc=f4ea4e2b32,itm=f4ea4e2b32)
> ...
> > 
> > These oops messages are generated
> > because timer_interrupt checks the condition itc > itm.
> 
> Is that the right comparison though?  itc isn't guaranteed to return
> different values on subsequent fetches, and the interrupt is generated
> when itc == itm, right?  So shouldn't the condition be itc >= itm?

   Good point.  With the slower ITC on a Montecito system, I don't know
if anything would prevent you hitting the interrupt handler when itc ==
itm.  Perhaps a Montecito fix for Linux-ia64 to use time_after_eq()
would eliminate this problem.

        Alex
-- 
Alex Williamson                             HP Open Source & Linux Org.


_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [Xen-ia64-devel] [PATCH] fix oops message from timer_interrupt on VTI domain, Aron Griffis

Next by Date:

Re: [Xen-ia64-devel][Patch] Clean patch (clean VLIDATE_VT), Alex Williamson

Previous by Thread:

Re: [Xen-ia64-devel] [PATCH] fix oops message from timer_interrupt on VTI domain, Aron Griffis

Next by Thread:

Re: [Xen-ia64-devel] [PATCH] fix oops message from timer_interrupton VTI domain, Atsushi SAKAI

Indexes:

[Date] [Thread] [Top] [All Lists]