forked from Minki/linux
parisc: Fix self-detected CPU stall warnings on Mako machines
The config option HAVE_UNSTABLE_SCHED_CLOCK is set automatically when compiling for SMP. There is no need to clear the stable-clock flag via clear_sched_clock_stable() when starting secondary CPUs, and even worse, clearing it triggers wrong self-detected CPU stall warnings on 64bit Mako machines. Signed-off-by: Helge Deller <deller@gmx.de> Cc: stable@vger.kernel.org # 4.7+
This commit is contained in:
parent
b391667eb4
commit
92420bd0d0
@ -226,12 +226,6 @@ void __init start_cpu_itimer(void)
|
||||
unsigned int cpu = smp_processor_id();
|
||||
unsigned long next_tick = mfctl(16) + clocktick;
|
||||
|
||||
#if defined(CONFIG_HAVE_UNSTABLE_SCHED_CLOCK) && defined(CONFIG_64BIT)
|
||||
/* With multiple 64bit CPUs online, the cr16's are not syncronized. */
|
||||
if (cpu != 0)
|
||||
clear_sched_clock_stable();
|
||||
#endif
|
||||
|
||||
mtctl(next_tick, 16); /* kick off Interval Timer (CR16) */
|
||||
|
||||
per_cpu(cpu_data, cpu).it_value = next_tick;
|
||||
|
Loading…
Reference in New Issue
Block a user