On Thu, Oct 10, 2013 at 10:52:35PM +0100, Andrew Morton wrote:
> On Wed, 9 Oct 2013 15:57:20 +0100 Will Deacon wrote:
>
> > @@ -295,9 +295,7 @@ void calibrate_delay(void)
> > }
> > per_cpu(cpu_loops_per_jiffy, this_cpu) = lpj;
> > if (!printed)
> > - pr_cont("%lu.%02lu
On Thu, Oct 10, 2013 at 10:52:35PM +0100, Andrew Morton wrote:
On Wed, 9 Oct 2013 15:57:20 +0100 Will Deacon will.dea...@arm.com wrote:
@@ -295,9 +295,7 @@ void calibrate_delay(void)
}
per_cpu(cpu_loops_per_jiffy, this_cpu) = lpj;
if (!printed)
-
On Wed, 9 Oct 2013 15:57:20 +0100 Will Deacon wrote:
> @@ -295,9 +295,7 @@ void calibrate_delay(void)
> }
> per_cpu(cpu_loops_per_jiffy, this_cpu) = lpj;
> if (!printed)
> - pr_cont("%lu.%02lu BogoMIPS (lpj=%lu)\n",
> - lpj/(50/HZ),
> -
On Wed, 9 Oct 2013 15:57:20 +0100 Will Deacon will.dea...@arm.com wrote:
@@ -295,9 +295,7 @@ void calibrate_delay(void)
}
per_cpu(cpu_loops_per_jiffy, this_cpu) = lpj;
if (!printed)
- pr_cont(%lu.%02lu BogoMIPS (lpj=%lu)\n,
-
BogoMIPs is a confusing concept to the ill-informed, so allow
architectures to print it only if they find it worthwhile. The delay
calibration code should stick to lpj and avoid trying to draw any
correlation with BogoMIPs, which may be a fixed value derived from a
timer frequency independent of
BogoMIPs is a confusing concept to the ill-informed, so allow
architectures to print it only if they find it worthwhile. The delay
calibration code should stick to lpj and avoid trying to draw any
correlation with BogoMIPs, which may be a fixed value derived from a
timer frequency independent of
6 matches
Mail list logo