From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
Anton Johansson <anjo@rev.ng>, Jason Wang <jasowang@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Alistair Francis <alistair@alistair23.me>,
Thomas Huth <thuth@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Peter Maydell <peter.maydell@linaro.org>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v5 11/16] hw/microblaze: Support various endianness for s3adsp1800 machines
Date: Tue, 11 Feb 2025 10:22:37 +0100 [thread overview]
Message-ID: <85539c0c-51e8-43ba-9c99-23e1b684f30e@linaro.org> (raw)
In-Reply-To: <Z6S3Mgt1G7fIjeBB@redhat.com>
On 6/2/25 14:20, Daniel P. Berrangé wrote:
> On Thu, Feb 06, 2025 at 02:10:47PM +0100, Philippe Mathieu-Daudé wrote:
>> Introduce an abstract machine parent class which defines
>> the 'little_endian' property. Duplicate the current machine,
>> which endian is tied to the binary endianness, to one big
>> endian and a little endian machine; updating the machine
>> description. Keep the current default machine for each binary.
>>
>> 'petalogix-s3adsp1800' machine is aliased as:
>> - 'petalogix-s3adsp1800-be' on big-endian binary,
>> - 'petalogix-s3adsp1800-le' on little-endian one.
>
> Does it makes sense to expose these as different machine types ?
>
> If all the HW is identical in both cases, it feels like the
> endianness could just be a bool property of the machine type,
> rather than a new machine type.
To clarify what we are trying to achieve here:
1/ Current situation:
$ qemu-system-microblaze -M help
Supported machines are:
none empty machine
petalogix-ml605 PetaLogix linux refdesign for xilinx ml605 (big
endian) (deprecated)
petalogix-s3adsp1800 PetaLogix linux refdesign for xilinx Spartan
3ADSP1800 (default)
xlnx-zynqmp-pmu Xilinx ZynqMP PMU machine (big endian) (deprecated)
$ qemu-system-microblazeel -M help
Supported machines are:
none empty machine
petalogix-ml605 PetaLogix linux refdesign for xilinx ml605 (little
endian)
petalogix-s3adsp1800 PetaLogix linux refdesign for xilinx Spartan
3ADSP1800 (default)
xlnx-zynqmp-pmu Xilinx ZynqMP PMU machine (little endian)
1 architecture declined in 2 binaries, total of 6 machines
2/ With this series:
qemu-system-microblaze -M help
Supported machines are:
none empty machine
petalogix-ml605 PetaLogix linux refdesign for xilinx ml605 (big
endian) (deprecated)
petalogix-s3adsp1800 PetaLogix linux refdesign for xilinx Spartan
3ADSP1800 (big endian) (alias of petalogix-s3adsp1800-be)
petalogix-s3adsp1800-be PetaLogix linux refdesign for xilinx Spartan
3ADSP1800 (big endian) (default)
petalogix-s3adsp1800-le PetaLogix linux refdesign for xilinx Spartan
3ADSP1800 (little endian)
xlnx-zynqmp-pmu Xilinx ZynqMP PMU machine (big endian) (deprecated)
qemu-system-microblazeel -M help
Supported machines are:
none empty machine
petalogix-ml605 PetaLogix linux refdesign for xilinx ml605 (little
endian)
petalogix-s3adsp1800-be PetaLogix linux refdesign for xilinx Spartan
3ADSP1800 (big endian)
petalogix-s3adsp1800 PetaLogix linux refdesign for xilinx Spartan
3ADSP1800 (little endian) (alias of petalogix-s3adsp1800-le)
petalogix-s3adsp1800-le PetaLogix linux refdesign for xilinx Spartan
3ADSP1800 (little endian) (default)
xlnx-zynqmp-pmu Xilinx ZynqMP PMU machine (little endian)
1 architecture declined in 2 binaries, total of 10 machines
3/ Once the deprecation period passed and we can merge the 2 binaries:
$ qemu-system-microblaze -M help
Supported machines are:
none empty machine
petalogix-ml605 PetaLogix linux refdesign for xilinx ml605 (little
endian)
petalogix-s3adsp1800-be PetaLogix linux refdesign for xilinx Spartan
3ADSP1800 (big endian)
petalogix-s3adsp1800-le PetaLogix linux refdesign for xilinx Spartan
3ADSP1800 (little endian)
xlnx-zynqmp-pmu Xilinx ZynqMP PMU machine (little endian)
1 architecture, 1 binary, 4 machines (which could be reduced to 3 if
we want a default endianness for the s3adsp1800).
Due to the deprecation policy, step 2/ is necessary to reach 3/.
next prev parent reply other threads:[~2025-02-11 9:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 13:10 [PATCH v5 00/16] hw/microblaze: Allow running cross-endian vCPUs Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 01/16] hw/intc/xilinx_intc: Make device endianness configurable Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 02/16] hw/net/xilinx_ethlite: " Philippe Mathieu-Daudé
2025-02-06 17:14 ` Thomas Huth
2025-02-06 21:32 ` Richard Henderson
2025-02-06 13:10 ` [PATCH v5 03/16] hw/timer/xilinx_timer: " Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 04/16] hw/char/xilinx_uartlite: " Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 05/16] hw/ssi/xilinx_spi: " Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 06/16] hw/arm/xlnx-zynqmp: Use &error_abort for programming errors Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 07/16] target/microblaze: Explode MO_TExx -> MO_TE | MO_xx Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 08/16] target/microblaze: Set MO_TE once in do_load() / do_store() Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 09/16] target/microblaze: Introduce mo_endian() helper Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 10/16] target/microblaze: Consider endianness while translating code Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 11/16] hw/microblaze: Support various endianness for s3adsp1800 machines Philippe Mathieu-Daudé
2025-02-06 13:20 ` Daniel P. Berrangé
2025-02-06 13:53 ` Philippe Mathieu-Daudé
2025-02-06 14:31 ` Daniel P. Berrangé
2025-02-06 15:04 ` Philippe Mathieu-Daudé
2025-02-06 17:08 ` Thomas Huth
2025-02-06 17:12 ` Daniel P. Berrangé
2025-02-06 17:49 ` Philippe Mathieu-Daudé
2025-02-06 18:06 ` Daniel P. Berrangé
2025-02-06 18:24 ` Philippe Mathieu-Daudé
2025-02-06 18:29 ` Daniel P. Berrangé
2025-02-06 18:43 ` Philippe Mathieu-Daudé
2025-02-06 18:37 ` Philippe Mathieu-Daudé
2025-02-06 17:34 ` Max Filippov
2025-02-06 17:44 ` Philippe Mathieu-Daudé
2025-02-11 9:22 ` Philippe Mathieu-Daudé [this message]
2025-02-06 13:10 ` [PATCH v5 12/16] tests/functional: Explicit endianness of microblaze assets Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 13/16] tests/functional: Allow microblaze tests to take a machine name argument Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 14/16] tests/functional: Remove sleep() kludges from microblaze tests Philippe Mathieu-Daudé
2025-02-06 17:10 ` Thomas Huth
2025-02-06 21:40 ` Richard Henderson
2025-02-06 13:10 ` [PATCH v5 15/16] tests/functional: Have microblaze tests inherit common parent class Philippe Mathieu-Daudé
2025-02-06 13:10 ` [PATCH v5 16/16] tests/functional: Run cross-endian microblaze tests Philippe Mathieu-Daudé
2025-02-10 20:35 ` [PATCH v5 00/16] hw/microblaze: Allow running cross-endian vCPUs 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=85539c0c-51e8-43ba-9c99-23e1b684f30e@linaro.org \
--to=philmd@linaro.org \
--cc=alistair@alistair23.me \
--cc=anjo@rev.ng \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=jasowang@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
/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).