qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Anton Johansson" <anjo@rev.ng>,
	qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	devel@lists.libvirt.org, qemu-ppc@nongnu.org,
	"Alistair Francis" <alistair@alistair23.me>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	qemu-arm@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH v2 07/16] hw/char/xilinx_uartlite: Make device endianness configurable
Date: Thu, 7 Nov 2024 10:27:52 +0000	[thread overview]
Message-ID: <fe69adc2-0ebb-4be0-93a2-9a45d87c36d3@linaro.org> (raw)
In-Reply-To: <20241107012223.94337-8-philmd@linaro.org>

On 11/7/24 01:22, Philippe Mathieu-Daudé wrote:
> Replace the DEVICE_NATIVE_ENDIAN MemoryRegionOps by a pair
> of DEVICE_LITTLE_ENDIAN / DEVICE_BIG_ENDIAN.
> Add the "little-endian" property to select the device
> endianness, defaulting to little endian.
> Set the proper endianness on the single machine using the
> device.
> 
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
>   hw/char/xilinx_uartlite.c                | 44 ++++++++++++++++--------
>   hw/microblaze/petalogix_s3adsp1800_mmu.c |  1 +
>   2 files changed, 31 insertions(+), 14 deletions(-)

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>

> +static const MemoryRegionOps uart_ops[2] = {
> +    {
> +        .read = uart_read,
> +        .write = uart_write,
> +        .endianness = DEVICE_BIG_ENDIAN,
> +        .impl = {
> +            .min_access_size = 4,
> +            .max_access_size = 4,
> +        },
> +        .valid = {
> +            .min_access_size = 1,
> +            .max_access_size = 4,
> +        },
> +    }, {
> +        .read = uart_read,
> +        .write = uart_write,
> +        .endianness = DEVICE_LITTLE_ENDIAN,
> +        .impl = {
> +            .min_access_size = 4,
> +            .max_access_size = 4,
> +        },
> +        .valid = {
> +            .min_access_size = 1,
> +            .max_access_size = 4,
> +        },
>       }
>   };

Having looked at several of these now, it occurs to me that you can avoid repetition:

static const MemoryRegionOps uart_ops[2] = {
     [0 ... 1] = {
         .read = uart_read,
         etc,
     },
     [0].endianness = DEVICE_BIG_ENDIAN,
     [1].endianness = DEVICE_LITTLE_ENDIAN,
};


r~


  reply	other threads:[~2024-11-07 10:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07  1:22 [PATCH v2 00/16] hw/microblaze: Allow running cross-endian vCPUs Philippe Mathieu-Daudé
2024-11-07  1:22 ` [PATCH v2 01/16] hw/microblaze: Restrict MemoryRegionOps are implemented as 32-bit Philippe Mathieu-Daudé
2024-11-07  1:22 ` [PATCH v2 02/16] hw/microblaze: Propagate CPU endianness to microblaze_load_kernel() Philippe Mathieu-Daudé
2024-11-07 10:06   ` Richard Henderson
2024-11-07  1:22 ` [PATCH v2 03/16] hw/intc/xilinx_intc: Make device endianness configurable Philippe Mathieu-Daudé
2024-11-07 10:12   ` Richard Henderson
2024-11-07  1:22 ` [RFC PATCH v2 04/16] hw/net/xilinx_ethlite: Simplify by having configurable endianness Philippe Mathieu-Daudé
2024-11-07 10:16   ` Richard Henderson
2024-11-07  1:22 ` [RFC PATCH v2 05/16] hw/timer/xilinx_timer: Allow down to 8-bit memory access Philippe Mathieu-Daudé
2024-11-07  1:22 ` [PATCH v2 06/16] hw/timer/xilinx_timer: Make device endianness configurable Philippe Mathieu-Daudé
2024-11-07 10:18   ` Richard Henderson
2024-11-07  1:22 ` [PATCH v2 07/16] hw/char/xilinx_uartlite: " Philippe Mathieu-Daudé
2024-11-07 10:27   ` Richard Henderson [this message]
2024-11-08 15:06     ` Philippe Mathieu-Daudé
2024-11-07  1:22 ` [PATCH v2 08/16] hw/ssi/xilinx_spi: " Philippe Mathieu-Daudé
2024-11-07 11:01   ` Richard Henderson
2024-11-08 15:07     ` Philippe Mathieu-Daudé
2024-11-07  1:22 ` [PATCH v2 09/16] hw/ssi/xilinx_spips: " Philippe Mathieu-Daudé
2024-11-07 11:02   ` Richard Henderson
2024-11-07  1:22 ` [PATCH v2 10/16] target/microblaze: Explode MO_TExx -> MO_TE | MO_xx Philippe Mathieu-Daudé
2024-11-07  1:22 ` [PATCH v2 11/16] target/microblaze: Set MO_TE once in do_load() / do_store() Philippe Mathieu-Daudé
2024-11-07  1:22 ` [PATCH v2 12/16] target/microblaze: Introduce mo_endian() helper Philippe Mathieu-Daudé
2024-11-07  1:22 ` [PATCH v2 13/16] target/microblaze: Consider endianness while translating code Philippe Mathieu-Daudé
2024-11-07  1:22 ` [PATCH v2 14/16] hw/microblaze: Support various endianness for s3adsp1800 machines Philippe Mathieu-Daudé
2024-11-07  1:22 ` [PATCH v2 15/16] tests/functional: Explicit endianness of microblaze assets Philippe Mathieu-Daudé
2024-11-07  1:22 ` [PATCH v2 16/16] tests/functional: Add microblaze cross-endianness tests 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=fe69adc2-0ebb-4be0-93a2-9a45d87c36d3@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alistair@alistair23.me \
    --cc=anjo@rev.ng \
    --cc=devel@lists.libvirt.org \
    --cc=edgar.iglesias@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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).