From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Kevin Wolf" <kwolf@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
qemu-block@nongnu.org, qemu-trivial@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Magnus Damm" <magnus.damm@gmail.com>
Subject: Re: [PATCH] tests/qemu-iotests/testenv: Use the "r2d" machine for sh4/sh4eb
Date: Wed, 25 Sep 2024 16:12:55 +0900 [thread overview]
Message-ID: <87a5fwjjew.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <872ca5a9-2359-4a83-9031-8c82fcdb7665@redhat.com>
On Fri, 20 Sep 2024 17:12:47 +0900,
Thomas Huth wrote:
>
> On 20/09/2024 10.06, Yoshinori Sato wrote:
> > On Wed, 18 Sep 2024 04:43:50 +0900,
> > Thomas Huth wrote:
> >>
> >> Commit 0ea0538fae516f9b4 removed the default machine of the sh4
> >> binaries, so a lot of iotests are failing now without such a default
> >> machine. Teach the iotest harness to use the "r2d" machine instead
> >> to fix this problem.
> >>
> >> Signed-off-by: Thomas Huth <thuth@redhat.com>
> >> ---
> >> tests/qemu-iotests/testenv.py | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/tests/qemu-iotests/testenv.py b/tests/qemu-iotests/testenv.py
> >> index 0b32eec119..6326e46b7b 100644
> >> --- a/tests/qemu-iotests/testenv.py
> >> +++ b/tests/qemu-iotests/testenv.py
> >> @@ -244,6 +244,8 @@ def __init__(self, source_dir: str, build_dir: str,
> >> ('riscv32', 'virt'),
> >> ('riscv64', 'virt'),
> >> ('rx', 'gdbsim-r5f562n8'),
> >> + ('sh4', 'r2d'),
> >> + ('sh4eb', 'r2d'),
> >> ('tricore', 'tricore_testboard')
> >> )
> >> for suffix, machine in machine_map:
> >> --
> >> 2.46.0
> >>
> >
> > r2d is works only sh4 little endian mode.
>
> Oh, that's interesting - since there is no other machine left for sh4/sh4eb.
>
> > There was probably no other hardware that ran in big endian.
>
> There used to be the "shix" machine, but it got removed, I assume that
> one worked in big endian mode, too?
Since shix's only external device is memory, it will work in big endian.
r2d has some peripheral devices that do not support big endian.
> > Anyway, if the r2d machine only works in little endian mode, and there
> is apparently no other machine available anymore, I think we can
> disable the sh4eb target completely since it is of no use now? Or is
> there a reason to still keep it around?
You're right. I haven't used sh4eb in years, and I don't think anyone needs it.
> Thomas
>
--
Yosinori Sato
next prev parent reply other threads:[~2024-09-25 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 19:43 [PATCH] tests/qemu-iotests/testenv: Use the "r2d" machine for sh4/sh4eb Thomas Huth
2024-09-20 8:06 ` Yoshinori Sato
2024-09-20 8:12 ` Thomas Huth
2024-09-25 7:12 ` Yoshinori Sato [this message]
2024-10-03 17:22 ` 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=87a5fwjjew.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=magnus.damm@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).