From: Marc Zyngier <marc.zyngier@arm.com>
To: Olof Johansson <olof@lixom.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: cpuinfo: Include cleartext implementer and part strings
Date: Mon, 16 Jul 2018 10:17:18 +0100 [thread overview]
Message-ID: <f619f0e9-b8b4-29fb-5ad6-7f5ebc3a4da8@arm.com> (raw)
In-Reply-To: <20180715035342.11371-1-olof@lixom.net>
Hi Olof,
On 15/07/18 04:53, Olof Johansson wrote:
> There's some use in printing out what the implementer and part numbers
> decode to for cases where they're known.
>
> I filled in the table based on public information; mostly from ARM TRMs
> and other tools (and some of the SSBD tables in the kernel, etc).
>
> Apple IDs came from
> https://github.com/apple/darwin-xnu/blob/master/osfmk/arm/cpuid.h
>
> Signed-off-by: Olof Johansson <olof@lixom.net>
> ---
> arch/arm64/kernel/cpuinfo.c | 79 +++++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 76 insertions(+), 3 deletions(-)
[...]
The same thing pops up every so often. And the answer is the same each time:
- it breaks an existing userspace ABI by changing the format of cpuinfo
- it is unmaintainable in the long run
- userspace already has this information by simply running "lscpu"
What has changed?
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2018-07-16 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 3:53 [PATCH] arm64: cpuinfo: Include cleartext implementer and part strings Olof Johansson
2018-07-16 9:17 ` Marc Zyngier [this message]
2018-07-16 14:34 ` Olof Johansson
2018-07-16 16:52 ` Mark Rutland
2018-07-17 12:27 ` Robin Murphy
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=f619f0e9-b8b4-29fb-5ad6-7f5ebc3a4da8@arm.com \
--to=marc.zyngier@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=will.deacon@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).