mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: "Rafał Miłecki" <rafal@milecki.pl>
Cc: Rabin Vincent <rabin.vincent@axis.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Srinivas Kandagatla <srinivas.kandagatla@gmail.com>,
	tglx@linutronix.de, Patrice Chotard <patrice.chotard@st.com>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	Maxime Coquelin <maxime.coquelin@st.com>
Subject: Re: DIfferent BogoMIPS value after bbaa06702719 ("clocksource/drivers/arm_global_timer: Register delay timer")
Date: Thu, 2 Mar 2017 14:13:34 +0000	[thread overview]
Message-ID: <20170302141334.GM21222@n2100.armlinux.org.uk> (raw)
In-Reply-To: <d22ec429-1a71-e56f-e1d7-28b066be8c1b@milecki.pl>

On Thu, Mar 02, 2017 at 02:36:23PM +0100, Rafał Miłecki wrote:
> Hi,
> 
> I just updated kernel on my SmartRG SR400ac (bcm4708-smartrg-sr400ac.dts) from
> 4.4 to 4.9 and noticed that this part of the log:
> [    0.020820] Calibrating delay loop... 1594.16 BogoMIPS (lpj=7970816)
> (...)
> [    0.190806] Brought up 2 CPUs
> [    0.200022] SMP: Total of 2 processors activated (3188.32 BogoMIPS).
> 
> became:
> [    0.027082] Calibrating delay loop (skipped), value calculated using timer frequency.. 800.00 BogoMIPS (lpj=4000000)
> (...)
> [    0.078858] Brought up 2 CPUs
> [    0.088254] SMP: Total of 2 processors activated (1600.00 BogoMIPS).
> 
> This is caused by commit bbaa06702719 ("clocksource/drivers/arm_global_timer:
> Register delay timer").
> 
> Is this something expected?

Yes.

> Or should I be worried about this? I'm aware it's just BogoMIPS, but I
> still prefer to ask :)

It's *bogus*.  Bogomips is the calibration value that the kernel uses
to achieve delays.  It has nothing to do with the speed of the CPU on
modern systems that use a timer instead.  (In that case, it's a
calibration value for the timer, rather than a calibration value for
the number of software loops required to achieve a delay.)

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2017-03-02 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 13:36 Rafał Miłecki
2017-03-02 14:13 ` Russell King - ARM Linux [this message]
2017-03-02 17:46   ` Rafał Miłecki
2017-03-02 14:13 ` Rabin Vincent

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=20170302141334.GM21222@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=daniel.lezcano@linaro.org \
    --cc=hauke@hauke-m.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.coquelin@st.com \
    --cc=patrice.chotard@st.com \
    --cc=rabin.vincent@axis.com \
    --cc=rafal@milecki.pl \
    --cc=srinivas.kandagatla@gmail.com \
    --cc=tglx@linutronix.de \
    /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®