On Mon, 30 Oct 2000, Vojtech Pavlik wrote:
> I don't think so. If you check the code paths more closely, you'll see
> that the timer is used even in the fast TSC case, the error causes by
> too big 'count' variable propagates up to the TSC routine. That's where
> I started hunting for the bug.
>
> So no, it wasn't a placebo effect. Put a printk() in the fix statement
> to see if it's triggered.
Mmmm. Okay. Maybe I fixed the 'wrong' place, but the place I 'fixed'
was in do_slow_gettimeoffset, which is inside #ifndef CONFIG_X86_TSC.
I'll compile with a printk in there at home tonight though.
*peers more closely* Ho-ho. I see. There's one further down in the
timer interrupt itself. Oops. My bad.
Cheers,
Mark
--
+-------------------------------------------------------------------------+
Mark Cooke The views expressed above are mine and are not
Systems Programmer necessarily representative of university policy
University Of Birmingham URL: http://www.sr.bham.ac.uk/~mpc/
+-------------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
