From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: BogoMIPS change in 3.6+
Date: Thu, 31 Jan 2013 10:15:11 -0600 [thread overview]
Message-ID: <510A988F.6030508@gmail.com> (raw)
The BogoMIPS value has changed on highbank since the commit below in
3.6. It is now half the value it used to be. Does that matter other than
perception (I've checked that I'm not running at half the freq)?
Rob
commit d0a533b18235d36206b9b422efadb7cee444dfdb
Author: Will Deacon <will.deacon@arm.com>
Date: Fri Jul 6 15:47:17 2012 +0100
ARM: 7452/1: delay: allow timer-based delay implementation to be
selected
This patch allows a timer-based delay implementation to be selected by
switching the delay routines over to use get_cycles, which is
implemented in terms of read_current_timer. This further allows us to
skip the loop calibration and have a consistent delay function in the
face of core frequency scaling.
To avoid the pain of dealing with memory-mapped counters, this
implementation uses the co-processor interface to the architected timers
when they are available. The previous loop-based implementation is
kept around for CPUs without the architected timers and we retain both
the maximum delay (2ms) and the corresponding conversion factors for
determining the number of loops required for a given interval. Since the
indirection of the timer routines will only work when called from C,
the sa1100 sleep routines are modified to branch to the loop-based delay
functions directly.
next reply other threads:[~2013-01-31 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 16:15 Rob Herring [this message]
2013-01-31 16:21 ` BogoMIPS change in 3.6+ Arnd Bergmann
2013-01-31 16:23 ` Will Deacon
2013-01-31 20:57 ` Rob Herring
2013-01-31 16:24 ` Santosh Shilimkar
2013-01-31 16:25 ` Will Deacon
2013-01-31 16:31 ` Santosh Shilimkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=510A988F.6030508@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).