From: Will Deacon <will@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
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>
Subject: Re: [PATCH] arm64: Kconfig: Make CPU_BIG_ENDIAN depend on BROKEN
Date: Thu, 25 Sep 2025 14:01:08 +0100 [thread overview]
Message-ID: <aNU9FPYAUnBMMznn@willie-the-truck> (raw)
In-Reply-To: <778ccdfe-791c-4d67-a7f5-354ea84159dc@roeck-us.net>
On Wed, Sep 24, 2025 at 09:09:16AM -0700, Guenter Roeck wrote:
> On 9/19/25 11:40, 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.
> >
> > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > Cc: Marc Zyngier <maz@kernel.org>
> > Cc: Ard Biesheuvel <ardb@kernel.org>
> > Cc: Arnd Bergmann <arnd@arndb.de>
> > Cc: Hanjun Guo <guohanjun@huawei.com>
> > Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > Cc: Guenter Roeck <linux@roeck-us.net>
> > Link: https://lore.kernel.org/linux-arm-kernel/73701e9f-bee1-7ae8-2277-7a3576171cd4@huawei.com/ [1]
> > Signed-off-by: Will Deacon <will@kernel.org>
> > ---
> >
> > Cc'ing Guenter as a heads-up in case he needs to turn down his testing
> > to avoid this causing a false regression report.
>
> Cool, one more architecture to drop. I wonder if I should drop arm64 big endian testing
> for all kernel releases. That would simplify my test infrastructure substantially,
> and it would avoid useless regressions due to bitrot for older kernel releases
> if no one is using it anyway. Thoughts ?
It's entirely up to you, but I'd suggest leaving it running until 6.18
is out and then turning it all off if nobody has chimed in to say
they're using this stuff.
Will
next prev parent reply other threads:[~2025-09-25 13:01 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 [this message]
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
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=aNU9FPYAUnBMMznn@willie-the-truck \
--to=will@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--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 \
/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