From: Will Deacon <will.deacon@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: marc.zyngier@arm.com, linux-kernel@vger.kernel.org,
Will Deacon <will.deacon@arm.com>
Subject: [RFC PATCH 0/2] ARM: Remove any correlation between IPC and BogoMips value
Date: Fri, 3 May 2013 18:35:45 +0100 [thread overview]
Message-ID: <1367602547-19322-1-git-send-email-will.deacon@arm.com> (raw)
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'.
After some education, they usually give in, but I figured it could be
solved by removing the reporting of this number to userspace altogether.
Unfortunately, that affects the output of /proc/cpuinfo, which I'm not
comfortable changing, so instead I've written this slightly tongue-in-cheek
series reporting obviously bogus values in those fields in the hope that
people don't interpret them as anything meaningful.
Comments welcome,
Will
Will Deacon (2):
ARM: delay: print dummy values for bogomips
init: calibrate: don't print out bogomips value on boot
arch/arm/Kconfig.debug | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
arch/arm/kernel/setup.c | 16 ++++++++--------
arch/arm/kernel/smp.c | 13 ++-----------
init/calibrate.c | 8 +++-----
4 files changed, 61 insertions(+), 24 deletions(-)
--
1.8.2.2
next reply other threads:[~2013-05-03 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 17:35 Will Deacon [this message]
2013-05-03 17:35 ` [RFC PATCH 1/2] ARM: delay: print dummy values for bogomips Will Deacon
2013-05-06 23:16 ` Pavel Machek
2013-05-07 8:17 ` Marc Zyngier
2013-05-14 19:54 ` Nicolas Pitre
2013-05-14 22:23 ` Rob Herring
2013-05-14 23:56 ` Nicolas Pitre
2013-05-15 9:01 ` Will Deacon
2013-05-15 11:47 ` Pavel Machek
2013-05-15 12:34 ` Nicolas Pitre
2013-05-20 9:59 ` Pavel Machek
2013-05-03 17:35 ` [RFC PATCH 2/2] init: calibrate: don't print out bogomips value on boot Will Deacon
2013-05-06 18:01 ` [RFC PATCH 0/2] ARM: Remove any correlation between IPC and BogoMips value Christopher Covington
2013-05-07 9:08 ` Will Deacon
2013-05-07 15:48 ` Christopher Covington
2013-05-08 9:06 ` Will Deacon
2013-05-13 15:14 ` Christopher Covington
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=1367602547-19322-1-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
/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
Powered by JetHome