diff options
| author | Peter Zijlstra <a.p.zijlstra@chello.nl> | 2008-05-03 18:29:28 +0200 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-05-05 23:56:18 +0200 |
| commit | 3e51f33fcc7f55e6df25d15b55ed10c8b4da84cd (patch) | |
| tree | 3752f9ea8e014ec40e95a1b197b0a3d18e1056a8 /init | |
| parent | a5574cf65b5f03ce9ade3918764fe22e5e2371e3 (diff) | |
| download | kernel_samsung_espresso10-3e51f33fcc7f55e6df25d15b55ed10c8b4da84cd.zip kernel_samsung_espresso10-3e51f33fcc7f55e6df25d15b55ed10c8b4da84cd.tar.gz kernel_samsung_espresso10-3e51f33fcc7f55e6df25d15b55ed10c8b4da84cd.tar.bz2 | |
sched: add optional support for CONFIG_HAVE_UNSTABLE_SCHED_CLOCK
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>
Diffstat (limited to 'init')
| -rw-r--r-- | init/main.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/init/main.c b/init/main.c index a87d4ca..ddada7a 100644 --- a/init/main.c +++ b/init/main.c @@ -602,6 +602,7 @@ asmlinkage void __init start_kernel(void) softirq_init(); timekeeping_init(); time_init(); + sched_clock_init(); profile_init(); if (!irqs_disabled()) printk("start_kernel(): bug: interrupts were enabled early\n"); |