From: Al Stone <ahs3@redhat.com>
To: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Al Stone <ahs3@redhat.com>
Subject: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable
Date: Tue, 26 Sep 2017 16:23:21 -0600 [thread overview]
Message-ID: <20170926222324.17409-1-ahs3@redhat.com> (raw)
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 ill, some of the
automation used to manage systems in data centers (as well as many of
the humans involved) need to have text; this helps them simply slide
into place and become usable quickly.
Patch 1/2 provides the MPIDR as basic topology info in /proc/cpuinfo
when using ACPI, perhaps until such time as the more robust ACPI
implementation is available [0]; this is helpful in automating the
selection of multi-CPU systems when many choices are available (for
example, in automated testing systems). While it is yet another hex
value, it does provide some topology information without interfering
with what [0] will ultimately provide, and is helpful in sorting out
ACPI table issues that use the MPIDR for identifying CPUs.
Patches 2/3 and 3/3 are similar in that they provide a more human-
readable version of the info already available; this allows admin
tools to provide proper strings to display in inventory systems, for
example, or when a human is using a CI system and needs to be provided
a list of possible systems to test on.
In all of the patches, I have avoided replacing or interfering with
any existing output so as not to affect systems already in use.
Tested on AMD Seattle, APM Mustang and Cavium ThunderX systems.
[0] https://marc.info/?l=linux-pm&m=150584702021552&w=2
Al Stone (3):
arm64: cpuinfo: add MPIDR value to /proc/cpuinfo
arm64: cpuinfo: add human readable CPU names to /proc/cpuinfo
arm64: cpuinfo: display product info in /proc/cpuinfo
arch/arm64/include/asm/cpu.h | 1 +
arch/arm64/kernel/cpuinfo.c | 225 +++++++++++++++++++++++++++++++++++++++++++
2 files changed, 226 insertions(+)
--
2.13.5
WARNING: multiple messages have this Message-ID (diff)
From: ahs3@redhat.com (Al Stone)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable
Date: Tue, 26 Sep 2017 16:23:21 -0600 [thread overview]
Message-ID: <20170926222324.17409-1-ahs3@redhat.com> (raw)
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 ill, some of the
automation used to manage systems in data centers (as well as many of
the humans involved) need to have text; this helps them simply slide
into place and become usable quickly.
Patch 1/2 provides the MPIDR as basic topology info in /proc/cpuinfo
when using ACPI, perhaps until such time as the more robust ACPI
implementation is available [0]; this is helpful in automating the
selection of multi-CPU systems when many choices are available (for
example, in automated testing systems). While it is yet another hex
value, it does provide some topology information without interfering
with what [0] will ultimately provide, and is helpful in sorting out
ACPI table issues that use the MPIDR for identifying CPUs.
Patches 2/3 and 3/3 are similar in that they provide a more human-
readable version of the info already available; this allows admin
tools to provide proper strings to display in inventory systems, for
example, or when a human is using a CI system and needs to be provided
a list of possible systems to test on.
In all of the patches, I have avoided replacing or interfering with
any existing output so as not to affect systems already in use.
Tested on AMD Seattle, APM Mustang and Cavium ThunderX systems.
[0] https://marc.info/?l=linux-pm&m=150584702021552&w=2
Al Stone (3):
arm64: cpuinfo: add MPIDR value to /proc/cpuinfo
arm64: cpuinfo: add human readable CPU names to /proc/cpuinfo
arm64: cpuinfo: display product info in /proc/cpuinfo
arch/arm64/include/asm/cpu.h | 1 +
arch/arm64/kernel/cpuinfo.c | 225 +++++++++++++++++++++++++++++++++++++++++++
2 files changed, 226 insertions(+)
--
2.13.5
next reply other threads:[~2017-09-26 22:23 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 22:23 Al Stone [this message]
2017-09-26 22:23 ` [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable Al Stone
2017-09-26 22:23 ` [PATCH 1/3] arm64: cpuinfo: add MPIDR value to /proc/cpuinfo Al Stone
2017-09-26 22:23 ` Al Stone
2017-09-27 11:33 ` Mark Rutland
2017-09-27 11:33 ` Mark Rutland
2017-09-26 22:23 ` [PATCH 2/3] arm64: cpuinfo: add human readable CPU names " Al Stone
2017-09-26 22:23 ` Al Stone
2017-09-27 10:35 ` Robin Murphy
2017-09-27 10:35 ` Robin Murphy
2017-09-27 11:26 ` Mark Rutland
2017-09-27 11:26 ` Mark Rutland
2017-10-13 14:16 ` Timur Tabi
2017-10-13 14:16 ` Timur Tabi
2017-09-26 22:23 ` [PATCH 3/3] arm64: cpuinfo: display product info in /proc/cpuinfo Al Stone
2017-09-26 22:23 ` Al Stone
2017-09-27 0:40 ` Florian Fainelli
2017-09-27 0:40 ` Florian Fainelli
2017-09-27 10:42 ` Robin Murphy
2017-09-27 10:42 ` Robin Murphy
2017-09-27 13:39 ` Mark Rutland
2017-09-27 13:39 ` Mark Rutland
2017-09-27 11:36 ` Mark Rutland
2017-09-27 11:36 ` Mark Rutland
2017-10-13 19:27 ` Timur Tabi
2017-10-13 19:27 ` Timur Tabi
2017-09-27 10:34 ` [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable Mark Rutland
2017-09-27 10:34 ` Mark Rutland
2017-10-09 22:46 ` Al Stone
2017-10-09 22:46 ` Al Stone
2017-10-13 13:39 ` Timur Tabi
2017-10-13 13:39 ` Timur Tabi
2017-10-13 14:27 ` Mark Rutland
2017-10-13 14:27 ` Mark Rutland
2017-10-16 23:43 ` Al Stone
2017-10-16 23:43 ` Al Stone
2017-10-20 16:10 ` Mark Rutland
2017-10-20 16:10 ` Mark Rutland
2017-10-20 17:24 ` Jon Masters
2017-10-20 17:24 ` Jon Masters
2017-10-21 0:50 ` Jon Masters
2017-10-21 0:50 ` Jon Masters
2017-10-20 23:26 ` Al Stone
2017-10-20 23:26 ` Al Stone
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=20170926222324.17409-1-ahs3@redhat.com \
--to=ahs3@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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.