From: Nicolas Pitre <nico@fluxnic.net>
To: Rob Herring <robherring2@gmail.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Will Deacon <Will.Deacon@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: Tue, 14 May 2013 19:56:51 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.03.1305141945160.31158@syhkavp.arg> (raw)
In-Reply-To: <CAL_Jsq+Q5UMGo3J+vKKCRU+w4Kj0YN0exs7UCWTEOxmFjWfo3g@mail.gmail.com>
On Tue, 14 May 2013, Rob Herring wrote:
> On Tue, May 14, 2013 at 2:54 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
> > [ Yes, I'm late to the party ]
> >
> > On Tue, 7 May 2013, Marc Zyngier wrote:
> >
> >> On 07/05/13 00:16, Pavel Machek wrote:
> >>
> >> Hi Pawel,
> >>
> >> >> Now that we support a timer-backed delay loop, I'm quickly getting sick
> >> >> and tired of people complaining that their beloved bogomips value has
> >> >> decreased. You know who you are!
> >> >
> >> >> Unfortunately, we can't just remove the entry from /proc/cpuinfo, as it
> >> >> will likely break fragile userspace code which is parsing that stuff, so
> >> >> instead replace it with a dummy value that can be chosen in the
> >> >> Kconfig.
> >> >
> >> > So, instead of removing it you silently report invalid value? Note
> >>
> >> Removing it would be an ABI breakage. Unfortunately.
> >
> > Did you really write this with a straight face?
> >
> >> Name one userspace application that extracts meaningful information out
> >> of the BogoMIPS field. Just one.
> >
> > 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?
> I agree reporting BogoMIPS is silly, but there
> are more differences between x86 and ARM. Somewhat meaningful fields
> like "cpu MHz" are missing on ARM for example. These are mainly useful
> for h/w inventory use which server folks tend to care about.
So... the tool must be coping well with missing fields already? If
/proc/cpuinfo is missing "important" fields on ARM then this is a
different issue.
> > This thread must be a joke. Please just kill the damn thing out of
> > /proc/cpuinfo and see if any application notices. And if some do then
> > they are already broken *today* and should be fixed.
>
> And please do so for all arches then.
Why? It happens that the bogomips reporting on ARM is even more
"broken" than on other architectures and therefore it deserves to be
removed even more than on other architectures. Who knows, maybe it
still has some semblance of a meaning on those other architectures and
that should be up to their respective maintainers to decide.
Nicolas
next prev parent reply other threads:[~2013-05-14 23:57 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 [this message]
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=alpine.LFD.2.03.1305141945160.31158@syhkavp.arg \
--to=nico@fluxnic.net \
--cc=Will.Deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--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®