linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/2] ARM: Remove any correlation between IPC and BogoMips value
Date: Mon, 13 May 2013 11:14:06 -0400	[thread overview]
Message-ID: <5191033E.2000303@codeaurora.org> (raw)
In-Reply-To: <20130508090644.GA15692@mudshark.cambridge.arm.com>

Hi Will,

On 05/08/2013 05:06 AM, Will Deacon wrote:
> Hello Christopher,
> 
> On Tue, May 07, 2013 at 04:48:26PM +0100, Christopher Covington wrote:
>> On 05/07/2013 05:08 AM, Will Deacon wrote:
>>> That seems like a lot of effort in order to preserve something that isn't
>>> even meaningful. We might be better just zeroing the value, but then we'll
>>> inevitably get bug reports of it being `wrong'.
>>
>> If I were in to filing bug reports about bogomips values, I would be just as
>> likely to do it for 1, 10000, 99999, and get_random_bytes(...) as for 0.
> 
> That's a fair point, and one of the reasons I posted this as an RFC. I'd
> basically like an `obviously bogus' value so that people don't think `hey,
> my CPU sure it slow' and instead think `looks like this really is a bogus
> value after all'.
> 
> However, you're probably right that there isn't a number which can convey
> that information properly, so how about we just put a string in there along
> the lines of "not reported" and leave it at that?

That sounds reasonable to me.

Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

      reply	other threads:[~2013-05-13 15:14 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
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 [this message]

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=5191033E.2000303@codeaurora.org \
    --to=cov@codeaurora.org \
    --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).