linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Rongwei Wang <rongwei.wang@linux.alibaba.com>
Cc: catalin.marinas@arm.com, will@kernel.org, joey.gouly@arm.com,
	mark.rutland@arm.com, akpm@linux-foundation.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] arm64: improve display about CPU architecture in cpuinfo
Date: Mon, 07 Mar 2022 12:23:20 +0000	[thread overview]
Message-ID: <87bkyi0x53.wl-maz@kernel.org> (raw)
In-Reply-To: <a31431bf-24bb-71ac-8f3c-f9ca19f5c4f0@linux.alibaba.com>

On Mon, 07 Mar 2022 12:13:50 +0000,
Rongwei Wang <rongwei.wang@linux.alibaba.com> wrote:
> 
> 
> 
> On 3/7/22 4:45 PM, Marc Zyngier wrote:
> > On Mon, 07 Mar 2022 03:04:17 +0000,
> > Rongwei Wang <rongwei.wang@linux.alibaba.com> wrote:
> >> 
> >> Now, it is unsuitable for both ARMv8 and ARMv9 to show a
> >> fixed string "CPU architecture: 8" in /proc/cpuinfo.
> > 
> > Please read the various threads that have been going on over the past
> > 10+ years about *why* we don't allow this sort of change (TL;DR: it
> > breaks userspace, and we don't do that).
> > 
> > Also, there is no material difference between v8 and v9 that would be
> > observable from userspace outside of the "Features:" line. And if that
> > doesn't convince you, just think of '8' as the number of bytes
> > used by

> I got your point. It seems that we can regard '8' as the number of
> bytes. But what make me do this is that 'CPU architecture: 8' is
> confusing, especially those responsible for testing.
> And I believe that most people regard this '8' as ARMv8, maybe not.

That was the original intention. But given that there is no userspace
visible difference between v8, v9 and  whatever comes after it, this
is a pointless change. My comment about the size of a VA was just a
joke, and not something to be taken seriously.

> In fact, I'm not sure it has potential ABI implications, so seek your
> advice.

Plenty of userspace programs parse /proc/cpuinfo. If you replace '8'
with anything else, they will fail. Which is why although your patch
makes sense, it comes 10 years too late, and we can't change this
anymore.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-03-07 12:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  3:04 [PATCH RFC] arm64: improve display about CPU architecture in cpuinfo Rongwei Wang
2022-03-07  8:43 ` Catalin Marinas
2022-03-07  8:45 ` Marc Zyngier
2022-03-07 12:13   ` Rongwei Wang
2022-03-07 12:23     ` Marc Zyngier [this message]
2022-03-07 16:48       ` Robin Murphy
2022-03-07 19:30         ` Arnd Bergmann
2022-03-07 20:05           ` Robin Murphy
2022-03-08 17:18             ` Catalin Marinas
2022-03-08 17:47               ` Robin Murphy
2022-03-08 17:57             ` Russell King (Oracle)
2022-03-08 19:09               ` Robin Murphy
2022-03-08 17:55           ` Russell King (Oracle)

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=87bkyi0x53.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rongwei.wang@linux.alibaba.com \
    --cc=will@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 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).