qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	qemu-devel@nongnu.org
Cc: Alistair Francis <alistair@alistair23.me>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH 3/4] hw/microblaze: Remove the big-endian variants of ml605 and xlnx-zynqmp-pmu
Date: Fri, 16 May 2025 17:06:45 +0200	[thread overview]
Message-ID: <9b75c7a1-b9c1-47cf-b421-0779fad23e5a@redhat.com> (raw)
In-Reply-To: <d5dbb421-83bc-4ac9-9a88-953ec0f97735@linaro.org>

On 16/05/2025 17.00, Philippe Mathieu-Daudé wrote:
> On 15/5/25 15:20, Thomas Huth wrote:
>> From: Thomas Huth <thuth@redhat.com>
>>
>> Both machines were added with little-endian in mind only (the
>> "endianness" CPU property was hard-wired to "true", see commits
>> 133d23b3ad1 and a88bbb006a52), so the variants that showed up
>> on the big endian target likely never worked. We deprecated these
>> non-working machine variants two releases ago, and so far nobody
>> complained, so it should be fine now to disable them. Hard-wire
>> the machines to little endian now.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>   docs/about/deprecated.rst           |  6 ------
>>   docs/about/removed-features.rst     |  9 +++++++++
>>   hw/microblaze/petalogix_ml605_mmu.c | 15 ++++-----------
>>   hw/microblaze/xlnx-zynqmp-pmu.c     |  7 +------
>>   4 files changed, 14 insertions(+), 23 deletions(-)
> 
> \o/
> 
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>

Thanks!

> I won't be able to look at the rest of this series until in 10 days,
> feel free to merge if necessary.

Maybe you could at least provide a quick comment on the idea of controlling 
the endianness of the s3adsp1800 machine via a machine property? (since your 
original idea was to do it via different machine names instead ... does the 
property sound acceptable to you?)

  Thomas



  reply	other threads:[~2025-05-16 15:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 13:20 [PATCH 0/4] hw/microblaze: Endianness clean-ups and deprecations Thomas Huth
2025-05-15 13:20 ` [PATCH 1/4] hw/microblaze: Add endianness property to the petalogix_s3adsp1800 machine Thomas Huth
2025-05-24 12:55   ` Richard Henderson
2025-05-25 19:09     ` Philippe Mathieu-Daudé
2025-05-26 13:51       ` Markus Armbruster
2025-05-27 13:56   ` Philippe Mathieu-Daudé
2025-05-15 13:20 ` [PATCH 2/4] tests/functional: Test both microblaze s3adsp1800 endianness variants Thomas Huth
2025-05-27 13:54   ` Philippe Mathieu-Daudé
2025-05-15 13:20 ` [PATCH 3/4] hw/microblaze: Remove the big-endian variants of ml605 and xlnx-zynqmp-pmu Thomas Huth
2025-05-16 15:00   ` Philippe Mathieu-Daudé
2025-05-16 15:06     ` Thomas Huth [this message]
2025-05-25 19:19       ` Philippe Mathieu-Daudé
2025-05-26  5:59         ` Thomas Huth
2025-05-24 12:56   ` Richard Henderson
2025-05-27 13:51   ` Philippe Mathieu-Daudé
2025-05-15 13:20 ` [PATCH 4/4] docs: Deprecate the qemu-system-microblazeel binary Thomas Huth
2025-05-24 12:57   ` Richard Henderson
2025-05-27 13:50   ` Philippe Mathieu-Daudé

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=9b75c7a1-b9c1-47cf-b421-0779fad23e5a@redhat.com \
    --to=thuth@redhat.com \
    --cc=alistair@alistair23.me \
    --cc=edgar.iglesias@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.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).