lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 07 Mar 2022 08:45:05 +0000
From:   Marc Zyngier <maz@...nel.org>
To:     Rongwei Wang <rongwei.wang@...ux.alibaba.com>
Cc:     catalin.marinas@....com, will@...nel.org, joey.gouly@....com,
        mark.rutland@....com, akpm@...ux-foundation.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC] arm64: improve display about CPU architecture in cpuinfo

On Mon, 07 Mar 2022 03:04:17 +0000,
Rongwei Wang <rongwei.wang@...ux.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
a virtual address. You can't make that a '9'. Yet.

	M.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ