Explicitly have the timecounter init happen after the cpu_initclocks is

called.  Otherwise (depending on a non-deterministic sort), the timecounter
code can be initialized before the clock rate has been set (on ia64) and it
assumes hz = 100, rather than the real value of 1024.  I'm not sure how much
gets upset by this.

Glanced at by:	phk
This commit is contained in:
peter 2003-01-06 01:01:08 +00:00
parent ebd1aff2ab
commit ce24f8fa5f
2 changed files with 2 additions and 2 deletions

View File

@ -596,7 +596,7 @@ ntp_init()
#endif /* PPS_SYNC */
}
SYSINIT(ntpclocks, SI_SUB_CLOCKS, SI_ORDER_FIRST, ntp_init, NULL)
SYSINIT(ntpclocks, SI_SUB_CLOCKS, SI_ORDER_MIDDLE, ntp_init, NULL)
/*
* hardupdate() - local clock update

View File

@ -693,4 +693,4 @@ inittimecounter(void *dummy)
(void)timecounter->tc_get_timecount(timecounter);
}
SYSINIT(timecounter, SI_SUB_CLOCKS, SI_ORDER_FIRST, inittimecounter, NULL)
SYSINIT(timecounter, SI_SUB_CLOCKS, SI_ORDER_SECOND, inittimecounter, NULL)