diff options
author | Ingo Molnar <mingo@elte.hu> | 2009-02-26 23:21:59 +0300 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2009-02-26 23:21:59 +0300 |
commit | 5d0859cef29167d45dc6cf89d19712145e6005d6 (patch) | |
tree | 1fe3be14cc773f4df5606a9993930cc43889a169 /include | |
parent | 14131f2f98ac350ee9e73faed916d2238a8b6a0d (diff) | |
parent | 83ce400928680a6c8123d492684b27857f5a2d95 (diff) | |
download | linux-5d0859cef29167d45dc6cf89d19712145e6005d6.tar.xz |
Merge branch 'sched/clock' into tracing/ftrace
Conflicts:
kernel/sched_clock.c
Diffstat (limited to 'include')
-rw-r--r-- | include/linux/sched.h | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/include/linux/sched.h b/include/linux/sched.h index 426666dd8203..7702cb166e08 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -1672,6 +1672,16 @@ static inline int set_cpus_allowed(struct task_struct *p, cpumask_t new_mask) return set_cpus_allowed_ptr(p, &new_mask); } +/* + * Architectures can set this to 1 if they have specified + * CONFIG_HAVE_UNSTABLE_SCHED_CLOCK in their arch Kconfig, + * but then during bootup it turns out that sched_clock() + * is reliable after all: + */ +#ifdef CONFIG_HAVE_UNSTABLE_SCHED_CLOCK +extern int sched_clock_stable; +#endif + extern unsigned long long sched_clock(void); extern void sched_clock_init(void); |