Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-20 Thread Jon Masters
On 10/20/2017 01:24 PM, Jon Masters wrote: > 1). The first thing people do when they get an Arm server is to cat > /proc/cpuinfo. They then come complaining that it's not like x86. They > can't get the output their looking for and this results in bug filing, > and countless hours on phone calls

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-20 Thread Jon Masters
On 10/20/2017 01:24 PM, Jon Masters wrote: > 1). The first thing people do when they get an Arm server is to cat > /proc/cpuinfo. They then come complaining that it's not like x86. They > can't get the output their looking for and this results in bug filing, > and countless hours on phone calls

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-20 Thread Al Stone
On 10/20/2017 10:10 AM, Mark Rutland wrote: > Hi Al, > > On Mon, Oct 16, 2017 at 05:43:19PM -0600, Al Stone wrote: >> On 10/13/2017 08:27 AM, Mark Rutland wrote: >>> I certainly agree that exposing the information that we have is useful, >>> as I have stated several times. I'm not NAKing exposing

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-20 Thread Al Stone
On 10/20/2017 10:10 AM, Mark Rutland wrote: > Hi Al, > > On Mon, Oct 16, 2017 at 05:43:19PM -0600, Al Stone wrote: >> On 10/13/2017 08:27 AM, Mark Rutland wrote: >>> I certainly agree that exposing the information that we have is useful, >>> as I have stated several times. I'm not NAKing exposing

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-20 Thread Jon Masters
Hi Mark, On 10/20/2017 12:10 PM, Mark Rutland wrote: > On Mon, Oct 16, 2017 at 05:43:19PM -0600, Al Stone wrote: >> Obviously, you'll have to see the patches to >> properly answer that, but what I'm playing with at present is placing >> this info in new entries in /sys/devices/cpu and/or

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-20 Thread Jon Masters
Hi Mark, On 10/20/2017 12:10 PM, Mark Rutland wrote: > On Mon, Oct 16, 2017 at 05:43:19PM -0600, Al Stone wrote: >> Obviously, you'll have to see the patches to >> properly answer that, but what I'm playing with at present is placing >> this info in new entries in /sys/devices/cpu and/or

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-20 Thread Mark Rutland
Hi Al, On Mon, Oct 16, 2017 at 05:43:19PM -0600, Al Stone wrote: > On 10/13/2017 08:27 AM, Mark Rutland wrote: > > I certainly agree that exposing the information that we have is useful, > > as I have stated several times. I'm not NAKing exposing this information > > elsewhere. > > > > If you

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-20 Thread Mark Rutland
Hi Al, On Mon, Oct 16, 2017 at 05:43:19PM -0600, Al Stone wrote: > On 10/13/2017 08:27 AM, Mark Rutland wrote: > > I certainly agree that exposing the information that we have is useful, > > as I have stated several times. I'm not NAKing exposing this information > > elsewhere. > > > > If you

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-16 Thread Al Stone
On 10/13/2017 08:27 AM, Mark Rutland wrote: > Hi Timur, > > On Fri, Oct 13, 2017 at 08:39:09AM -0500, Timur Tabi wrote: >> On Wed, Sep 27, 2017 at 5:34 AM, Mark Rutland wrote: >>> On Tue, Sep 26, 2017 at 04:23:21PM -0600, Al Stone wrote: As ARMv8 servers get deployed,

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-16 Thread Al Stone
On 10/13/2017 08:27 AM, Mark Rutland wrote: > Hi Timur, > > On Fri, Oct 13, 2017 at 08:39:09AM -0500, Timur Tabi wrote: >> On Wed, Sep 27, 2017 at 5:34 AM, Mark Rutland wrote: >>> On Tue, Sep 26, 2017 at 04:23:21PM -0600, Al Stone wrote: As ARMv8 servers get deployed, I keep getting the

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-13 Thread Mark Rutland
Hi Timur, On Fri, Oct 13, 2017 at 08:39:09AM -0500, Timur Tabi wrote: > On Wed, Sep 27, 2017 at 5:34 AM, Mark Rutland wrote: > > On Tue, Sep 26, 2017 at 04:23:21PM -0600, Al Stone wrote: > >> As ARMv8 servers get deployed, I keep getting the same set of questions > >> from

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-13 Thread Mark Rutland
Hi Timur, On Fri, Oct 13, 2017 at 08:39:09AM -0500, Timur Tabi wrote: > On Wed, Sep 27, 2017 at 5:34 AM, Mark Rutland wrote: > > On Tue, Sep 26, 2017 at 04:23:21PM -0600, Al Stone wrote: > >> As ARMv8 servers get deployed, I keep getting the same set of questions > >> from end-users of those

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-13 Thread Timur Tabi
On Wed, Sep 27, 2017 at 5:34 AM, Mark Rutland wrote: > Hi Al, > > On Tue, Sep 26, 2017 at 04:23:21PM -0600, Al Stone wrote: >> As ARMv8 servers get deployed, I keep getting the same set of questions >> from end-users of those systems: what do all the hex numbers mean in >>

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-13 Thread Timur Tabi
On Wed, Sep 27, 2017 at 5:34 AM, Mark Rutland wrote: > Hi Al, > > On Tue, Sep 26, 2017 at 04:23:21PM -0600, Al Stone wrote: >> As ARMv8 servers get deployed, I keep getting the same set of questions >> from end-users of those systems: what do all the hex numbers mean in >> /proc/cpuinfo and could

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-09 Thread Al Stone
On 09/27/2017 04:34 AM, Mark Rutland wrote: > On Tue, Sep 26, 2017 at 04:23:21PM -0600, Al Stone wrote: >> As ARMv8 servers get deployed, I keep getting the same set of questions >> from end-users of those systems: what do all the hex numbers mean in >> /proc/cpuinfo and could you make them so I

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-10-09 Thread Al Stone
On 09/27/2017 04:34 AM, Mark Rutland wrote: > On Tue, Sep 26, 2017 at 04:23:21PM -0600, Al Stone wrote: >> As ARMv8 servers get deployed, I keep getting the same set of questions >> from end-users of those systems: what do all the hex numbers mean in >> /proc/cpuinfo and could you make them so I

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-09-27 Thread Mark Rutland
Hi Al, On Tue, Sep 26, 2017 at 04:23:21PM -0600, Al Stone wrote: > As ARMv8 servers get deployed, I keep getting the same set of questions > from end-users of those systems: what do all the hex numbers mean in > /proc/cpuinfo and could you make them so I don't have to carry a cheat > sheet with

Re: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-09-27 Thread Mark Rutland
Hi Al, On Tue, Sep 26, 2017 at 04:23:21PM -0600, Al Stone wrote: > As ARMv8 servers get deployed, I keep getting the same set of questions > from end-users of those systems: what do all the hex numbers mean in > /proc/cpuinfo and could you make them so I don't have to carry a cheat > sheet with

[PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-09-26 Thread Al Stone
As ARMv8 servers get deployed, I keep getting the same set of questions from end-users of those systems: what do all the hex numbers mean in /proc/cpuinfo and could you make them so I don't have to carry a cheat sheet with me all the time? These patches respond to those questions. For good or

[PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable

2017-09-26 Thread Al Stone
As ARMv8 servers get deployed, I keep getting the same set of questions from end-users of those systems: what do all the hex numbers mean in /proc/cpuinfo and could you make them so I don't have to carry a cheat sheet with me all the time? These patches respond to those questions. For good or