From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: restore bogomips information in /proc/cpuinfo
Date: Thu, 19 Nov 2015 12:20:30 +0000 [thread overview]
Message-ID: <20151119122030.GE22786@arm.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1511181646090.22569@knanqh.ubzr>
On Wed, Nov 18, 2015 at 04:55:10PM -0500, Nicolas Pitre wrote:
> On Wed, 18 Nov 2015, Will Deacon wrote:
> > On Wed, Nov 18, 2015 at 10:15:05AM -0800, Yang Shi wrote:
> > > + loops_per_jiffy / (500000UL/HZ),
> > > + loops_per_jiffy / (5000UL/HZ) % 100);
>
> Also, given nobody ever relied on any prior value here, can we at least
> print something here with some semblance of a meaning i.e. something
> related to the actual CPU speed and not some separate useless constant
> timer clock please?
There's also an argument that a 32-bit application should see the same
BogoMIPS value under an arm64 kernel as an arm kernel running on the
same machine. But I was never clear about what this value was intended
to mean anyway, despite all the shouting :)
Right now, I'm happy with anything that fixes libvirt and backports
easily.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Yang Shi <yang.shi@linaro.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo
Date: Thu, 19 Nov 2015 12:20:30 +0000 [thread overview]
Message-ID: <20151119122030.GE22786@arm.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1511181646090.22569@knanqh.ubzr>
On Wed, Nov 18, 2015 at 04:55:10PM -0500, Nicolas Pitre wrote:
> On Wed, 18 Nov 2015, Will Deacon wrote:
> > On Wed, Nov 18, 2015 at 10:15:05AM -0800, Yang Shi wrote:
> > > + loops_per_jiffy / (500000UL/HZ),
> > > + loops_per_jiffy / (5000UL/HZ) % 100);
>
> Also, given nobody ever relied on any prior value here, can we at least
> print something here with some semblance of a meaning i.e. something
> related to the actual CPU speed and not some separate useless constant
> timer clock please?
There's also an argument that a 32-bit application should see the same
BogoMIPS value under an arm64 kernel as an arm kernel running on the
same machine. But I was never clear about what this value was intended
to mean anyway, despite all the shouting :)
Right now, I'm happy with anything that fixes libvirt and backports
easily.
Will
next prev parent reply other threads:[~2015-11-19 12:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:15 [PATCH] arm64: restore bogomips information in /proc/cpuinfo Yang Shi
2015-11-18 18:15 ` Yang Shi
2015-11-18 18:47 ` Will Deacon
2015-11-18 18:47 ` Will Deacon
2015-11-18 18:54 ` Shi, Yang
2015-11-18 18:54 ` Shi, Yang
2015-11-18 21:55 ` Nicolas Pitre
2015-11-18 21:55 ` Nicolas Pitre
2015-11-19 12:20 ` Will Deacon [this message]
2015-11-19 12:20 ` Will Deacon
2015-11-25 5:45 ` Jon Masters
2015-11-25 5:45 ` Jon Masters
2015-11-25 11:52 ` Catalin Marinas
2015-11-25 11:52 ` Catalin Marinas
2015-11-25 12:00 ` Russell King - ARM Linux
2015-11-25 12:00 ` Russell King - ARM Linux
2015-11-25 12:36 ` Riku Voipio
2015-11-25 12:36 ` Riku Voipio
2015-11-25 15:16 ` Nicolas Pitre
2015-11-25 15:16 ` Nicolas Pitre
2015-11-25 17:32 ` Shi, Yang
2015-11-25 17:32 ` Shi, Yang
2015-11-25 18:09 ` Nicolas Pitre
2015-11-25 18:09 ` Nicolas Pitre
2015-11-26 10:23 ` Jon Medhurst (Tixy)
2015-11-26 10:23 ` Jon Medhurst (Tixy)
-- strict thread matches above, loose matches on Subject: below --
2016-01-27 12:14 Will Deacon
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=20151119122030.GE22786@arm.com \
--to=will.deacon@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.