From: Thomas Huth <huth@tuxfamily.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH 4/5] hw/openrisc: Mark devices as big-endian
Date: Sat, 9 Nov 2024 19:40:05 +0100 [thread overview]
Message-ID: <20241109194005.628e8a53@tpx1> (raw)
In-Reply-To: <dfccc639-8347-4e75-af08-cee7f8ae2bd9@linaro.org>
Am Sat, 9 Nov 2024 10:08:16 -0800
schrieb Richard Henderson <richard.henderson@linaro.org>:
> On 11/9/24 07:58, Philippe Mathieu-Daudé wrote:
> > Hi Thomas,
> >
> > On 9/11/24 06:42, Thomas Huth wrote:
> >> Am Wed, 6 Nov 2024 18:46:11 +0000
> >> schrieb Philippe Mathieu-Daudé <philmd@linaro.org>:
> >>
> >>> These devices are only used by the OpenRISC target, which is
> >>> only built as big-endian. Therefore the DEVICE_NATIVE_ENDIAN
> >>> definition expand to DEVICE_BIG_ENDIAN (besides, the
> >>> DEVICE_LITTLE_ENDIAN case isn't tested). Simplify directly
> >>> using DEVICE_BIG_ENDIAN.
> >>>
> >>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> >>> ---
> >>> hw/openrisc/openrisc_sim.c | 2 +-
> >>> hw/openrisc/virt.c | 2 +-
> >>> 2 files changed, 2 insertions(+), 2 deletions(-)
> >
> >
> >>> diff --git a/hw/openrisc/virt.c b/hw/openrisc/virt.c
> >>> index 47d2c9bd3c..ede57fe391 100644
> >>> --- a/hw/openrisc/virt.c
> >>> +++ b/hw/openrisc/virt.c
> >>> @@ -236,7 +236,7 @@ static void openrisc_virt_serial_init(OR1KVirtState *state, hwaddr
> >>> base,
> >>> qemu_irq serial_irq = get_per_cpu_irq(cpus, num_cpus, irq_pin);
> >>> serial_mm_init(get_system_memory(), base, 0, serial_irq, 115200,
> >>> - serial_hd(0), DEVICE_NATIVE_ENDIAN);
> >>> + serial_hd(0), DEVICE_BIG_ENDIAN);
> >>> /* Add device tree node for serial. */
> >>> nodename = g_strdup_printf("/serial@%" HWADDR_PRIx, base);
> >>
> >> According to https://openrisc.io/or1k.html the openrisc CPU could be
> >> implemented as little endian, too ... so would it make sense to use
> >> a runtime detected value here instead?
> >
> > While this patch is a code change, it aims to not introduce any
> > functional change. We are not building (nor testing) these devices
> > in a little endian configuration:
> >
> > $ git grep -l TARGET_BIG_ENDIAN configs/targets/*softmmu*
> > configs/targets/hppa-softmmu.mak
> > configs/targets/m68k-softmmu.mak
> > configs/targets/microblaze-softmmu.mak
> > configs/targets/mips-softmmu.mak
> > configs/targets/mips64-softmmu.mak
> > configs/targets/or1k-softmmu.mak
> > ^^^^
>
> The openrisc little-endian control is in a control register: SR[LEE] (which we do not
> implement at present).
>
> So any openrisc little-endian support would look like qemu-system-ppc64. I would not
> expect devices to switch endianness at all.
Ok, thanks, in that case, I think the patch is fine.
FWIW:
Reviewed-by: Thomas Huth <huth@tuxfamily.org>
next prev parent reply other threads:[~2024-11-09 18:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 18:46 [PATCH 0/5] hw: Mark architecture specific devices with specific endianness Philippe Mathieu-Daudé
2024-11-06 18:46 ` [PATCH 1/5] hw/i386: Mark devices as little-endian Philippe Mathieu-Daudé
2024-11-07 9:59 ` Richard Henderson
2024-11-09 6:39 ` Thomas Huth
2024-11-06 18:46 ` [PATCH 2/5] hw/tricore: " Philippe Mathieu-Daudé
2024-11-07 10:01 ` Richard Henderson
2024-11-09 6:38 ` Thomas Huth
2024-11-06 18:46 ` [PATCH 3/5] hw/m68k: Mark devices as big-endian Philippe Mathieu-Daudé
2024-11-07 10:02 ` Richard Henderson
2024-11-09 6:28 ` Thomas Huth
2024-11-06 18:46 ` [PATCH 4/5] hw/openrisc: " Philippe Mathieu-Daudé
2024-11-07 10:03 ` Richard Henderson
2024-11-09 6:42 ` Thomas Huth
2024-11-09 15:58 ` Philippe Mathieu-Daudé
2024-11-09 18:08 ` Richard Henderson
2024-11-09 18:40 ` Thomas Huth [this message]
2024-11-06 18:46 ` [PATCH 5/5] hw/sparc: " Philippe Mathieu-Daudé
2024-11-06 22:56 ` Mark Cave-Ayland
2024-11-07 10:04 ` Richard Henderson
2024-12-30 16:42 ` [PATCH 0/5] hw: Mark architecture specific devices with specific endianness 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=20241109194005.628e8a53@tpx1 \
--to=huth@tuxfamily.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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.