Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/ https://git.shady.money/linux/atom?h=v2.6.26 2008-05-29T09:29:19Z 2008-05-29T09:29:19Z Peter Zijlstra a.p.zijlstra@chello.nl 2008-05-29T08:07:15Z urn:sha1:a381759d6ad5c5dea5a981918e0b4493e9b66ac7 Make sched_clock_cpu() return 0 before it has been initialized and avoid corrupting its state due to doing so. This fixes the weird printk timestamp jump reported. Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> 2008-05-05T21:56:18Z Peter Zijlstra a.p.zijlstra@chello.nl 2008-05-03T16:29:28Z urn:sha1:3e51f33fcc7f55e6df25d15b55ed10c8b4da84cd this replaces the rq->clock stuff (and possibly cpu_clock()). - architectures that have an 'imperfect' hardware clock can set CONFIG_HAVE_UNSTABLE_SCHED_CLOCK - the 'jiffie' window might be superfulous when we update tick_gtod before the __update_sched_clock() call in sched_clock_tick() - cpu_clock() might be implemented as: sched_clock_cpu(smp_processor_id()) if the accuracy proves good enough - how far can TSC drift in a single jiffie when considering the filtering and idle hooks? [ mingo@elte.hu: various fixes and cleanups ] Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Signed-off-by: Ingo Molnar <mingo@elte.hu>