On Mon, May 06, 2013 at 07:01:23PM +0100, Christopher Covington wrote: > Hi Will, > > On 05/03/2013 01:35 PM, Will Deacon wrote: > > Hi all, > > > > This small patch set may look a little over a month late, but there is a > > serious reason for posting it. > > > > When I moved the ARM delay loop over to using the architected timers > > rather than the CPU spinning loop (which has all the problems associated > > with cpu frequency scaling and what-not) I thought I was doing something > > useful for the port. However, it turns out that a surprising number of > > people have complained, and continue to complain, about the drop in > > their `BogoMIPs score'. > > Have you considered adding the old code back in, but in a form that's not at > all referenced by the delay loop code and just calculates CPU-based bogomips?
That seems like a lot of effort in order to preserve something that isn't even meaningful. We might be better just zeroing the value, but then we'll inevitably get bug reports of it being `wrong'. Plus, the calibration during boot introduces a brief delay when onlining each core whereas this can be skipped when using a constant timer. Will -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/