From: Marc Zyngier <maz@kernel.org>
To: "\"J. Neuschäfer\"" <j.neuschaefer@gmx.net>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.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: Tue, 30 Sep 2025 09:57:52 +0100 [thread overview]
Message-ID: <86wm5gz59r.wl-maz@kernel.org> (raw)
In-Reply-To: <aNrpIY4_2bfJm5XK@probook>
On Mon, 29 Sep 2025 21:16:33 +0100,
"J. Neuschäfer" <j.neuschaefer@gmx.net> wrote:
>
> I understand the maintenance cost argument, and I'm fine with the
> CONFIG_BROKEN dependency, even if it might be applied to features that
> cause problems in the future (such as nested virt) — it's easy to work
> around, and features can be fixed as needed.
Not really. Cross-endianness support is completely incompatible with
nested virt *by design*, and can't be worked around by SW. You'd need
to introduce incompatible changes in the architecture to support this.
Yes, this is a shame, but also a sign that architecture and
implementations have moved on.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-09-30 8:58 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
2025-09-29 10:52 ` Catalin Marinas
2025-09-29 20:16 ` J. Neuschäfer
2025-09-30 8:57 ` Marc Zyngier [this message]
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=86wm5gz59r.wl-maz@kernel.org \
--to=maz@kernel.org \
--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=j.neuschaefer@gmx.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@roeck-us.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.