All of lore.kernel.org
 help / color / mirror / Atom feed
* 11 bogomips at 500 MHz?
@ 2011-06-08 12:40 Meelis Roos
  2011-06-08 21:58 ` David Miller
  0 siblings, 1 reply; 2+ messages in thread
From: Meelis Roos @ 2011-06-08 12:40 UTC (permalink / raw)
  To: sparclinux

I see this on 500 MHz Fire V100.

[   59.253164] calibrate_delay_direct() timer_rate_maxU726 timer_rate_minU504 pre_start29128453 pre_end29184069
[   59.283196] calibrate_delay_direct() timer_rate_maxU721 timer_rate_minU503 pre_start29295308 pre_end29350920
[   59.313228] calibrate_delay_direct() timer_rate_maxU722 timer_rate_minU502 pre_start29462156 pre_end29517768
[   59.343261] calibrate_delay_direct() timer_rate_maxU723 timer_rate_minU505 pre_start29629002 pre_end29684616
[   59.373293] calibrate_delay_direct() timer_rate_maxU718 timer_rate_minU499 pre_start29795855 pre_end29851464
[   59.373349] Calibrating delay using timer specific routine.. 11.14 BogoMIPS (lpjU722)

11 bogomips seems ... slow. Older machines like Ultra 1, Ultra 5/10 show 
double the CPU clock speed as bogomips. Is it normal or is something 
clock-related broken?

cpu             : TI UltraSparc IIe (Hummingbird)
fpu             : UltraSparc IIe integrated FPU
pmu             : ultra12
prom            : OBP 4.0.18 2002/05/23 18:22
type            : sun4u
ncpus probed    : 1
ncpus active    : 1
D$ parity tl1   : 0
I$ parity tl1   : 0
Cpu0ClkTck      : 000000001dcd6500
MMU Type        : Spitfire

Netra X1 has it also similarly.

My dmesg logs go back to August 2008 and it has been the same always (at 
least at about 2.6.25), so it's not anything recent.

-- 
Meelis Roos (mroos@linux.ee)

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: 11 bogomips at 500 MHz?
  2011-06-08 12:40 11 bogomips at 500 MHz? Meelis Roos
@ 2011-06-08 21:58 ` David Miller
  0 siblings, 0 replies; 2+ messages in thread
From: David Miller @ 2011-06-08 21:58 UTC (permalink / raw)
  To: sparclinux

From: Meelis Roos <mroos@linux.ee>
Date: Wed, 8 Jun 2011 15:40:33 +0300 (EEST)

> I see this on 500 MHz Fire V100.
> 
> [   59.253164] calibrate_delay_direct() timer_rate_maxU726 timer_rate_minU504 pre_start29128453 pre_end29184069
> [   59.283196] calibrate_delay_direct() timer_rate_maxU721 timer_rate_minU503 pre_start29295308 pre_end29350920
> [   59.313228] calibrate_delay_direct() timer_rate_maxU722 timer_rate_minU502 pre_start29462156 pre_end29517768
> [   59.343261] calibrate_delay_direct() timer_rate_maxU723 timer_rate_minU505 pre_start29629002 pre_end29684616
> [   59.373293] calibrate_delay_direct() timer_rate_maxU718 timer_rate_minU499 pre_start29795855 pre_end29851464
> [   59.373349] Calibrating delay using timer specific routine.. 11.14 BogoMIPS (lpjU722)
> 
> 11 bogomips seems ... slow. Older machines like Ultra 1, Ultra 5/10 show 
> double the CPU clock speed as bogomips. Is it normal or is something 
> clock-related broken?

It has to do with what clock source we're using for timer interrupt
generation, and for this CPU we use the system TICK value which runs
at the bus clock speed and not the CPU clock speed.

Absolutely no interpretation of the bogomips value should ever be
made.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-06-08 21:58 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-06-08 12:40 11 bogomips at 500 MHz? Meelis Roos
2011-06-08 21:58 ` David Miller

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.