From: Will Deacon <will.deacon@arm.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Rob Herring <robherring2@gmail.com>,
Marc Zyngier <Marc.Zyngier@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Pavel Machek <pavel@ucw.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 1/2] ARM: delay: print dummy values for bogomips
Date: Wed, 15 May 2013 10:01:03 +0100 [thread overview]
Message-ID: <20130515090103.GA12907@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <alpine.LFD.2.03.1305141945160.31158@syhkavp.arg>
Hi Nico,
On Wed, May 15, 2013 at 12:56:51AM +0100, Nicolas Pitre wrote:
> On Tue, 14 May 2013, Rob Herring wrote:
> > On Tue, May 14, 2013 at 2:54 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
> > > Waitaminute... Didn't you just claim this would be an ABI break?
> > >
> > > So if no application can be found, where is the ABI breakage?
> >
> > lscpu
> >
> > But that is already "broken" on ARM because x86 uses "bogomips" and
> > ARM uses "BogoMIPS".
>
> So basically it won't be any more broken if the field disappears
> entirely, right?
It's not these sort of tools I was worried about. I was thinking about the
possibility of badly written parsers which want some other field from
cpuinfo, but use the bogomips line for context. Do these applications exist?
No idea.
My second (less stupid) version of the patch prints "not reported". I'd be
happy to remove the line altogether if people get behind the decision though.
In fact, I just tried it and at least my linaro filesystem seems happy
enough.
Will
next prev parent reply other threads:[~2013-05-15 9:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 17:35 [RFC PATCH 0/2] ARM: Remove any correlation between IPC and BogoMips value Will Deacon
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 [this message]
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=20130515090103.GA12907@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=pavel@ucw.cz \
--cc=robherring2@gmail.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
all inboxes | Powered by JetHome®