Re: [RFC PATCH 1/2] ARM: delay: print dummy values for bogomips

From: Pavel Machek
Date: Mon May 20 2013 - 05:59:14 EST


> > > In fact, I just tried it and at least my linaro filesystem seems happy
> > > enough.
> >
> > Would it be too much work to simply put the field back with the right
> > value? We don't have to get it as precise as we used to, that should
> > make slowdown minimum.
> There is simply no right value. And whenever there is a value, people
> read too much into it.

You are right that there is no right value. But there are many _wrong_

Take a look at CPU temperature. There's no right value there, either,
as CPU has different temperatures at different places. Displaying
heatsink temp +5C is probably ok. Displaying case temperature or
compile time constant is not.

Now, bogoMIPS is supposed to be instructions per second. Measure
instructions per second, and you have acceptable value to display. Put
back code from previous version, and you have acceptable value to

"0", "1" or value from Kconfig is _not_ acceptable value.

Maybe bogomips should not have been exposed in /proc in the first
place, but it is too late now. "No regressions".

(cesky, pictures)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at