On 11/16/2026 3:00 PM, Philippe Mathieu-Daudé wrote:
> On 16/11/26 23:28, Richard Henderson wrote:
>> On 11/16/26 09:05, Philippe Mathieu-Daudé wrote:
>>> Tangent to this, it makes sense to deprecate quickly enough on
>>> QEMU side when a host-related project we use deprecates / removes
>>> it; when this is guest related I don't see the urge, in particular
>>> when the maintenance is almost zero cost. For the particular
>>> aarch64_be I agree what we lacks is coverage testing; but for
>>> other features I'd prefer we keep them as long as there is interest
>>> within QEMU users, independent of external projects change like
>>> the Linux kernel.
>>
>> There have been a couple of attempts at aarch64_be, but *never* any
>> upstream traction.  qemu-linux-user is about emulating Linux -- you
>> can't divorce these two.
>>
>> In my opinion, those that want to work on aarch64_be can work in
>> system mode, where the endian switching bits work as required by the
>> architecture.
> 
> OK I'm happy dropping Aarch64_be. Patches 7-10 are still common to all
> targets and worth review comments :)

Beyond aarch64, what about qemu-arm and qemu-armeb?
If we all agree to try to unify that, I would be happy to help review
the series.

Regards,
Pierrick

Reply via email to