From: "J. Neuschäfer" <j.neuschaefer@gmx.net>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Marc Zyngier <maz@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Hanjun Guo <guohanjun@huawei.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Guenter Roeck <linux@roeck-us.net>,
Jens Reidel <adrian@mainlining.org>
Subject: Re: [PATCH] arm64: Kconfig: Make CPU_BIG_ENDIAN depend on BROKEN
Date: Mon, 29 Sep 2025 02:18:55 +0200 [thread overview]
Message-ID: <aNnQb9gH8pzwfRJ5@probook> (raw)
In-Reply-To: <20250919184025.15416-1-will@kernel.org>
On Fri, Sep 19, 2025 at 07:40:25PM +0100, Will Deacon wrote:
> Big-endian arm64 configurations are vanishingly rare, yet we still claim
> to support them in Linux despite very limited testing or visible
> interest. Supporting big-endian adds unnecessary burden to reviewers and
> contributors which, without any known active users, is hard to justify.
> For example, recent work to improve our futex routines and to implement
> nested virtualisation support is non-trivially complicated by having to
> support both big- and little-endianness.
>
> Back in 2019 [1], it was claimed that Huawei were using arm64 big-endian
> machines in their telecommunication products but I don't know whether
> that's still the case and certainly haven't seen any patch contributions
> to help support or maintain it.
>
> Make CPU_BIG_ENDIAN depend on BROKEN as an initial deprecation step
> towards its removal.
As of this month (September 2025) there's a new community project [1,2]
to revive aarch64_be. Jens Reidel (CC'd) and I are involved in it. We've
been fixing several aarch64_be-related bugs, but mostly[3] in userspace,
because the kernel support is pretty solid.
So, just so it doesn't go unmentioned, there is interest in keeping
big-endian ARM64 alive.
Best regards,
J. Neuschäfer
[1]: https://aarch64.be/ (binary packages)
[2]: https://codeberg.org/neuschaefer/porting/src/branch/main/aarch64_be.md
(status and documentation)
[3]: https://lore.kernel.org/lkml/20250726235646.254730-1-adrian@mainlining.org/
next prev parent reply other threads:[~2025-09-29 0:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 18:40 [PATCH] arm64: Kconfig: Make CPU_BIG_ENDIAN depend on BROKEN Will Deacon
2025-09-19 19:00 ` Ard Biesheuvel
2025-09-19 20:56 ` Marc Zyngier
2025-09-19 21:10 ` Catalin Marinas
2025-09-24 16:09 ` Guenter Roeck
2025-09-25 13:01 ` Will Deacon
2025-09-25 22:54 ` Guenter Roeck
2025-09-24 16:09 ` Will Deacon
2025-09-27 1:44 ` Hanjun Guo
2025-09-29 0:18 ` J. Neuschäfer [this message]
2025-09-29 10:52 ` Catalin Marinas
2025-09-29 20:16 ` J. Neuschäfer
2025-09-30 8:57 ` Marc Zyngier
2025-10-01 9:29 ` A. Wilcox
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=aNnQb9gH8pzwfRJ5@probook \
--to=j.neuschaefer@gmx.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=adrian@mainlining.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=maz@kernel.org \
--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).