RE: [RFC] timer_interrupt: Avoid device timeouts by freezing time if system froze

I don't think that I've followed all the steps and proposed
solutions in this thread.  There are (at least) two issues to
try to solve when the system has been frozen for an extended
period of time (more than a few ticks):

1) The system clock (gettimeofday(2)) needs to catch up the
missed time.  We can either do this in one mighty bound, or
we can creep up on it.  Either is plausible (though each may
have its own issues for applications, neither should be
catastrophic as applications should already deal with jumping
and slewing time due to NTP and other agents setting the
system clock).

2) There are some pending timeouts from the interval of real
time that we skipped.  Dealing with these may be harder, as
some of them may be related to physical limitations of devices,
so almost any choice we make about these (call all the pending
timeouts immediately, call them at some accelerated rate, skip
them) may cause problems for some device driver.  I think to
make any progress on a solution here we need to restrict the
discussion to real device drivers that are currently in the
tree.  Otherwise we will rathole forever discussing theoretical
situations.

Any other issues?

-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html