Messages in this thread | | | Date | Thu, 2 Mar 2017 15:13:56 +0100 | From | Rabin Vincent <> | Subject | Re: DIfferent BogoMIPS value after bbaa06702719 ("clocksource/drivers/arm_global_timer: Register delay timer") |
| |
On Thu, Mar 02, 2017 at 02:36:23PM +0100, Rafał Miłecki wrote: > I just updated kernel on my SmartRG SR400ac (bcm4708-smartrg-sr400ac.dts) from > 4.4 to 4.9 and noticed that this part of the log: > [ 0.020820] Calibrating delay loop... 1594.16 BogoMIPS (lpj=7970816) > (...) > [ 0.190806] Brought up 2 CPUs > [ 0.200022] SMP: Total of 2 processors activated (3188.32 BogoMIPS). > > became: > [ 0.027082] Calibrating delay loop (skipped), value calculated using timer frequency.. 800.00 BogoMIPS (lpj=4000000) > (...) > [ 0.078858] Brought up 2 CPUs > [ 0.088254] SMP: Total of 2 processors activated (1600.00 BogoMIPS). > > This is caused by commit bbaa06702719 ("clocksource/drivers/arm_global_timer: > Register delay timer"). > > Is this something expected? Or should I be worried about this? I'm aware it's > just BogoMIPS, but I still prefer to ask :)
Yes, it's expected.
No, you shouldn't be worried.
It's even explained on Wikipedia: https://en.wikipedia.org/wiki/BogoMips#Timer-based_delays
You can run the udelay test (CONFIG_TEST_UDELAY) if you want to make sure that your delay loops are fine.
| |