From: Jan Glauber The least significant bit of the TOD clock value returned by get_clock is the 4096th part of a microsecond. To get to nanoseconds the value needs to be divided by 4096 and multiplied with 1000. The current method multiplies first and then shifts the value to make the result as precise as possible. The disadvantage is that the multiplication with 1000 will overflow shortly after 52 days. sched_clock is used by the scheduler for time stamp deltas, if an overflow occurs between two time stamps the scheduler will get confused. With the patch the problem occurs only after approx. one year, so the chance to run into this overflow is extremly low. Signed-off-by: Jan Glauber Signed-off-by: Martin Schwidefsky Signed-off-by: Heiko Carstens Signed-off-by: Andrew Morton --- arch/s390/kernel/time.c | 2 +- 1 files changed, 1 insertion(+), 1 deletion(-) diff -puN arch/s390/kernel/time.c~s390-overflow-in-sched_clock arch/s390/kernel/time.c --- devel/arch/s390/kernel/time.c~s390-overflow-in-sched_clock 2006-01-18 20:11:28.000000000 -0800 +++ devel-akpm/arch/s390/kernel/time.c 2006-01-18 20:11:28.000000000 -0800 @@ -61,7 +61,7 @@ extern unsigned long wall_jiffies; */ unsigned long long sched_clock(void) { - return ((get_clock() - jiffies_timer_cc) * 1000) >> 12; + return ((get_clock() - jiffies_timer_cc) * 125) >> 9; } void tod_to_timeval(__u64 todval, struct timespec *xtime) _