Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, 2015-11-25 at 13:09 -0500, Nicolas Pitre wrote: > But CPU MHz, when available, has the merit of not being open to > interpretation. Current MHz, maximum MHz or 'turbo' MHz? ;-) -- Tixy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, 2015-11-25 at 13:09 -0500, Nicolas Pitre wrote: > But CPU MHz, when available, has the merit of not being open to > interpretation. Current MHz, maximum MHz or 'turbo' MHz? ;-) -- Tixy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, 25 Nov 2015, Shi, Yang wrote: > On 11/25/2015 7:16 AM, Nicolas Pitre wrote: > > On Wed, 25 Nov 2015, Jon Masters wrote: > > > > > On 11/18/15, 1:15 PM, Yang Shi wrote: > > > > > > > As what Pavel Machek reported [1], some userspace applications depend on > > > > bogomips showed by

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On 11/25/2015 7:16 AM, Nicolas Pitre wrote: On Wed, 25 Nov 2015, Jon Masters wrote: On 11/18/15, 1:15 PM, Yang Shi wrote: As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm,

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, 25 Nov 2015, Jon Masters wrote: > On 11/18/15, 1:15 PM, Yang Shi wrote: > > > As what Pavel Machek reported [1], some userspace applications depend on > > bogomips showed by /proc/cpuinfo. > > > > Although there is much less legacy impact on aarch64 than arm, but it does > > break

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On 25 November 2015 at 07:45, Jon Masters wrote: > On a total tangent, it would be ideal to (eventually) have something > reported in /proc/cpuinfo or dmesg during boot that does "accurately" map > back to the underlying core frequency (as opposed to the generic timer > frequency). Try: grep .

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, Nov 25, 2015 at 12:45:13AM -0500, Jon Masters wrote: > On 11/18/15, 1:15 PM, Yang Shi wrote: > > >As what Pavel Machek reported [1], some userspace applications depend on > >bogomips showed by /proc/cpuinfo. > > > >Although there is much less legacy impact on aarch64 than arm, but it does

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, Nov 25, 2015 at 12:45:13AM -0500, Jon Masters wrote: > On 11/18/15, 1:15 PM, Yang Shi wrote: > > >As what Pavel Machek reported [1], some userspace applications depend on > >bogomips showed by /proc/cpuinfo. > > > >Although there is much less legacy impact on aarch64 than arm, but it does

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On 11/25/2015 7:16 AM, Nicolas Pitre wrote: On Wed, 25 Nov 2015, Jon Masters wrote: On 11/18/15, 1:15 PM, Yang Shi wrote: As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm,

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, 25 Nov 2015, Shi, Yang wrote: > On 11/25/2015 7:16 AM, Nicolas Pitre wrote: > > On Wed, 25 Nov 2015, Jon Masters wrote: > > > > > On 11/18/15, 1:15 PM, Yang Shi wrote: > > > > > > > As what Pavel Machek reported [1], some userspace applications depend on > > > > bogomips showed by

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, 25 Nov 2015, Jon Masters wrote: > On 11/18/15, 1:15 PM, Yang Shi wrote: > > > As what Pavel Machek reported [1], some userspace applications depend on > > bogomips showed by /proc/cpuinfo. > > > > Although there is much less legacy impact on aarch64 than arm, but it does > > break

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, Nov 25, 2015 at 12:45:13AM -0500, Jon Masters wrote: > On 11/18/15, 1:15 PM, Yang Shi wrote: > > >As what Pavel Machek reported [1], some userspace applications depend on > >bogomips showed by /proc/cpuinfo. > > > >Although there is much less legacy impact on aarch64 than arm, but it does

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On 25 November 2015 at 07:45, Jon Masters wrote: > On a total tangent, it would be ideal to (eventually) have something > reported in /proc/cpuinfo or dmesg during boot that does "accurately" map > back to the underlying core frequency (as opposed to the generic timer >

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, Nov 25, 2015 at 12:45:13AM -0500, Jon Masters wrote: > On 11/18/15, 1:15 PM, Yang Shi wrote: > > >As what Pavel Machek reported [1], some userspace applications depend on > >bogomips showed by /proc/cpuinfo. > > > >Although there is much less legacy impact on aarch64 than arm, but it does

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On 11/18/15, 1:15 PM, Yang Shi wrote: As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm, but it does break libvirt. Basically, this patch reverts commit

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On 11/18/15, 1:15 PM, Yang Shi wrote: As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm, but it does break libvirt. Basically, this patch reverts commit

Re: [V2 PATCH] arm64: restore bogomips information in /proc/cpuinfo

On 11/19/2015 9:59 AM, Catalin Marinas wrote: On Wed, Nov 18, 2015 at 10:48:55AM -0800, Yang Shi wrote: As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm, but it does break

Re: [V2 PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, Nov 18, 2015 at 10:48:55AM -0800, Yang Shi wrote: > As what Pavel Machek reported [1], some userspace applications depend on > bogomips showed by /proc/cpuinfo. > > Although there is much less legacy impact on aarch64 than arm, but it does > break libvirt. > > Basically, this patch

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

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 / (50UL/HZ), > > > +loops_per_jiffy / (5000UL/HZ) % 100); > >

Re: [V2 PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, Nov 18, 2015 at 10:48:55AM -0800, Yang Shi wrote: > As what Pavel Machek reported [1], some userspace applications depend on > bogomips showed by /proc/cpuinfo. > > Although there is much less legacy impact on aarch64 than arm, but it does > break libvirt. > > Basically, this patch

Re: [V2 PATCH] arm64: restore bogomips information in /proc/cpuinfo

On 11/19/2015 9:59 AM, Catalin Marinas wrote: On Wed, Nov 18, 2015 at 10:48:55AM -0800, Yang Shi wrote: As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm, but it does break

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

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 / (50UL/HZ), > > > +loops_per_jiffy / (5000UL/HZ) % 100); > >

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, 18 Nov 2015, Will Deacon wrote: > Hello, > > On Wed, Nov 18, 2015 at 10:15:05AM -0800, Yang Shi wrote: > > As what Pavel Machek reported [1], some userspace applications depend on > > bogomips showed by /proc/cpuinfo. > > > > Although there is much less legacy impact on aarch64 than

[V2 PATCH] arm64: restore bogomips information in /proc/cpuinfo

As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm, but it does break libvirt. Basically, this patch reverts commit 326b16db9f69fd0d279be873c6c00f88c0a4aad5 ("arm64: delay: don't

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On 11/18/2015 10:47 AM, Will Deacon wrote: Hello, On Wed, Nov 18, 2015 at 10:15:05AM -0800, Yang Shi wrote: As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm, but it does

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

Hello, On Wed, Nov 18, 2015 at 10:15:05AM -0800, Yang Shi wrote: > As what Pavel Machek reported [1], some userspace applications depend on > bogomips showed by /proc/cpuinfo. > > Although there is much less legacy impact on aarch64 than arm, but it does > break libvirt. > > Basically, this

[PATCH] arm64: restore bogomips information in /proc/cpuinfo

As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm, but it does break libvirt. Basically, this patch reverts commit 326b16db9f69fd0d279be873c6c00f88c0a4aad5 ("arm64: delay: don't

[PATCH] arm64: restore bogomips information in /proc/cpuinfo

As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm, but it does break libvirt. Basically, this patch reverts commit 326b16db9f69fd0d279be873c6c00f88c0a4aad5 ("arm64: delay: don't

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

Hello, On Wed, Nov 18, 2015 at 10:15:05AM -0800, Yang Shi wrote: > As what Pavel Machek reported [1], some userspace applications depend on > bogomips showed by /proc/cpuinfo. > > Although there is much less legacy impact on aarch64 than arm, but it does > break libvirt. > > Basically, this

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On 11/18/2015 10:47 AM, Will Deacon wrote: Hello, On Wed, Nov 18, 2015 at 10:15:05AM -0800, Yang Shi wrote: As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm, but it does

[V2 PATCH] arm64: restore bogomips information in /proc/cpuinfo

As what Pavel Machek reported [1], some userspace applications depend on bogomips showed by /proc/cpuinfo. Although there is much less legacy impact on aarch64 than arm, but it does break libvirt. Basically, this patch reverts commit 326b16db9f69fd0d279be873c6c00f88c0a4aad5 ("arm64: delay: don't

Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo

On Wed, 18 Nov 2015, Will Deacon wrote: > Hello, > > On Wed, Nov 18, 2015 at 10:15:05AM -0800, Yang Shi wrote: > > As what Pavel Machek reported [1], some userspace applications depend on > > bogomips showed by /proc/cpuinfo. > > > > Although there is much less legacy impact on aarch64 than